Forum Home
Press F1
 
Thread ID: 47680 2004-08-02 07:46:00 Slowdown of gaming connection Jester (13) Press F1
Post ID Timestamp Content User
257547 2004-08-02 07:46:00 Where is my bottleneck?

I have experienced a sudden slow-down in gaming connection . It happened the other day after Telecom's snafu which has since been resolved . . . . apparently .

Telecom email: " I can confirm we had a routing issue last week which may have caused some issues, but this was resolved last Friday and we have experienced no issues since then . "

My 256k browsing and downloading connection seems ok, but gaming pings have gone from a steady 40-50 to a widely variable 70-200 . I am with Orcon, who said they can't find the problem . Telecom inferred it's an Orcon prob . I then signed up with Xtra yesterday (there goes $27 . 95, but I am gonna play the I'm not satisfied card if I can't get it resolved) to see whether it was any different, and nope, it's not . There is NO difference in pings when using the JSG Realm .

Screenshot ( . neoburn . net/imagef1/files/ase . jpg" target="_blank">sal . neoburn . net)of All Seeing Eye for BF1942 shows high pings . ASE generally reports higher than what I get in the game, but usually they show in the 60's .

Tracerts to various IP addys reveal that I am getting about 70 - 80 ping to NZ and 200-300 to overseas, with lots of timeouts . Telecom checked my line and it was ok .

Can anyone else give me indication of their pings using tracert etc? I need comparisons and ideas of places to ping to for testing .

Cheers

J
:D
Jester (13)
257548 2004-08-02 08:48:00 Heres a couple for you.

I'm on Jetsurf 256 with Telecom.

C:\DOCUME~1\SAM>tracert pressf1.pcworld.co.nz

Tracing route to forums.pcworld.co.nz [210.48.100.45]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 48 ms 45 ms 45 ms 222-152-88-1.jetstream.xtra.co.nz [222.152.88.1]

3 90 ms 44 ms 44 ms 210.55.205.123
4 52 ms 52 ms 52 ms 222.152.127.1
5 53 ms 53 ms 52 ms 202.50.245.193
6 53 ms 54 ms 54 ms f4-0-1-6.akcr5.global-gateway.net.nz [202.37.246
.20]
7 52 ms 53 ms 52 ms iconz1.ape.net.nz [192.203.154.44]
8 53 ms 53 ms 53 ms ae-01a.akl.iconz.net [202.14.100.20]
9 53 ms 55 ms 54 ms e0-0.core3.akl.iconz.net.nz [202.14.100.220]
10 54 ms 53 ms 54 ms ip-210-48-113-34.iconz.net.nz [210.48.113.34]
11 54 ms 54 ms 57 ms ip-210-48-100-45.iconz.net.nz [210.48.100.45]

C:\DOCUME~1\SAM>tracert o-bot.com

Tracing route to o-bot.com [203.96.152.15]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 44 ms 44 ms 45 ms 222-152-88-1.jetstream.xtra.co.nz [222.152.88.1]

3 44 ms 44 ms 43 ms 210.55.205.123
4 52 ms 53 ms 91 ms 222.152.127.1
5 53 ms 53 ms 54 ms 202.50.245.193
6 54 ms 53 ms 54 ms f4-0-1-6.akcr5.global-gateway.net.nz [202.37.246
.20]
7 102 ms 62 ms 55 ms telstraclear2.ape.net.nz [192.203.154.33]
8 228 ms 187 ms 193 ms g1-0-1043.u12.brh.telstraclear.net [203.98.23.17
]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 65 ms 75 ms 63 ms a12-3-23.u21.tar.telstraclear.net [203.98.23.34]

13 64 ms 64 ms 64 ms fa7-4-1042.bertha.tce.telstraclear.net [203.98.2
3.42]
14 65 ms 64 ms 64 ms vanessa.paradise.net.nz [203.96.152.15]

Trace complete.

C:\DOCUME~1\SAM>tracert tw.giga-byte.com

Tracing route to tw.giga-byte.com [203.66.138.81]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 45 ms 45 ms 45 ms 222-152-88-1.jetstream.xtra.co.nz [222.152.88.1]

3 43 ms 43 ms 161 ms 210.55.205.123
4 * * * Request timed out.
5 738 ms 164 ms 89 ms vlan-283.tkbr4.global-gateway.net.nz [202.50.245
.197]
6 754 ms 707 ms 792 ms g2-0-3.tkbr3.global-gateway.net.nz [202.37.245.1
40]
7 298 ms 925 ms 902 ms 203.96.120.189
8 148 ms 338 ms 79 ms 202.68.65.17
9 77 ms 78 ms 77 ms ge-1-0-0.r00.sydnau01.au.bb.verio.net [202.68.64
.249]
10 197 ms 197 ms 197 ms p1-0-2-0.r00.tokyjp01.jp.bb.verio.net [129.250.2
.229]
11 396 ms 238 ms 239 ms p4-1.hinet.tokyjp01.jp.bb.verio.net [129.250.9.1
26]
12 237 ms 238 ms 240 ms 211.75.91.206
13 239 ms 238 ms 237 ms tp-s2-c7r6.router.hinet.net [168.95.2.226]
14 240 ms 240 ms 244 ms 210.61.147.1
15 239 ms 239 ms 238 ms 211.75.172.14
16 239 ms 239 ms 239 ms 203.66.138.81

Trace complete.

Shaun
Shaun Minfie (2961)
257549 2004-08-02 09:16:00 Thanks Shaun - mine used to look like that for press f1. Heres the latest.

>tracert pressf1.pcworld.co.nz

Tracing route to forums.pcworld.co.nz [210.48.100.45]
over a maximum of 30 hops:

1 * * * Request timed out.
2 78 ms 77 ms 77 ms 222-152-172-1.jetstream.xtra.co.nz [222.152.172.1]
3 94 ms 62 ms 77 ms 210.55.205.249
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 156 ms 93 ms 109 ms ae-01a.akl.iconz.net [202.14.100.20]
9 78 ms 77 ms 77 ms e0-0.core3.akl.iconz.net.nz [202.14.100.220]
10 78 ms 78 ms 77 ms ip-210-48-113-34.iconz.net.nz [210.48.113.34]
11 74 ms 75 ms 73 ms ip-210-48-100-45.iconz.net.nz [210.48.100.45]

Trace complete.
Jester (13)
1