1: 300% increase in latency during peak periods on Big Time this week. 2: It was fine in previous weeks, has a recent change caused this? 3: Traffic management and/or caching hardware isn't handling the load adequately? 4: 500ms is woefully bad latency, it's normally 150-180ms to the US and under 100ms to AU
Example: 8pm Sunday 30th August
Tracing route to youtube.com [74.125.67.100] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1 2 1 ms <1 ms <1 ms 192.168.1.1 3 22 ms 8 ms 7 ms 210-55-69-120.iprolink.co.nz [210.55.69.120] 4 * * * Request timed out. 5 310 ms 321 ms 323 ms xe6-0-0-10.akbr5.global-gateway.net.nz [202.37.244.221] 6 305 ms 302 ms * xe0-0-0-2.akbr4.global-gateway.net.nz [202.50.232.77] 7 280 ms 281 ms 287 ms xe6-1-0.tkbr9.global-gateway.net.nz [202.50.232.186] 8 453 ms 441 ms 437 ms so6-0-3.labr5.global-gateway.net.nz [122.56.127.34] 9 450 ms 440 ms 466 ms so6-0-1.sjbr2.global-gateway.net.nz [202.50.232.89] 10 414 ms 427 ms 427 ms 202.50.232.234 11 464 ms 465 ms 466 ms 74.125.49.105 12 441 ms 448 ms 444 ms 216.239.49.250 13 526 ms 524 ms 524 ms 209.85.249.140 14 517 ms 509 ms 520 ms 72.14.239.127 15 542 ms 534 ms 545 ms 209.85.255.198 16 514 ms 512 ms 508 ms gw-in-f100.google.com [74.125.67.100]
Tracing route to bbc.co.uk [212.58.224.138] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1 2 1 ms <1 ms <1 ms 192.168.1.1 3 8 ms 8 ms 8 ms 210-55-69-120.iprolink.co.nz [210.55.69.120] 4 * * * Request timed out. 5 319 ms 318 ms 317 ms xe6-0-0-10.akbr5.global-gateway.net.nz [202.37.244.221] 6 318 ms 309 ms 304 ms xe0-0-0-2.akbr4.global-gateway.net.nz [202.50.232.77] 7 297 ms 295 ms 295 ms xe6-1-0.tkbr9.global-gateway.net.nz [202.50.232.186] 8 433 ms 435 ms 443 ms so6-1-1.labr5.global-gateway.net.nz [122.56.127.62] 9 454 ms 454 ms 451 ms so7-0-3.sjbr2.global-gateway.net.nz [122.56.127.54] 10 429 ms 428 ms 425 ms 202.50.232.234 11 540 ms 510 ms 619 ms ge-6-6.car2.SanJose2.Level3.net [4.59.4.57] 12 454 ms 444 ms 436 ms vlan79.csw2.SanJose1.Level3.net [4.68.18.126] 13 445 ms 439 ms 453 ms ae-74-74.ebr4.SanJose1.Level3.net [4.69.134.245] 14 529 ms 539 ms 539 ms ae-2.ebr4.NewYork1.Level3.net [4.69.135.186] 15 532 ms 528 ms 532 ms ae-74-74.csw2.NewYork1.Level3.net [4.69.134.118] 16 524 ms 519 ms 529 ms ae-71-71.ebr1.NewYork1.Level3.net [4.69.134.69] 17 572 ms 580 ms 579 ms ae-41-41.ebr2.London1.Level3.net [4.69.137.65] 18 590 ms 584 ms 583 ms ae-24-52.car3.London1.Level3.net [4.69.139.100] 19 559 ms 554 ms 554 ms 195.50.90.190 20 590 ms 589 ms 586 ms 212.58.238.129 21 588 ms 594 ms 589 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]
Tracing route to facebook.com [69.63.178.11] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1 2 1 ms <1 ms <1 ms 192.168.1.1 3 8 ms 8 ms 8 ms 210-55-69-120.iprolink.co.nz [210.55.69.120] 4 * * * Request timed out. 5 308 ms 309 ms 307 ms xe6-0-0-10.akbr5.global-gateway.net.nz [202.37.244.221] 6 300 ms 301 ms 302 ms xe0-0-0-2.akbr4.global-gateway.net.nz [202.50.232.77] 7 290 ms 291 ms 323 ms xe6-1-0.tkbr9.global-gateway.net.nz [202.50.232.186] 8 414 ms 407 ms 415 ms so7-0-1.labr5.global-gateway.net.nz [122.56.127.38] 9 464 ms 456 ms 452 ms so6-0-2.sjbr2.global-gateway.net.nz [202.50.232.93] 10 448 ms 455 ms 460 ms so0-0-1.pabr4.global-gateway.net.nz [202.50.232.86] 11 458 ms 465 ms 468 ms paix.br01.pao1.tfbnw.net [198.32.176.71] 12 482 ms 477 ms 475 ms xe-0-0-0.br02.pao1.tfbnw.net [204.15.20.35] 13 457 ms 455 ms 462 ms xe-7-0-0.br01.snc1.tfbnw.net [204.15.20.9] 14 442 ms 450 ms 455 ms te-11-0.csw01b.snc1.tfbnw.net [204.15.21.46] 15 452 ms 464 ms 434 ms www-02-01-snc1.facebook.com [69.63.178.11]
Tracing route to internode.on.net [203.16.214.17] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1 2 1 ms <1 ms <1 ms 192.168.1.1 3 9 ms 7 ms 10 ms 210-55-69-120.iprolink.co.nz [210.55.69.120] 4 * * * Request timed out. 5 282 ms 284 ms 291 ms xe6-0-0-10.akbr5.global-gateway.net.nz [202.37.244.221] 6 298 ms 291 ms 297 ms xe0-0-0-2.akbr4.global-gateway.net.nz [202.50.232.77] 7 280 ms 273 ms 275 ms so1-1-1.tkbr9.global-gateway.net.nz [203.96.120.194] 8 309 ms 288 ms 306 ms so1-1-1.sybr6.global-gateway.net.nz [202.50.232.218] 9 295 ms 293 ms 292 ms xe2-0-0-2.sybr4.global-gateway.net.nz [202.50.232.242] 10 291 ms 289 ms 290 ms vlan356.52gdc76f02.optus.net.au [59.154.21.137] 11 317 ms 309 ms 308 ms 61.88.221.51 12 309 ms 314 ms 312 ms internodesystemspl.optus.net.au [59.154.0.18] 13 330 ms 336 ms 363 ms gi1-24.cor3.adl2.internode.on.net [150.101.134.50] 14 332 ms 327 ms 320 ms po2.rtr2.adl2.internode.on.net [150.101.136.1] 15 319 ms 327 ms 317 ms corp.internode.on.net [203.16.214.17]
are you guys on adsl2 or normal? i'm currnetly on telstra 10G plan and find i run out of quota after 2 weeks or so ending up nearly turning the PC off so's not to go over the limit. I have talked to Telecom and i can go on Big Time ADSL2. Thought thats great only i'd be paying $40 a month for a land-line i'd never use... Telstra wasn't any better for gaming, i constantly had micro outages which would drop game (warhawk- i know a while ago now). Completely ruined my ranking and ended up quiting...
You can check if the the exchange or cabinet in your area supports ADSL2+ but putting your address (or a neighbours address) in this map tool (link below). Your modem needs to support ADSL2+ and if you are too far from the exchange/cabinet you will be better off connecting in ADSL1 mode for stability.
The connection rate/speed you see in your modem's admin status pages will depend on your distance from the exchange/cabinet and the quality of your wiring. The actual speed you'll see downloading something will depend on ISP congestion, the time of day and so on.
Back on topic for this thread...
Gaming on local NZ servers is fine, it's just AU and US latency at peak time since the start of last week that's been a problem.
I've been on Big Time for my home connection since the 5th of August and only noticed this international latency problem after work from the ~20th I think.
I've never had so much latency in all 7 years I have been gaming! It's impossible to play! I'm really frustrated and about to chuck in my Telecom Broadband and phone line etc... I did this trace route...what does this mean? TraceRoute to 125.238.88.xxx [125-238-88-xxx.broadband-telecom.global-gateway.net.nz] Hop (ms) (ms) (ms) IP Address Host name 1 12 24 6 206.123.69.137 - 2 7 11 13 8.9.232.73 xe-5-3-0.edge3.dallas1.level3.net 3 16 22 20 4.69.145.116 ae-73-70.ebr3.dallas1.level3.net 4 45 54 51 4.69.132.77 ae-3.ebr2.losangeles1.level3.net 5 48 55 Timed out 4.69.146.12 ae-73-78.ebr3.losangeles1.level3.net 6 55 77 62 4.69.132.9 ae-2.ebr3.sanjose1.level3.net 7 61 55 52 4.69.134.234 ae-83-83.csw3.sanjose1.level3.net 8 49 50 55 4.68.18.140 ae-42-89.car2.sanjose2.level3.net 9 50 49 49 4.59.4.26 telecom-new.car2.sanjose2.level3.net 10 49 51 57 202.50.232.17 so7-0-1.sjbr2.global-gateway.net.nz 11 203 168 196 122.56.127.21 so1-0-1.akbr4.global-gateway.net.nz 12 202 172 199 202.50.232.78 xe0-0-0-2.akbr5.global-gateway.net.nz 13 226 216 217 202.50.237.34 mdr-fid-int.akbr5.global-gateway.net.nz 14 268 228 219 210.55.67.80 210-55-67-80.adsl.netgate.net.nz 15 Timed out Timed out Timed out - 16 Timed out Timed out Timed out - 17 Timed out Timed out Timed out - 18 Timed out Timed out Timed out -
Does seem to be a BT problem. I have a few friends on BT having the same problem.
In comparision, a trace route on Go Large to Internode.
Tracing route to www.internode.on.net [203.16.214.27] over a maximum of 30 hops:
1 * * * Request timed out. 2 50 ms 49 ms 49 ms ip210-55-69-224.kc.net.nz [210.55.69.224] 3 * * * Request timed out. 4 61 ms 59 ms 61 ms xe6-0-0-10.akbr5.global-gateway.net.nz [202.37.244.221] 5 61 ms 61 ms 61 ms xe0-0-0-2.akbr4.global-gateway.net.nz [202.50.232.77] 6 60 ms 61 ms 59 ms xe6-1-0.tkbr9.global-gateway.net.nz [202.50.232.186] 7 84 ms 83 ms 85 ms so7-0-1.sybr6.global-gateway.net.nz [122.56.127.42] 8 82 ms 85 ms 83 ms xe2-0-0-2.sybr4.global-gateway.net.nz [202.50.232.242] 9 86 ms 85 ms 85 ms vlan556.52gdc76f02.optus.net.au [59.154.21.137] 10 113 ms 113 ms 113 ms 61.88.221.53 11 118 ms 117 ms 117 ms internodesystemspl.optus.net.au [59.154.0.18] 12 114 ms 111 ms 113 ms gi1-9.cor1.adl6.internode.on.net [150.101.225.98] 13 118 ms 119 ms 119 ms po2.rtr2.adl6.internode.on.net [150.101.136.5] 14 117 ms 117 ms 117 ms pubweb.internode.on.net [203.16.214.27]
profrink: Does seem to be a BT problem. I have a few friends on BT having the same problem.
In comparision, a trace route on Go Large to Internode.
Tracing route to www.internode.on.net [203.16.214.27] over a maximum of 30 hops:
1 * * * Request timed out. 2 50 ms 49 ms 49 ms ip210-55-69-224.kc.net.nz [210.55.69.224] 3 * * * Request timed out. 4 61 ms 59 ms 61 ms xe6-0-0-10.akbr5.global-gateway.net.nz [202.37.244.221] 5 61 ms 61 ms 61 ms xe0-0-0-2.akbr4.global-gateway.net.nz [202.50.232.77] 6 60 ms 61 ms 59 ms xe6-1-0.tkbr9.global-gateway.net.nz [202.50.232.186] 7 84 ms 83 ms 85 ms so7-0-1.sybr6.global-gateway.net.nz [122.56.127.42] 8 82 ms 85 ms 83 ms xe2-0-0-2.sybr4.global-gateway.net.nz [202.50.232.242] 9 86 ms 85 ms 85 ms vlan556.52gdc76f02.optus.net.au [59.154.21.137] 10 113 ms 113 ms 113 ms 61.88.221.53 11 118 ms 117 ms 117 ms internodesystemspl.optus.net.au [59.154.0.18] 12 114 ms 111 ms 113 ms gi1-9.cor1.adl6.internode.on.net [150.101.225.98] 13 118 ms 119 ms 119 ms po2.rtr2.adl6.internode.on.net [150.101.136.5] 14 117 ms 117 ms 117 ms pubweb.internode.on.net [203.16.214.27]
Trace complete.
8.25pm Tuesday
yes and i should hope telecom are fixing this as they clearly state that the big time plan is ideal for online gaming witch clearly it is not so apart from the unlimited downloads the only other good thing for me from the bigtime plan is it gives me a reason not to play games and get some work done.
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.
Trusted
