I have had this issue for 1-2 weeks, tried 2 routers with power cycling, speed tests came out fine, did all the thigns gms said back and forth over and over until they sent me here
location: waxahachie texas
game: world of warcraft
not sure how to attach my pathping or traceart here but its in my tickets
~also feeling the frustration of paying 2 people for a service I can not use
Sounds like you’ll be someone that falls into the Dallas connection issue that’s been ongoing.
They’ve been collecting data there from those affected.
I contacted support 2 weeks ago (weekend between Black Friday and Cyber Monday) and, after doing the traceroute, had a suspicion it was Level 3 in Dallas that was the issue. The GM also suspected it and this thread is definitely confirmation. I don’t think I can access any us.battle.net page except through VPN at the moment.
It’s a bit frustrating that Level 3 is taking so long to fix their issue. I guess it’s good timing that I’m burned out from WoW, and playing other games in the meantime, if this is also affecting pings in-game (at the time of my first ticket, that wasn’t the case).
PS: This new forum setup is a downgrade. 
I am in Missouri using Fidelity communications. Having same problem, as anything battle.net seems to be a no-go. Other network suggestion (mobile data) works. This has been an issue for several weeks.
Traceroute:
Tracing route to us.battle.net [24.105.29.40]
over a maximum of 30 hops:
1 10 ms 12 ms 24 ms 72-172-211-1.fidnet.com [72.172.211.1]
2 41 ms 17 ms 42 ms nwhnmo1-te00039.fidnet.com [216.229.74.52]
3 13 ms 15 ms 14 ms stlsmo2-te0005.fidnet.com [216.229.74.54]
4 23 ms 41 ms 69 ms v516.core1.stl1.he.net [184.105.18.185]
5 33 ms 59 ms 35 ms 100ge5-1.core2.chi1.he.net [184.105.213.237]
6 21 ms 21 ms 21 ms 206.108.115.62
7 91 ms 96 ms 99 ms ae1-br02-eqch2.as57976.net [137.221.69.35]
8 65 ms 65 ms 73 ms et-0-0-3-br02-eqla1.as57976.net [137.221.65.4]
9 83 ms 71 ms 72 ms be2-pe02-eqla1.as57976.net [137.221.68.73]
10 82 ms 89 ms 89 ms lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
11 65 ms 65 ms 64 ms 10.104.5.40
12 80 ms 77 ms 70 ms 24.105.29.40
Trace complete.
Pathping:
Tracing route to us.battle.net [24.105.29.40]
over a maximum of 30 hops:
0 DESKTOP-NKD6FKA [192.168.0.112]
1 72-172-211-1.fidnet.com [72.172.211.1]
2 nwhnmo1-te00039.fidnet.com [216.229.74.52]
3 stlsmo2-te0005.fidnet.com [216.229.74.54]
4 v516.core1.stl1.he.net [184.105.18.185]
5 100ge5-1.core2.chi1.he.net [184.105.213.237]
6 206.108.115.62
7 ae1-br02-eqch2.as57976.net [137.221.69.35]
8 et-0-0-3-br02-eqla1.as57976.net [137.221.65.4]
9 be2-pe02-eqla1.as57976.net [137.221.68.73]
10 lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
11 10.104.5.40
12 24.105.29.40
Computing statistics for 300 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-NKD6FKA [192.168.0.112]
0/ 100 = 0% |
1 19ms 0/ 100 = 0% 0/ 100 = 0% 72-172-211-1.fidnet.com [72.172.211.1]
0/ 100 = 0% |
2 22ms 0/ 100 = 0% 0/ 100 = 0% nwhnmo1-te00039.fidnet.com [216.229.74.52]
0/ 100 = 0% |
3 22ms 0/ 100 = 0% 0/ 100 = 0% stlsmo2-te0005.fidnet.com [216.229.74.54]
0/ 100 = 0% |
4 21ms 0/ 100 = 0% 0/ 100 = 0% v516.core1.stl1.he.net [184.105.18.185]
0/ 100 = 0% |
5 31ms 0/ 100 = 0% 0/ 100 = 0% 100ge5-1.core2.chi1.he.net [184.105.213.237]
0/ 100 = 0% |
6 — 100/ 100 =100% 100/ 100 =100% 206.108.115.62
0/ 100 = 0% |
7 30ms 0/ 100 = 0% 0/ 100 = 0% ae1-br02-eqch2.as57976.net [137.221.69.35]
0/ 100 = 0% |
8 76ms 0/ 100 = 0% 0/ 100 = 0% et-0-0-3-br02-eqla1.as57976.net [137.221.65.4]
0/ 100 = 0% |
9 70ms 0/ 100 = 0% 0/ 100 = 0% be2-pe02-eqla1.as57976.net [137.221.68.73]
0/ 100 = 0% |
10 — 100/ 100 =100% 100/ 100 =100% lax-eqla1-ia-bons-03.as57976.net [137.221.66.7]
0/ 100 = 0% |
11 30ms 0/ 100 = 0% 0/ 100 = 0% 10.104.5.40
8/ 100 = 8% |
12 74ms 8/ 100 = 8% 0/ 100 = 0% 24.105.29.40
Trace complete.I am Fidelity also
I am also experiencing massive world ms lag spikes. My ISP is Blue Stream (South Florida).
Here is my traceroute and pingpath info:
Tracing route to us(dot)battle(dot)net [24.105.29.40]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.0.1
2 10 ms 8 ms 9 ms 10.135.0.1
3 10 ms 9 ms 9 ms vl-65-core1-wn.myacc(dot)net [24.233.167.114]
4 10 ms 14 ms 9 ms 45.42.62.45
5 10 ms 11 ms 11 ms 208.67.164.198
6 10 ms 11 ms 12 ms 208.67.164.180
7 15 ms 11 ms 10 ms 198.32.125.224
8 * 72 ms 72 ms ae1-br01-eqmi2.as57976(dot)net [137.221.76.33]
9 70 ms 70 ms 71 ms xe-0-0-1-1-br01-eqda6.as57976(dot)net [137.221.65.62]
10 72 ms 71 ms 71 ms et-0-0-2-br02-swlv10.as57976(dot)net [137.221.65.67]
11 70 ms 71 ms 72 ms 137.221.65.122
12 * * * Request timed out.
13 73 ms 72 ms 74 ms be1-pe01-eqla1.as57976(dot)net [137.221.68.67]
14 73 ms 72 ms 71 ms lax-eqla1-ia-bons-01.as57976(dot)net [137.221.66.1]
15 * * * Request timed out.
16 77 ms 71 ms 73 ms 24.105.29.40
Trace complete.
C:\WINDOWS\system32>pathping us(dot)battle(dot)net
Tracing route to us.battle.net [24.105.29.40]
over a maximum of 30 hops:
0 DESKTOP-GJ67R8V.utopia(dot)net [192.168.0.35]
1 192.168.0.1
2 10.135.0.1
3 vl-65-core1-wn.myacc(dot)net [24.233.167.114]
4 45.42.62.45
5 208.67.164.198
6 208.67.164.180
7 198.32.125.224
8 ae1-br01-eqmi2.as57976(dot)net [137.221.76.33]
9 xe-0-0-1-1-br01-eqda6.as57976(dot)net [137.221.65.62]
10 et-0-0-2-br02-swlv10.as57976(dot)net [137.221.65.67]
11 137.221.65.122
12 et-0-0-2-br01-eqla1.as57976(dot)net [137.221.65.68]
13 * be1-pe01-eqla1.as57976(dot)net [137.221.68.67]
14 lax-eqla1-ia-bons-01.as57976(dot)net [137.221.66.1]
15 * * *
Computing statistics for 350 seconds…
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-GJ67R8V(dot)utopia(dot)net [192.168.0.35]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
47/ 100 = 47% |
2 — 100/ 100 =100% 53/ 100 = 53% 10.135.0.1
0/ 100 = 0% |
3 9ms 94/ 100 = 94% 47/ 100 = 47% vl-65-core1-wn.myacc(dot)net [24.233.167.114]
0/ 100 = 0% |
4 10ms 47/ 100 = 47% 0/ 100 = 0% 45.42.62.45
0/ 100 = 0% |
5 10ms 95/ 100 = 95% 48/ 100 = 48% 208.67.164.198
0/ 100 = 0% |
6 12ms 48/ 100 = 48% 1/ 100 = 1% 208.67.164.180
0/ 100 = 0% |
7 — 100/ 100 =100% 53/ 100 = 53% 198.32.125.224
0/ 100 = 0% |
8 13ms 47/ 100 = 47% 0/ 100 = 0% ae1-br01-eqmi2.as57976(dot)net [137.221.76.33]
1/ 100 = 1% |
9 48ms 95/ 100 = 95% 47/ 100 = 47% xe-0-0-1-1-br01-eqda6.as57976(dot)net [137.221.65.62]
0/ 100 = 0% |
10 79ms 48/ 100 = 48% 0/ 100 = 0% et-0-0-2-br02-swlv10.as57976(dot)net [137.221.65.67]
0/ 100 = 0% |
11 73ms 95/ 100 = 95% 47/ 100 = 47% 137.221.65.122
0/ 100 = 0% |
12 77ms 48/ 100 = 48% 0/ 100 = 0% et-0-0-2-br01-eqla1.as57976(dot)net [137.221.65.68]
52/ 100 = 52% |
13 — 100/ 100 =100% 0/ 100 = 0% be1-pe01-eqla1.as57976(dot)net [137.221.68.67]
0/ 100 = 0% |
14 — 100/ 100 =100% 0/ 100 = 0% lax-eqla1-ia-bons-01.as57976(dot)net [137.221.66.1]
Trace complete.
Since hyperlinks cant be added, I removed all the periods and replaced them with “(dot)”
So Im using a free VPN and the problem is fixed. Didn’t think it would be that easy but I still would like to be on my normal isp address. Any idea what is causing this mess?
Hey all,
We tweaked some things about a half an hour ago now which should have fixed things. If you continue to have problems, can you post in the main thread on this - it’ll help us find any further issues.