Tracing route to war-clouds.com [67.106.81.125] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms RTA1335.home [192.168.1.1] 2 9 ms 10 ms 8 ms 210-55-67-80.adsl.netgate.net.nz [210.55.67.80]
3 * * * Request timed out. 4 198 ms 192 ms 303 ms xe6-0-0-10.akbr5.global-gateway.net.nz [202.37.2 44.221] 5 195 ms 310 ms 314 ms xe0-0-0-2.akbr4.global-gateway.net.nz [202.50.23 2.77] 6 312 ms 306 ms 310 ms xe6-1-0.tkbr9.global-gateway.net.nz [202.50.232. 186] 7 436 ms 430 ms 433 ms so7-0-1.labr5.global-gateway.net.nz [122.56.127. 38] 8 441 ms 531 ms 440 ms so6-0-2.sjbr2.global-gateway.net.nz [202.50.232. 93] 9 507 ms 475 ms 475 ms so-0-0-0.pabr4.global-gateway.net.nz [203.96.120 .218] 10 431 ms 433 ms 427 ms 206.111.12.141.ptr.us.xo.net [206.111.12.141] 11 466 ms 466 ms 468 ms te-3-4-0.rar3.sanjose-ca.us.xo.net [207.88.12.17 7] 12 383 ms * 497 ms te-3-0-0.rar3.denver-co.us.xo.net [207.88.12.57]
13 480 ms 479 ms 487 ms te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21 ] 14 523 ms 500 ms 507 ms 65.106.1.89.ptr.us.xo.net [65.106.1.89] 15 500 ms 506 ms 511 ms p7-0-0.MAR2.Chicago13-IL.us.xo.net [65.106.6.186 ] 16 396 ms 497 ms 505 ms v301.cer1.chicago13-il.us.xo.net [71.5.184.11] 17 507 ms 511 ms 503 ms 209.117.0.250 18 498 ms 500 ms 495 ms war-clouds.com [67.106.81.125]
hop 4: 198 ms 192 ms 303 ms xe6-0-0-10.akbr5.global-gateway.net.nz [202.37.244.221]
200ms to a local boarder router is pretty slow, however as Pen mentioned earlier routers de-prioritise ICMP packets so sometimes these tests can be a little misleading.
For $60 a month I think you're doing quite well considering you can seemingly backup the internet for free each month. Perhaps you should look to change plans if your gaming is that important to you while they work on their traffic management, then change back once you see people stop complaining about it.
Hop 3 for his gateway (210.55.67.80) is mdr-fid-int.akbr5.global-gateway.net.nz, many gamers on Big Time routed via that interface have noticed a high latency problem in peak times starting in August.
Not every Big Time customer is routed via that interface though, some regions you can reboot your router till you get an ip address on a range that is routed via a different interface (this is the case for me).
I and many others reported the problem via this form about half way through August so they know there is a problem it's just a matter of if and when it gets fixed.
If I was you I'd report the problem too and give them a decent amount of time to sort it out. You can always change ISP or change plan to Pro. I don't believe pro is affected.
Looks like the average home now needs at least two Internet connections, one for the gamers in the house and one for everybody else, or maybe one connection to one ISP and a second connection to another ISP. I guess this is also why lots of people have two cell phones. So much for all you can eat plans, it is more like everything we can feed you with a tooth pick plan.
I'm switching back to Adventure plan for gaming to see if it makes an ounce of difference... which I believe it won't. I've never had so much latency problems ever in 7 years of gaming since the ADSL2+ cabinet came online earlier this year. I want to go back to ADSL1 at least I could game in the U.S. In fact dial up was better!!!!!! THIS IS JUST CRAP BROADBAND SERVICE TELECOM!
I have heard it's only a problem for Big Time users and only on the ip address ranges that go via the bad interface/3rd hop. So I wouldn't expect the same problem on a standard plan.
Hey thanks for your helpful replies Ragnor. I have now been switched back to Telecom's Adventure plan. I still think something is wrong...as gaming is no better than Big Time and HOP 3 is timing out...this can't be good. HOP 5 & 6 has a huge ping! What have Telecom changed in the last 9 months? The way they route International traffic? It's just not the same service I was getting last year or the 6 years before? I thought ADSL2+ was supposed to be better? Not for my international gaming. Here is my tracert to my gaming server in the U.S. Tracing route to war-clouds.com [67.106.81.125] over a maximum of 30 hops:
1 2 ms <1 ms <1 ms RTA1335.home [192.168.1.1] 2 34 ms 29 ms 30 ms 125-237-32-1.jetstream.xtra.co.nz [125.237.32.1]
3 * * * Request timed out. 4 34 ms 35 ms 34 ms xe6-0-0-10.akbr5.global-gateway.net.nz [202.37.2 44.221] 5 4294967270 ms 34 ms 34 ms xe0-0-0-2.akbr4.global-gateway.net.nz [202 .50.232.77] 6 4294967270 ms 34 ms 34 ms g1-3-5.tkbr9.global-gateway.net.nz [202.50 .232.82] 7 101 ms 169 ms 159 ms so0-3-3.labr5.global-gateway.net.nz [202.50.232. 193] 8 131 ms 189 ms 190 ms so6-0-2.sjbr2.global-gateway.net.nz [202.50.232. 93] 9 194 ms 193 ms 131 ms so0-0-1.pabr4.global-gateway.net.nz [202.50.232. 86] 10 135 ms 189 ms 189 ms 206.111.12.141.ptr.us.xo.net [206.111.12.141] 11 136 ms 194 ms 195 ms 207.88.12.181.ptr.us.xo.net [207.88.12.181] 12 222 ms 219 ms 219 ms te-3-0-0.rar3.denver-co.us.xo.net [207.88.12.57]
13 218 ms 220 ms 220 ms te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21 ] 14 163 ms 162 ms 219 ms ge7-0-0d0.rar1.chicago-il.us.xo.net [65.106.1.41 ] 15 219 ms 219 ms 219 ms p7-0-0.MAR1.Chicago13-IL.us.xo.net [65.106.6.182 ] 16 222 ms 219 ms 219 ms v300.CER1.Chicago13-IL.us.xo.net [71.5.184.3] 17 161 ms 219 ms 219 ms 209.117.0.250 18 220 ms 162 ms 220 ms war-clouds.com [67.106.81.125]
Here is another Tracert....This one looks worse!!!!!! Tracing route to war-clouds.com [67.106.81.125] over a maximum of 30 hops:
1 1 ms <1 ms 4294967240 ms RTA1335.home [192.168.1.1] 2 4294967270 ms4294967269 ms4294967268 ms 125-237-32-1.jetstream.xtra.co .nz [125.237.32.1] 3 * * * Request timed out. 4 34 ms 4294967273 ms4294967274 ms xe6-0-0-10.akbr5.global-gateway.net. nz [202.37.244.221] 5 4294967274 ms 4294967273 ms4294967274 ms xe0-0-0-2.akbr4.global-gateway .net.nz [202.50.232.77] 6 4294967274 ms4294967278 ms4294967274 ms g1-3-5.tkbr9.global-gateway.ne t.nz [202.50.232.82] 7 101 ms 102 ms 101 ms so0-3-3.labr5.global-gateway.net.nz [202.50.232. 193] 8 131 ms 131 ms 132 ms so6-0-2.sjbr2.global-gateway.net.nz [202.50.232. 93] 9 134 ms 131 ms 132 ms so0-0-1.pabr4.global-gateway.net.nz [202.50.232. 86] 10 133 ms 132 ms 131 ms 206.111.12.141.ptr.us.xo.net [206.111.12.141] 11 134 ms 137 ms 136 ms 207.88.12.181.ptr.us.xo.net [207.88.12.181] 12 219 ms 161 ms 219 ms te-3-0-0.rar3.denver-co.us.xo.net [207.88.12.57]
13 162 ms 161 ms 162 ms te-4-1-0.rar3.chicago-il.us.xo.net [207.88.12.21 ] 14 161 ms 162 ms 161 ms ge7-0-0d0.rar1.chicago-il.us.xo.net [65.106.1.41 ] 15 163 ms 162 ms 162 ms p7-0-0.MAR1.Chicago13-IL.us.xo.net [65.106.6.182 ] 16 164 ms 161 ms 221 ms v300.CER1.Chicago13-IL.us.xo.net [71.5.184.3] 17 163 ms 161 ms 162 ms 209.117.0.250 18 218 ms 161 ms 162 ms war-clouds.com [67.106.81.125]
I have also done this tracert to a New Zealand Server Inspire with the same results??? What is Up? I think I need technical help... Tracing route to 203-114-130-15.colo.sta.inspire.net.nz [203.114.130.15] over a maximum of 30 hops:
1 4294967240 ms 4294967239 ms 4294967239 ms RTA1335.home [192.168.1.1] 2 4294967273 ms 4294967270 ms 4294967272 ms 125-237-32-1.jetstream.xtra.c .nz [125.237.32.1] 3 * * * Request timed out. 4 4294967270 ms 4294967273 ms 4294967269 ms x6-0-0-v20.akcr10.global-gate ay.net.nz [202.50.238.49] 5 4294967270 ms 35 ms 4294967274 ms v4.aksw7.global-gateway.net.nz [210 55.202.51] 6 54 ms 4294967285 ms 4294967289 ms inspirenet-dom.aksw7.global-gateway net.nz [202.50.235.138] 7 4294967288 ms 4294967288 ms 50 ms 203-114-130-15.colo.sta.inspire.net nz [203.114.130.15]
Well hop 3 doesn't reply to ICMP traffic there's nothing wrong with that per se. However those huge numbers look impossible. Have you tried rebooting your modem/router?
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.
ID Verified
Trusted
