Latency to LA up around 60-100~ (UFB)

Forums › Snap › Latency to LA up around 60-100~ (UFB)

Kiwiownage

37 posts

Geek

Topic # 112232 1-Dec-2012 15:39
Just noticed this past week or so my latency has sky rocketed to LA/US West, normally I'd play on around 160-180, currently sitting on 250 and won't budge, has something changed? Its making my average experience on US servers even more average :( Seems to be effecting me in HoN/WoW, even speedtest.net is pinging high Is it just me? :(

1 | 2

16718 posts

Uber Geek

Moderator

Trusted

Biddle Corp

Subscriber

Reply # 725535 1-Dec-2012 16:04
Where is the spike occuring? A traceroute would be handy. *Need help configuring your Linksys ATA or IP Phones for New Zealand? Check my blog post

Kiwiownage

37 posts

Geek

Reply # 725537 1-Dec-2012 16:08
its not a spike, my latency is just 100 higher, all day everyday, doing tracert now

Kiwiownage

37 posts

Geek

Reply # 725539 1-Dec-2012 16:13
Tracing route to 12.129.254.216 over a maximum of 30 hops 1 <1 ms 4 ms <1 ms fritz.box [192.168.178.1] 2 8 ms 8 ms 8 ms 20.17.69.111.static.snap.net.nz [111.69.17.20] 3 5 ms 7 ms 8 ms 24.17.69.111.static.snap.net.nz [111.69.17.24] 4 * * * Request timed out. 5 * * * Request timed out. 6 19 ms 22 ms 19 ms xe-0-3-0-1037.mdr.core.snap.net.nz [111.69.27.66 ] 7 22 ms 19 ms 22 ms 111-69-27-65.core.snap.net.nz [111.69.27.65] 8 201 ms 198 ms 198 ms te7-3.ccr01.sjc05.atlas.cogentco.com [38.122.92. 105] 9 200 ms 201 ms 201 ms te0-3-0-7.ccr22.sjc01.atlas.cogentco.com [154.54 .6.69] 10 223 ms 213 ms 212 ms te0-3-0-2.mpd22.lax01.atlas.cogentco.com [154.54 .25.189] 11 214 ms 213 ms 212 ms te3-4.ccr02.lax05.atlas.cogentco.com [154.54.3.1 0] 12 225 ms 231 ms 229 ms 192.205.35.5 13 232 ms 237 ms 229 ms cr2.la2ca.ip.att.net [12.122.84.218] 14 232 ms 226 ms 233 ms gar20.la2ca.ip.att.net [12.122.128.181] 15 229 ms 231 ms 228 ms 12-122-254-234.attens.net [12.122.254.234] 16 227 ms 231 ms 227 ms 206.16.68.46 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete.

Kiwiownage

37 posts

Geek

Reply # 725559 1-Dec-2012 17:30
also spiking now... every 5 or so minutes it'll hang for a second

Stasis007

39 posts

Geek

Reply # 725588 1-Dec-2012 20:04
I've found the same. Normally sit around 160-180ms latency in WoW, last week or two it's consistently been 220-280+. Tracerting with my current latency of 233ms (which is better than it has been recently) shows: Tracing route to 12.129.254.156 over a maximum of 30 hops 1 <1 ms 1 ms 1 ms mygateway1.ar7 [10.1.1.1] 2 26 ms 6 ms 25 ms 20.17.69.111.static.snap.net.nz [111.69.17.20] 3 5 ms 5 ms 5 ms 24.17.69.111.static.snap.net.nz [111.69.17.24] 4 * * * Request timed out. 5 * * * Request timed out. 6 19 ms 19 ms 19 ms xe-0-3-0-1037.mdr.core.snap.net.nz [111.69.27.66] 7 20 ms 20 ms 19 ms 111-69-27-65.core.snap.net.nz [111.69.27.65] 8 199 ms 199 ms 199 ms te7-3.ccr01.sjc05.atlas.cogentco.com [38.122.92.105] 9 199 ms 199 ms 199 ms te0-3-0-7.ccr22.sjc01.atlas.cogentco.com [154.54.6.69] 10 211 ms 211 ms 211 ms te0-4-0-2.mpd22.lax01.atlas.cogentco.com [154.54.85.37] 11 245 ms 214 ms 217 ms te3-4.ccr02.lax05.atlas.cogentco.com [154.54.3.10] 12 213 ms 212 ms 212 ms 192.205.37.157 13 218 ms 219 ms 215 ms cr1.la2ca.ip.att.net [12.122.84.202] 14 213 ms 215 ms * gar20.la2ca.ip.att.net [12.122.128.181] 15 214 ms 212 ms 213 ms 12.122.251.190 16 216 ms 215 ms 215 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250] 17 * * * Request timed out. ..... 30 * * * Request timed out. I'll post again if my in-game latency changes significantly.

Kiwiownage

37 posts

Geek

Reply # 725589 1-Dec-2012 20:07
Here's what snap has to say : From what you can see from the trace, Router 8 is where your ping jumps. Router 8: 201 ms 198 ms 198 ms te7-3.ccr01.sjc05.atlas.cogentco.com That equipment its outside of Snap, which means there is nothing we can do to help as the route taken is dynamic. That said you could try a VPN Tunnel it would most likely change the route taken, which may help. so if I want to continue playing on american servers I'm going to have to fork out more money to get < 250 ms

RalphFromSnap

393 posts

Ultimate Geek

Trusted

Snap Internet

Reply # 725596 1-Dec-2012 20:44
Hi All, We have identified an issue which is causing increased latency (as you are seeing) to some USA routes. We have logged a fault with a 3rd party in the US and hope to have this resolved shortly. Apologies for the inconvenience. Thanks snap! 0800 BROADBAND (276 232) www.snap.net.nz @SnapInternet on Twitter Snap Internet on Facebook Our Team: ^MC Michelle Clements ^AL Allan Loveday ^RO Ricky Owens ^ST Sam Taylor

Kiwiownage

37 posts

Geek

Reply # 725601 1-Dec-2012 20:57
Awesome! Thanks for letting us know

Stasis007

39 posts

Geek

Reply # 725603 1-Dec-2012 21:41
Thanks Ralph

Kiwiownage

37 posts

Geek

Reply # 725701 2-Dec-2012 11:25
Definite improvement in "lowest latency" this morning , although its not what it used to be (Still around the 200-230 mark, was 280 yesterday though) But now I'm getting very inconsistent pings, and if anything this has made it worse (as in ALOT worse). Tracing route to 12.129.254.216 over a maximum of 30 hops 1 2 1 ms 3 26 ms 25 ms 21 ms 20.17.69.111.static.snap.net.nz [111.69.17.20] 4 7 ms 8 ms 8 ms 24.17.69.111.static.snap.net.nz [111.69.17.24] 5 * * * Request timed out. 6 * * * Request timed out. 7 23 ms 22 ms 21 ms xe-0-3-0-1037.mdr.core.snap.net.nz [111.69.27.66 ] 8 22 ms 22 ms 22 ms 111-69-27-65.core.snap.net.nz [111.69.27.65] 9 145 ms 147 ms 147 ms te7-3.ccr01.sjc05.atlas.cogentco.com [38.122.92. 105] 10 146 ms 148 ms 147 ms te0-3-0-7.ccr22.sjc01.atlas.cogentco.com [154.54 .6.69] 11 159 ms 159 ms 159 ms te0-3-0-2.mpd22.lax01.atlas.cogentco.com [154.54 .25.189] 12 224 ms 222 ms 211 ms te3-4.ccr02.lax05.atlas.cogentco.com [154.54.3.1 0] 13 187 ms 187 ms 187 ms 192.205.35.5 14 164 ms 160 ms 163 ms cr2.la2ca.ip.att.net [12.122.84.218] 15 185 ms 164 ms 186 ms gar29.la2ca.ip.att.net [12.122.129.241] 16 163 ms 189 ms 191 ms 12-122-254-234.attens.net [12.122.254.234] 17 162 ms 160 ms 158 ms 206.16.68.46

Kiwiownage

37 posts

Geek

Reply # 725702 2-Dec-2012 11:27
Wont let me edit, Anywho latency is now sitting around 210-400, it's now unplayable Edit : just running ping plotter for a bit and it seems the 13th hop (192.205.35.5) is where the spike in latency occurs

Kiwiownage

37 posts

Geek

Reply # 725774 2-Dec-2012 15:30
Seems better now. Yay

savag3

179 posts

Master Geek

Subscriber

Reply # 726569 4-Dec-2012 03:33
It looks like Snap have changed their international bandwidth provider from TelstraClear to someone else. Traceroutes now look quite different to TelstraClear cable and appear to go through Cogent in the US.

mercutio

783 posts

Ultimate Geek

Reply # 726672 4-Dec-2012 11:18
savag3: It looks like Snap have changed their international bandwidth provider from TelstraClear to someone else. Traceroutes now look quite different to TelstraClear cable and appear to go through Cogent in the US. i think you'll find that telstraclear bought online cogent capacity, although snap may be buying a cogent chunk... although when that happened speeds went up. it was within a few monthos of that telstraclear unlimited weekend iirc. telstraclear in general can have variable routes. like if you trace to two snap ip addresses you can get two diferrent paths, even on the same subnet. --- 202.37.101.1 ping statistics --- 10 packets transmitted, 10 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 126.688/126.790/126.913/0.483 ms --- 202.37.101.2 ping statistics --- 10 packets transmitted, 10 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 143.895/144.030/144.161/0.457 ms Although it looks like .2 is in Christchurch, and .1 in Auckland, the route is clearly different within the telstraglobal network. to .2: 5 po5-40G.ar3.LAX2.gblx.net (67.16.141.170) 0.757 ms 0.756 ms 0.661 ms 6 i-7-4-peer.eqla01.pr.telstraglobal.net (134.159.61.21) 0.708 ms 0.663 ms 0.686 ms 7 i-0-0-1-0.tlot-core01.bi.telstraglobal.net (202.84.251.169) 0.985 ms i-0-4-4-0.tlot-core01.bi.telstraglobal.net (202.40.149.133) 1.102 ms i-0-2-4-0.tlot-core01.bi.telstraglobal.net (202.40.149.129) 0.973 ms 8 i-0-1-0.hptw-core01.bx.telstraglobal.net (202.84.142.105) 133.727 ms 141.732 ms 133.168 ms 9 unknown.telstraglobal.net (134.159.174.42) 129.734 ms 129.762 ms 132.934 ms 10 xe-0-3-0-1037.mdr.core.snap.net.nz (111.69.27.66) 130.26 ms 130.261 ms 130.441 ms 11 * * * 12 ae0-100.d21.core.snap.net.nz (202.37.101.62) 144.876 ms 144.922 ms 144.885 ms to .1: 5 po5-40G.ar3.LAX2.gblx.net (67.16.141.170) 0.741 ms 9.626 ms 87.823 ms 6 i-1-4-peer.eqla01.pr.telstraglobal.net (134.159.63.201) 0.802 ms 0.692 ms 0.627 ms 7 i-0-2-4-0.tlot-core01.bi.telstraglobal.net (202.40.149.129) 1.274 ms i-0-0-0-0.tlot-core01.bi.telstraglobal.net (202.84.251.193) 1.82 ms i-0-0-1-0.tlot-core01.bi.telstraglobal.net (202.84.251.169) 0.977 ms 8 i-2-2-0.hptw-core01.bx.telstraglobal.net (202.84.142.117) 126.409 ms 126.464 ms 126.421 ms 9 unknown.telstraglobal.net (134.159.174.42) 125.196 ms 125.226 ms 125.526 ms 10 xe-0-3-0-1037.mdr.core.snap.net.nz (111.69.27.66) 125.400 ms 125.439 ms 125.314 ms it's only 5 msec in this example, but sometimes the routes can be more significantly different. and yeah, that route is non-cogent, so it's better, especially from los angeles.

Kiwiownage

37 posts

Geek

Reply # 744190 13-Jan-2013 20:05
Issues back now, back to 250 ping to US Tracing route to 12.129.254.216 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1] 2 8 ms 7 ms 9 ms 20.17.69.111.static.snap.net.nz [111.69.17.20] 3 26 ms 8 ms 8 ms 24.17.69.111.static.snap.net.nz [111.69.17.24] 4 * * * Request timed out. 5 * * * Request timed out. 6 22 ms 22 ms 22 ms xe-0-3-0-1037.mdr.core.snap.net.nz [111.69.27.66 ] 7 22 ms 21 ms 31 ms 111-69-27-65.core.snap.net.nz [111.69.27.65] 8 145 ms 144 ms 145 ms te7-3.ccr01.sjc05.atlas.cogentco.com [38.122.92. 105] 9 173 ms 174 ms 173 ms te0-3-0-7.ccr22.sjc01.atlas.cogentco.com [154.54 .6.69] 10 158 ms 158 ms 159 ms te0-2-0-1.ccr22.lax01.atlas.cogentco.com [154.54 .5.70] 11 185 ms 184 ms 185 ms 154.54.88.193 12 200 ms 199 ms 199 ms att.lax05.atlas.cogentco.com [154.54.11.10] 13 232 ms 229 ms 227 ms cr1.la2ca.ip.att.net [12.122.84.202] 14 286 ms 212 ms 228 ms gar29.la2ca.ip.att.net [12.122.129.241] 15 226 ms 227 ms 228 ms 12.122.251.190 16 202 ms 197 ms 200 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.12 9.193.250]

1 | 2