Nice stall tactic. In other words even Blizzards own network operation center doesn’t know what the problem is.
I get stuck in the BG loading screens and sometimes Ic ant use abilities so I have to alt f4, wait for like 10 min, and then log back in. Is this all part of the same issue?
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms MyRouter [192.168.1.1]
2 5 ms 3 ms 3 ms 186-230-207-60.ded.intelignet.com.br [186.230.207.60]
3 4 ms 3 ms 3 ms 10.224.253.21
4 3 ms 4 ms 6 ms 10.224.91.213
5 23 ms 23 ms 23 ms 10.224.200.25
6 22 ms 21 ms 23 ms 10.229.248.217
7 27 ms 23 ms 23 ms 10.223.238.62
8 24 ms 23 ms 23 ms et2-0-0.sanpaolo2.spa.seabone.net [149.3.181.9]
9 155 ms 157 ms 156 ms et0-3-0.miami19.mia.seabone.net [89.221.41.161]
10 130 ms 136 ms 136 ms be6762.ccr21.mia03.atlas.cogentco.com [154.54.9.17]
11 128 ms 130 ms 129 ms be3401.ccr22.mia01.atlas.cogentco.com [154.54.47.29]
12 131 ms 129 ms 129 ms be3411.rcr21.b002802-2.mia01.atlas.cogentco.com [154.54.26.42]
13 128 ms 129 ms 129 ms te0-0-2-3.nr11.b002802-1.mia01.atlas.cogentco.com [154.24.43.42]
14 128 ms 178 ms 128 ms gi0-0-0-18.205.nr11.b002802-1.mia01.atlas.cogentco.com [38.104.90.5]
15 158 ms 157 ms 157 ms ae1-br01-eqmi2.as57976.net [137.221.76.33]
16 158 ms 160 ms 158 ms xe-0-0-0-1-br01-eqat2.as57976.net [137.221.65.50]
17 158 ms * * et-0-0-4-br02-eqch2.as57976.net [137.221.65.46]
18 158 ms 157 ms 157 ms be2-pe01-eqch2.as57976.net [137.221.69.71]
19 159 ms 161 ms 160 ms chi-eqch2-ia-bons-02.as57976.net [137.221.66.11]
20 159 ms 159 ms 159 ms 24.105.62.129
Trace complete.
just got pass login screen all black… im so sad today,
Is it true some can play? I have been unable to log in all day.
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Fios_Quantum_Gateway.local [192.168.1.1]
2 12 ms 8 ms 9 ms 24.105.30.129
Trace complete.
probably experimenting with weird classic crap on the lowest population isp wise across the board. we are lab rats bois
It seams like east coast players are out of luck.
Have you tried a VPN?
and i bet you have people on your friends list just chillin’ in Vol’dun questing or others in a dungeon too, right?
i’m verizon and central time. not using vpn and i refuse to as well
so they can fix it or lose a sub lol
Yea, not using a VPN either.
using a vpn is risky. good way to get your account info stolen
TRACEROUTE:
traceroute to 108.175.128.70 (108.175.128.70), 15 hops max, 60 byte packets
1 Blizzard Blizzard 5.842 ms 5.844 ms 5.854 ms
2 24.105.18.131 (24.105.18.131) 4.857 ms 4.905 ms 4.932 ms
3 137.221.105.12 (137.221.105.12) 5.916 ms 5.932 ms 5.939 ms
4 137.221.66.20 (137.221.66.20) 5.933 ms 5.942 ms 5.951 ms
5 137.221.83.68 (137.221.83.68) 5.871 ms 5.886 ms 5.895 ms
6 137.221.65.68 (137.221.65.68) 45.699 ms 40.605 ms 40.853 ms
7 137.221.68.32 (137.221.68.32) 6.360 ms 5.948 ms 5.949 ms
8 las-b21-link.telia.ne(62.115.178.200) 5.900 ms 5.959 ms 5.929 ms
9 las-b24-link.telia.ne (62.115.136.47) 7.402 ms 7.602 ms 7.625 ms
10 80.239.160.155 (80.239.160.155) 14.967 ms 14.564 ms 14.722 ms
11 et-3-3-0.cr0-mtl1.ip4.gtt.ne (141.136.105.209) 59.385 ms 59.204 ms 59.163 ms
12 ip4.gtt.ne (69.174.17.122) 74.092 ms 74.235 ms 74.100 ms
13 dsl-user.acndigital.ne (108.175.143.1) 76.526 ms 78.292 ms 78.089 ms
14 dsl-user.acndigital.ne(108.175.143.10) 167.486 ms 160.723 ms 160.727 ms
15 dsl-user.acndigital.ne(108.175.128.70) 88.301 ms 86.262 ms 91.381 ms
19/08/2019 15:05:56 UTC
PING:
PING 108.175.128.70 (108.175.128.70) 56(84) bytes of data.
64 bytes from 108.175.128.70: icmp_seq=1 ttl=50 time=90.8 ms
64 bytes from 108.175.128.70: icmp_seq=2 ttl=50 time=88.4 ms
64 bytes from 108.175.128.70: icmp_seq=3 ttl=50 time=91.6 ms
64 bytes from 108.175.128.70: icmp_seq=4 ttl=50 time=89.2 ms
— 108.175.128.70 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 88.434/90.054/91.677/1.303 ms
i mean my first assumption was i got hacked
or i was being banned lol
and it happend when i left a discord that i was in carrying 15’s lol , guess i carried a bit too hard
long island ny is down, will not give out tracer root.
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 19 ms 19 ms 18 ms tukw-dsl-gw76.tukw.qwest.net [63.231.10.76]
3 19 ms 19 ms 19 ms tukw-agw1.inet.qwest.net [63.226.198.89]
4 20 ms 19 ms 19 ms sea-brdr-03.inet.qwest.net [67.14.41.150]
5 * * * Request timed out.
6 20 ms 20 ms 19 ms ae-1-3513.edge1.Seattle3.Level3.net [4.69.160.69]
7 21 ms 21 ms 20 ms BLIZZARD-EN.edge1.Seattle3.Level3.net [4.59.232.146]
8 48 ms 48 ms 48 ms ae1-br01-eqse2.as57976.net [137.221.73.33]
9 48 ms 48 ms 48 ms xe-0-0-0-1-br01-eqsv5.as57976.net [137.221.65.40]
10 48 ms 48 ms 48 ms et-0-0-29-br02-eqsv5.as57976.net [137.221.65.117]
11 64 ms 88 ms 54 ms xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6]
12 48 ms 48 ms 48 ms be2-pe01-eqla1.as57976.net [137.221.68.71]
13 48 ms 49 ms 48 ms lax-eqla1-ia-bons-02.as57976.net [137.221.66.3]
14 48 ms 49 ms 48 ms 24.105.30.129
Trace complete.