Being routed through NJ to get to the Midwest... when I'm already in the midwest

Tracing route to over a maximum of 30 hops

1 <1 ms <1 ms <1 ms
2 2 ms 2 ms 2 ms stpl-dsl-gw21.stpl.qwest []
3 3 ms 8 ms 5 ms stpl-agw1.inet.qwest []
4 3 ms 2 ms 2 ms 216-160-19-2.mpls.qwest []
5 2366 ms * * ae-2-3602.ear3.Washington1.Level3 []
6 29 ms 29 ms 29 ms BLIZZARD-EN.ear3.Washington1.Level3 []
7 30 ms 29 ms 29 ms ae1-br01-eqdc2.as57976 []
8 30 ms 30 ms 35 ms et-0-0-2-br01-eqch2.as57976 []
9 34 ms 30 ms 29 ms be1-pe01-eqch2.as57976 []
10 34 ms 31 ms 33 ms chi-eqch2-ia-bons-02.as57976 []
11 30 ms 30 ms 31 ms

Trace complete.

My ISP says there is nothing they can do, and this only started happening after service was restored on Monday. My ISP is Centurylink and they claim they have no control over that node but the own it…

Also had to remove every dot net to post, all addresses had a dot net.

Hey Demo,

I’m not seeing any serious problems in the test, and it looks like you are getting around 30ms to the Overwatch servers. Unless you are seeing high latency in-game, I don’t think this is something to worry about.

The 2400ms at the one node is normal? Also being routed through washington while in MN to connect to chicago makes sense to you? I am normally at 11ms. Tripling my MS doesn’t feel good at all, even if you think it’s fine.

Or the fact that if I use a VPN I’m at 20ms.

The 2400ms is due to ICMP throttling, and would only affect ping tests. Game data would pass through normally without being throttled. If it was affecting all data, you would consistently see 2400ms latency on every hop.

If the VPN helps, that would indicate that there is some kind of ISP routing that is sending you to another data center that is farther away.

You could try using a public DNS (such as Google DNS) which could help but otherwise this is something that the ISP needs to investigate. If your ISP wants to reach out to our Network team and discuss this further, they can find our peering contact information here.