Bad Hop only on A52 server at ae1-br01-eqla1.as57976.net

Only having high latency issue with the A52 server, called my ISP & went through the port forwarding/router reset & nothing changes. This is the only game & only server i have high LAT on, every other game typically runs under 10LAT/ping & so do other servers. Issue recently popped up within the last couple months. Have friends that live in the same area with worse internet than me & they have better LAT to this server.
WinMTR below:

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
dsldevice.attlocal.net 0 114 114 0 0 6 0
23-125-216-1.lightspeed.irvnca.sbcglobal.net 0 114 114 1 1 6 2
70.232.229.60 0 114 114 2 2 6 3
12.242.115.33 0 114 114 3 3 5 4
12.245.64.10 0 114 114 3 9 126 14
ae1-br01-eqla1.as57976.net 0 111 111 53 275 3078 274
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
et-0-0-0-pe02-evch1.as57976.net 0 114 114 51 52 81 52
137.221.67.65 0 114 114 51 51 53 52
10.108.6.35 0 114 114 49 49 52 50
10.108.194.99 0 114 114 51 51 53 52
10.22.0.2 0 114 114 49 50 53 51
66.40.178.54 0 114 114 51 53 277 52

Your test was run to a Blizzard IP I don’t recognize in Los Angeles, which is not the location of their game servers anymore. West coast servers moved to Las Vegas earlier this year. Is the IP from the Bnet connection, or how did you gather it?

Which other servers are you playing on?

Took it from the network section in resource monitor, the IP changed as i changed servers & reflected same LAT as in-game. Hopped on Boulderfist & was running 3-5.

Okay, going to elaborate on the ae1-br01-eqla1.as57976.net hop. Basically, ignore it. I know that sounds crazy, but the data on the hops after it are completely unaffected by a full 3-second-long (3078ms) response time. The high number is only occurring because the node is ignoring ICMP data (this test) as a DDoS protection mechanism. If the 3-second delay was real, you would not be able to login to WoW, let alone play.

The test shows your ping to the server is 53ms. If you’re in California and the connection is being routed to Chicago before it goes back to Las Vegas, that will create a higher ping value. Unfortunately, the only remedy is to use a VPN until the route gets reverted/fixed by the ISP. SBCGlobal runs into this issue every few months.

Unfortunate but got it, appreciate the quick response & help here!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.