There goes last minute timewalking, I guess. =[
I mean it isn’t Blizz’s fault - its Verizon’s.
In the game for 10 minutes and disconnected again. Broke my 11 key. This has to stop. VPN is only a bandaid.
Disconnected again. Stuck on logging in to game server.
Blizz needs to speak with Verizon ASAP. High level technician stuff or whatever.
1 Like
Ok here is a traceroute to Pagle when it was working:
TRACEROUTE:
traceroute to 173.63.112.80 (173.63.112.80), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.595 ms 1.594 ms 1.566 ms
2 24.105.18.3 (24.105.18.3) 1.574 ms 1.606 ms 1.623 ms
3 137.221.105.16 (137.221.105.16) 1.585 ms 1.594 ms 1.597 ms
4 137.221.66.22 (137.221.66.22) 3.070 ms 3.057 ms 3.063 ms
5 137.221.83.68 (137.221.83.68) 8.534 ms 8.537 ms 8.538 ms
6 137.221.65.68 (137.221.65.68) 65.832 ms 58.985 ms 58.945 ms
7 137.221.68.32 (137.221.68.32) 6.098 ms 5.902 ms 5.893 ms
8 las-b21-link.telia.net (62.115.178.200) 5.638 ms 5.643 ms 5.628 ms
9 xe-5-3-2.BR3.LAX15.ALTER.NET (152.179.21.77) 5.685 ms 5.729 ms 5.722 ms
10 * * *
11 ae203-0.NWRKNJ-VFTTP-306.verizon-gni.net (100.41.205.99) 61.992 ms 60.973 ms 60.904 ms
12 pool-173-63-112-80.nwrknj.fios.verizon.net (173.63.112.80) 64.911 ms 64.910 ms 64.734 ms
19/11/2019 03:17:12 UTC
--------------------
TRACEROUTE:
traceroute to 173.63.112.80 (173.63.112.80), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.383 ms 0.388 ms 0.392 ms
2 24.105.18.3 (24.105.18.3) 0.687 ms 1.347 ms 1.393 ms
3 137.221.105.16 (137.221.105.16) 0.874 ms 0.906 ms 1.340 ms
4 137.221.66.22 (137.221.66.22) 1.326 ms 1.490 ms 1.508 ms
5 137.221.83.68 (137.221.83.68) 5.474 ms 5.483 ms 5.521 ms
6 137.221.65.68 (137.221.65.68) 61.759 ms 59.082 ms 59.198 ms
7 137.221.68.32 (137.221.68.32) 8.107 ms 7.208 ms 7.212 ms
8 las-b21-link.telia.net (62.115.178.200) 6.211 ms 6.227 ms 6.253 ms
9 xe-5-3-2.BR3.LAX15.ALTER.NET (152.179.21.77) 6.264 ms 6.307 ms 6.321 ms
10 * * *
11 ae203-0.NWRKNJ-VFTTP-306.verizon-gni.net (100.41.205.99) 61.022 ms 61.047 ms 61.178 ms
12 pool-173-63-112-80.nwrknj.fios.verizon.net (173.63.112.80) 66.129 ms 66.166 ms 66.291 ms
19/11/2019 03:17:12 UTC
--------------------
PING:
PING 173.63.112.80 (173.63.112.80) 56(84) bytes of data.
64 bytes from 173.63.112.80: icmp_seq=1 ttl=51 time=65.2 ms
64 bytes from 173.63.112.80: icmp_seq=2 ttl=51 time=66.0 ms
64 bytes from 173.63.112.80: icmp_seq=3 ttl=51 time=64.0 ms
64 bytes from 173.63.112.80: icmp_seq=4 ttl=51 time=64.7 ms
--- 173.63.112.80 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 64.099/65.052/66.064/0.736 ms
19/11/2019 03:17:12 UTC
--------------------
PING:
PING 173.63.112.80 (173.63.112.80) 56(84) bytes of data.
64 bytes from 173.63.112.80: icmp_seq=1 ttl=51 time=62.8 ms
64 bytes from 173.63.112.80: icmp_seq=2 ttl=51 time=63.7 ms
64 bytes from 173.63.112.80: icmp_seq=3 ttl=51 time=66.8 ms
64 bytes from 173.63.112.80: icmp_seq=4 ttl=51 time=62.1 ms
--- 173.63.112.80 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 62.195/63.911/66.823/1.780 ms
19/11/2019 03:17:12 UTC
--------------------
MTR:
Start: Tue Nov 19 03:17:12 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.5 0.0
2.|-- 24.105.18.3 0.0% 10 0.6 0.9 0.5 2.2 0.3
3.|-- 137.221.105.16 0.0% 10 0.8 1.1 0.8 2.5 0.3
4.|-- 137.221.66.22 0.0% 10 1.0 1.3 0.9 2.7 0.5
5.|-- 137.221.83.68 0.0% 10 2.4 5.4 2.4 10.4 2.6
6.|-- 137.221.65.68 0.0% 10 6.0 9.5 5.8 25.3 6.7
7.|-- 137.221.68.32 0.0% 10 6.2 6.1 5.9 6.7 0.0
8.|-- las-b21-link.telia.net 0.0% 10 5.7 5.8 5.5 6.1 0.0
9.|-- xe-5-3-2.BR3.LAX15.ALTER.NET 0.0% 10 8.2 6.0 5.6 8.2 0.7
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ae203-0.NWRKNJ-VFTTP-306.verizon-gni.net 0.0% 10 60.9 63.5 60.7 79.5 5.9
12.|-- pool-173-63-112-80.nwrknj.fios.verizon.net 0.0% 10 62.2 63.6 62.2 65.5 0.9
19/11/2019 03:17:12 UTC
--------------------
MTR:
Start: Tue Nov 19 03:17:13 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.6 0.0
2.|-- 24.105.18.3 0.0% 10 0.5 0.6 0.5 0.9 0.0
3.|-- 137.221.105.16 0.0% 10 0.7 1.0 0.7 1.3 0.0
4.|-- 137.221.66.22 0.0% 10 1.1 1.0 0.9 1.2 0.0
5.|-- 137.221.83.68 0.0% 10 1.0 8.8 1.0 44.1 12.6
6.|-- 137.221.65.68 0.0% 10 5.7 7.9 5.6 20.2 4.7
7.|-- 137.221.68.32 0.0% 10 5.8 11.5 5.8 61.9 17.7
8.|-- las-b21-link.telia.net 0.0% 10 5.9 5.7 5.5 5.9 0.0
9.|-- xe-5-3-2.BR3.LAX15.ALTER.NET 0.0% 10 5.7 5.8 5.7 6.1 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ae203-0.NWRKNJ-VFTTP-306.verizon-gni.net 0.0% 10 61.4 64.2 60.7 79.0 6.4
12.|-- pool-173-63-112-80.nwrknj.fios.verizon.net 0.0% 10 65.5 64.1 62.1 66.1 1.4
19/11/2019 03:17:12 UTC
--------------------
[/details]
And here’s when it is not:
TRACEROUTE:
traceroute to 173.63.112.80 (173.63.112.80), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.297 ms 0.304 ms 0.309 ms
2 24.105.18.3 (24.105.18.3) 0.657 ms 0.682 ms 0.817 ms
3 137.221.105.16 (137.221.105.16) 0.746 ms 0.818 ms 0.878 ms
4 137.221.66.22 (137.221.66.22) 1.018 ms 1.040 ms 1.048 ms
5 137.221.83.68 (137.221.83.68) 366.687 ms 366.725 ms 366.735 ms
6 137.221.65.68 (137.221.65.68) 62.531 ms 59.786 ms 59.761 ms
7 137.221.68.32 (137.221.68.32) 5.881 ms 5.959 ms 6.368 ms
8 las-b21-link.telia.net (62.115.178.200) 5.630 ms 5.744 ms 5.737 ms
9 xe-5-3-2.BR3.LAX15.ALTER.NET (152.179.21.77) 5.714 ms 5.622 ms 5.615 ms
10 * * *
11 ae203-0.NWRKNJ-VFTTP-306.verizon-gni.net (100.41.205.99) 60.613 ms 60.607 ms 60.616 ms
12 pool-173-63-112-80.nwrknj.fios.verizon.net (173.63.112.80) 64.572 ms 64.492 ms 64.202 ms
19/11/2019 03:24:46 UTC
--------------------
TRACEROUTE:
traceroute to 173.63.112.80 (173.63.112.80), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.648 ms 1.637 ms 1.636 ms
2 24.105.18.131 (24.105.18.131) 2.383 ms 2.402 ms 2.417 ms
3 137.221.105.16 (137.221.105.16) 2.403 ms 2.412 ms 2.478 ms
4 137.221.66.18 (137.221.66.18) 142.781 ms 142.791 ms 142.794 ms
5 137.221.83.66 (137.221.83.66) 578.690 ms 579.019 ms 579.046 ms
6 137.221.65.68 (137.221.65.68) 51.001 ms 46.621 ms 46.594 ms
7 137.221.68.32 (137.221.68.32) 6.043 ms 6.007 ms 6.043 ms
8 las-b21-link.telia.net (62.115.178.200) 5.634 ms 5.554 ms 5.517 ms
9 xe-5-3-2.BR3.LAX15.ALTER.NET (152.179.21.77) 5.620 ms 5.570 ms 5.511 ms
10 * * *
11 ae203-0.NWRKNJ-VFTTP-306.verizon-gni.net (100.41.205.99) 60.829 ms 60.747 ms 60.493 ms
12 pool-173-63-112-80.nwrknj.fios.verizon.net (173.63.112.80) 63.352 ms 60.921 ms 65.285 ms
19/11/2019 03:24:46 UTC
--------------------
PING:
PING 173.63.112.80 (173.63.112.80) 56(84) bytes of data.
64 bytes from 173.63.112.80: icmp_seq=1 ttl=51 time=65.7 ms
64 bytes from 173.63.112.80: icmp_seq=2 ttl=51 time=65.6 ms
64 bytes from 173.63.112.80: icmp_seq=3 ttl=51 time=65.4 ms
64 bytes from 173.63.112.80: icmp_seq=4 ttl=51 time=62.6 ms
--- 173.63.112.80 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 62.688/64.883/65.717/1.270 ms
19/11/2019 03:24:46 UTC
--------------------
PING:
PING 173.63.112.80 (173.63.112.80) 56(84) bytes of data.
64 bytes from 173.63.112.80: icmp_seq=1 ttl=51 time=63.0 ms
64 bytes from 173.63.112.80: icmp_seq=2 ttl=51 time=65.1 ms
64 bytes from 173.63.112.80: icmp_seq=3 ttl=51 time=65.0 ms
64 bytes from 173.63.112.80: icmp_seq=4 ttl=51 time=62.0 ms
--- 173.63.112.80 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 62.015/63.836/65.158/1.362 ms
19/11/2019 03:24:46 UTC
--------------------
MTR:
Start: Tue Nov 19 03:24:46 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.3 0.0
2.|-- 24.105.18.3 0.0% 10 0.6 0.7 0.5 1.4 0.0
3.|-- 137.221.105.16 0.0% 10 1.0 0.9 0.7 1.7 0.0
4.|-- 137.221.66.22 0.0% 10 0.9 8.3 0.9 55.9 17.4
5.|-- 137.221.83.68 0.0% 10 2.0 104.0 2.0 547.8 166.9
6.|-- 137.221.65.68 0.0% 10 5.9 18.4 5.7 107.9 31.8
7.|-- 137.221.68.32 0.0% 10 6.0 9.5 5.8 40.3 10.8
8.|-- las-b21-link.telia.net 0.0% 10 5.9 5.7 5.4 5.9 0.0
9.|-- xe-5-3-2.BR3.LAX15.ALTER.NET 0.0% 10 5.7 5.7 5.6 6.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ae203-0.NWRKNJ-VFTTP-306.verizon-gni.net 0.0% 10 60.6 60.8 60.6 61.3 0.0
12.|-- pool-173-63-112-80.nwrknj.fios.verizon.net 0.0% 10 66.1 64.2 62.0 66.4 1.4
19/11/2019 03:24:46 UTC
--------------------
MTR:
Start: Tue Nov 19 03:24:46 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.2 0.4 0.0
2.|-- 24.105.18.131 0.0% 10 0.7 0.6 0.5 0.7 0.0
3.|-- 137.221.105.16 0.0% 10 0.8 0.8 0.7 1.0 0.0
4.|-- 137.221.66.18 0.0% 10 0.9 12.4 0.9 61.8 20.1
5.|-- 137.221.83.66 0.0% 10 1.1 81.0 1.1 347.3 113.5
6.|-- 137.221.65.68 0.0% 10 5.9 12.2 5.7 62.8 17.8
7.|-- 137.221.68.32 0.0% 10 6.0 12.3 5.8 53.6 15.3
8.|-- las-b21-link.telia.net 0.0% 10 5.8 7.1 5.5 18.2 3.9
9.|-- xe-5-3-2.BR3.LAX15.ALTER.NET 0.0% 10 5.8 6.4 5.6 10.8 1.4
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ae203-0.NWRKNJ-VFTTP-306.verizon-gni.net 0.0% 10 60.6 60.8 60.6 61.4 0.0
12.|-- pool-173-63-112-80.nwrknj.fios.verizon.net 0.0% 10 63.1 62.9 61.4 64.7 1.0
19/11/2019 03:24:46 UTC
--------------------
2 Likes
Has anybody had success talking to Blizzard or Verizon support? Blizzard support told me they can’t even run a connection test because it’s ipv6. Verizon support told me there is absolutely nothing wrong with my connection. Wanted me to pay $15 for advanced technical support. I am calling billing tomorrow when the billing line opens and telling them I am switching to comcast if they don’t offer the advanced technical support for free.
2 Likes
How so? Blizzard is literally the only thing that does not work for us. Everything else internet wise works on Verizon except blizzard.
4 Likes
I’m curious as to the experience others are facing when attempting to do a speed test through Verizon. When this issue pops up for me, the router speed test goes through without issue; but the device speed test either fails, or tells me to check my connection because it’s not working. I have a friend a mile down the road who is getting the same thing.
///verizon.com/speedtest/
Also having the same issue here
have tracert and other info if needed
managed to log on once but then once I tried to swap toons or log back in I couldn’t
no they both dont give a s**t
VPN definitely works, but this is just a temporary fix.
and you gotta pay $10/mo for VPN
There are some free ones with limited bandwidth.
Fios, Southern NJ. Mt issue is that I stay logged in as far as chat, and other players can see me, however mobs stop spawning and to everyone else it looks like I’m running on foot at mount speed. Worried I could get in trouble for it looking like I’m breaking the game, though I can’t interact with anything I only get chat updates on my end. Never experienced anything like it.
1 Like
Verizon is trying to charge me $100 to have some service rep come check out the issues. WTF
Same issue as above. Fios. Central/northern NJ. Chat sometimes works, sometimes chat goes down first. Blizz GM says its on Fios end. Need information to tell Fios, what is the underlying cause here??
Yeah they want to send a technician out. No sense in doing that since i’m clearly not the only one suffering from this malaise
yeah they last for about 25 mins
And there’s the bad hop. Called it.
1 Like
just tried to log in on retail client (had been trying to get into classic) and i got stuck at the usual “logging in to game server”… but when i tried on the retail client on an account without an active subscription it brought me through into the character select screen (but was completely black)… just found it weird they weren’t getting stuck in the same spot