Ping problems on Blizzards end

Support Technical Support
1

I Ran Battle.net looking Glass. Results below.

TRACEROUTE:
traceroute to 73.113.147.67 (73.113.147.67), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.272 ms 0.266 ms 0.565 ms
2 24.105.18.2 (24.105.18.2) 0.577 ms 0.661 ms 0.725 ms
3 137.221.105.10 (137.221.105.10) 0.871 ms 0.881 ms 0.904 ms
4 137.221.66.20 (137.221.66.20) 0.798 ms 0.802 ms 0.802 ms
5 137.221.83.84 (137.221.83.84) 1398.090 ms 1398.142 ms 1398.153 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 6.102 ms 6.128 ms 6.446 ms
8 be-102-pe12.600wseventh.ca.ibone.comcast.net (75.149.229.69) 6.210 ms 6.272 ms 6.319 ms
9 be-3112-cs01.losangeles.ca.ibone.comcast.net (96.110.33.65) 6.712 ms 6.606 ms 6.629 ms
10 be-1112-cr12.losangeles.ca.ibone.comcast.net (96.110.45.166) 5.931 ms 5.758 ms 5.823 ms
11 be-301-cr13.houston.tx.ibone.comcast.net (96.110.37.185) 32.503 ms 32.688 ms 32.662 ms
12 be-1413-cs04.houston.tx.ibone.comcast.net (96.110.46.153) 33.022 ms 32.707 ms 32.567 ms
13 be-1412-cr12.houston.tx.ibone.comcast.net (96.110.46.150) 32.539 ms 32.538 ms 32.821 ms
14 be-302-cr14.56marietta.ga.ibone.comcast.net (96.110.39.209) 44.348 ms 44.565 ms 44.836 ms
15 be-1114-cs01.56marietta.ga.ibone.comcast.net (96.110.34.241) 45.409 ms 45.055 ms 45.012 ms

03/08/2021 01:31:55 UTC

PING:
PING 73.113.147.67 (73.113.147.67) 56(84) bytes of data.
64 bytes from 73.113.147.67: icmp_seq=1 ttl=49 time=67.2 ms
64 bytes from 73.113.147.67: icmp_seq=2 ttl=49 time=70.0 ms
64 bytes from 73.113.147.67: icmp_seq=3 ttl=49 time=77.9 ms
64 bytes from 73.113.147.67: icmp_seq=4 ttl=49 time=68.6 ms

— 73.113.147.67 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 67.272/70.985/77.960/4.145 ms

03/08/2021 01:31:55 UTC

MTR:
Start: Tue Aug 3 01:31:55 2021 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.5 0.0
2.|-- 24.105.18.130 0.0% 10 9.6 5.3 0.5 22.4 7.8
3.|-- 137.221.105.10 0.0% 10 0.8 0.9 0.8 1.1 0.0
4.|-- 137.221.66.20 0.0% 10 0.5 6.7 0.5 62.1 19.4
5.|-- 137.221.83.84 0.0% 10 207.9 758.9 203.7 1613. 535.3
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.68.32 0.0% 10 6.0 7.8 5.9 18.0 4.0
8.|-- be-102-pe12.600wseventh.ca.ibone.comcast.net 0.0% 10 6.7 6.8 6.7 7.1 0.0
9.|-- be-3412-cs04.losangeles.ca.ibone.comcast.net 0.0% 10 7.0 6.8 6.5 7.2 0.0
10.|-- be-1412-cr12.losangeles.ca.ibone.comcast.net 0.0% 10 7.0 6.7 6.3 7.1 0.0
11.|-- be-302-cr13.houston.tx.ibone.comcast.net 0.0% 10 32.8 33.1 32.5 35.5 0.7
12.|-- be-1113-cs01.houston.tx.ibone.comcast.net 0.0% 10 33.3 33.1 32.6 33.4 0.0
13.|-- be-1112-cr12.houston.tx.ibone.comcast.net 0.0% 10 33.3 33.1 32.7 33.3 0.0
14.|-- be-301-cr14.56marietta.ga.ibone.comcast.net 0.0% 10 44.6 44.6 44.4 44.8 0.0
15.|-- be-1114-cs01.56marietta.ga.ibone.comcast.net 0.0% 10 45.4 45.3 45.0 45.7 0.0
16.|-- 96.110.43.82 0.0% 10 60.9 55.0 50.7 68.9 6.0
17.|-- 162.151.94.94 0.0% 10 61.7 63.3 58.4 91.5 10.1
18.|-- 68.85.171.94 0.0% 10 59.3 59.4 59.3 59.5 0.0
19.|-- 96.110.189.62 0.0% 10 58.9 59.0 58.9 59.2 0.0
20.|-- c-73-113-147-67.hsd1.tn.comcast.net 0.0% 10 70.0 69.6 68.1 70.7 0.6

03/08/2021 01:31:55 UTC

2

To add to the above, Aldirick is a guildie and both he and his girlfriend have been having major disconnect issues with battle.net, the launcher, the forums and the game starting last night but no issues outside of that. I haven’t had the same issues myself, but am including my looking glass details below none the less. I had noticed step 5 of the tracert having insanely high ms numbers on mine as well as much higher on theirs and in looking up the ip address it shows as owned by blizzard. For whatever reason, in my test the ping failed entirely even though I was not having actual connection issues.

TRACEROUTE:
traceroute to 184.56.211.77 (184.56.211.77), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.365 ms 0.355 ms 0.354 ms
2 24.105.18.130 (24.105.18.130) 0.663 ms 0.719 ms 0.843 ms
3 137.221.105.14 (137.221.105.14) 0.882 ms 0.892 ms 0.894 ms
4 137.221.66.22 (137.221.66.22) 1.443 ms 1.462 ms 1.463 ms
5 137.221.83.86 (137.221.83.86) 493.115 ms 493.151 ms 493.154 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 6.072 ms 5.825 ms 5.807 ms
8 24.30.201.94 (24.30.201.94) 5.353 ms 5.447 ms 5.437 ms
9 66.109.5.134 (66.109.5.134) 52.487 ms 49.997 ms 50.129 ms
10 bu-ether16.chctilwc00w-bcr00.tbone.rr.com (66.109.6.226) 45.439 ms 45.470 ms 47.015 ms
11 be1.clmkohpe01r.midwest.rr.com (66.109.6.69) 55.441 ms 55.461 ms 61.371 ms
12 be1.pltsohae01r.midwest.rr.com (65.29.1.29) 59.528 ms 59.572 ms 59.675 ms
13 24.33.103.51 (24.33.103.51) 557.087 ms 554.780 ms 554.726 ms
14 agg2.akrnohbr02m.neo.rr.com (24.164.98.46) 59.105 ms 59.132 ms 59.106 ms
15 * * *

03/08/2021 01:26:20 UTC

PING:
PING 184.56.211.77 (184.56.211.77) 56(84) bytes of data.

— 184.56.211.77 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3009ms

03/08/2021 01:26:19 UTC

MTR:
Start: Tue Aug 3 01:26:19 2021 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.3 0.0
2.|-- 24.105.18.130 0.0% 10 0.6 0.6 0.5 0.6 0.0
3.|-- 137.221.105.14 0.0% 10 0.8 0.9 0.8 1.0 0.0
4.|-- 137.221.66.22 0.0% 10 0.5 0.5 0.4 0.7 0.0
5.|-- 137.221.83.86 0.0% 10 341.3 531.9 48.0 1123. 341.4
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.68.32 0.0% 10 5.9 13.0 5.9 54.1 14.8
8.|-- 24.30.201.94 0.0% 10 5.6 6.3 5.4 13.1 2.3
9.|-- 66.109.5.134 0.0% 10 48.8 48.1 45.2 51.5 2.2
10.|-- bu-ether16.chctilwc00w-bcr00.tbone.rr.com 0.0% 10 45.4 45.4 45.2 45.7 0.0
11.|-- be1.clmkohpe01r.midwest.rr.com 0.0% 10 57.1 59.3 56.1 62.3 2.1
12.|-- be1.pltsohae01r.midwest.rr.com 0.0% 10 59.5 59.7 59.5 60.0 0.0
13.|-- 24.33.103.51 0.0% 10 71.3 101.8 70.0 295.3 69.6
14.|-- agg2.akrnohbr02m.neo.rr.com 0.0% 10 59.3 59.2 59.0 60.1 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

03/08/2021 01:26:19 UTC

3

None of the tests in this thread are showing issues. I recommend following the steps provided in the pinned thread for “What to do if you need more help” and running a WinMTR from the affected location.

1 Like
4

Thanks Elocin for reading the info Carnest and Aldirick posted. I’m the girlfriend mentioned. I’ve spent literally hours trying to TS this issue in conjunction with the above gentlemen.

Let me point out the numbers. Line 5 of the tracert is showing some fairish lag on Aldirick’s post, less on Carnests. Both have about a 3000 ms ping. But wait…there’s an MTR as well…that’s what looking glass does, shows connection issues between Blizzard and user.

In addition I have personally done ALL TS steps listed in the article you mentioned. This is the first time in 4 days I’ve been able to access the actual forums.

I’ve rebooted, reset routers and modems, checked cables, checked for updated drivers, attempted to patch wow and when that failed to get anywhere I reinstalled it. The issue is not at my end. Categorically. Emphatically. Aldirick has not gone to the same extreme because he’s had less time available to deal with it.

What I’m looking for is ideas I haven’t tried. In a perfect world I’d like solutions because this is costing me gold/play time. This game is a part of my therapy.

ok back to signing in and failing…again

5

if you’ve already tried the generic troubleshooting steps like a full UI reset and rebooting router etc, then posting a winmtr is the next step. the information it provides is different from the looking glass.

1 Like
6

Latency on the last line of both the traceroute and the MTR are very normal. The concerning part of the test is the ping. When Blizzard tries to ping the computer, the data is leaving Blizzard’s server but being lost within the ISP network or at the endpoint. In other words, there’s nothing demonstrating an issue coming from Blizzard’s end in these tests. I have no motivation to make Blizzard look better, and I would absolutely point out the issue if I saw one on their end.

A WinMTR is part of the troubleshooting process (pinned at top of forum), so I recommend adding that. Additionally, not being able to access the forum is only further pointing to an ISP/routing issue, as there has been no forum downtime.

To be fair, connection troubleshooting is something Blizzard offers as a courtesy only, with no guarantee to figure out what’s causing any specific issue. However, if you’re unsatisfied with the help from the community, I highly recommend utilizing the ticket system to reach their staff instead. You will need to run a WinMTR for the ticket process, as well.

2 Likes
7

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 10.0.0.1 - 0 | 317 | 317 | 1 | 16 | 136 | 6 |

| 96.120.108.61 - 1 | 313 | 312 | 8 | 16 | 89 | 13 |

| 96.110.189.61 - 0 | 317 | 317 | 9 | 17 | 99 | 15 |

| 68.85.171.93 - 0 | 317 | 317 | 9 | 19 | 124 | 16 |

| 162.151.94.93 - 1 | 313 | 312 | 17 | 25 | 101 | 22 |

|be-33122-cs02.56marietta.ga.ibone.comcast.net - 0 | 317 | 317 | 24 | 32 | 134 | 31 |

|be-2212-pe12.56marietta.ga.ibone.comcast.net - 0 | 317 | 317 | 23 | 31 | 75 | 30 |

| 50.208.235.62 - 0 | 317 | 317 | 24 | 35 | 141 | 29 |

| ae1-br01-eqat2.as57976.net - 0 | 317 | 317 | 35 | 45 | 146 | 39 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| et-0-0-1-pe02-eqch2.as57976.net - 1 | 313 | 312 | 33 | 44 | 107 | 40 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 64 | 0 | 0 | 0 | 0 | 0 |

|____________|||||||

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

I’ve got perfect connection to facebook, youtube, reddit, twitter
I can send and receive email flawlessly.
I can’t stay in game long enough to create a ticket.
17 disconnects in ten minutes
5 DC’s while doing this test.

8

I probably should have asked earlier, but no one has defined what “ping problems” actually refers to. Are we talking pings into the thousands? Or just over 140? Because the 140 is definitely showing up in the WinMTR.

Unfortunately, this does look to be a problem with the home equipment or the line coming in. The average ping and worst ping on the first hop (router/modem) are much higher than you’d want to see. Normally, you’d want the average to be around 1-3ms, and the worst should really be no higher than 10ms (but it’s 136ms).

Websites and streaming services are not going to be good connection comparisons. None of these services use the same data transfer rate as WoW (60 packets/second). Auto-updating elements on web pages (like Facebook comments) are not going to be affected by blips in latency like the ones in the test. And streaming services (YouTube) buffer data ahead of time to prevent interruptions in playback.

Ultimately, your best path forward is to send these results to your ISP and ask them to look into the line and your equipment. A technician will likely need to come out and physically hook up a meter to accomplish this.

1 Like