Server Aggramar
I think it is a ISP problem, thats why the long time to fix it. Probably isnt on Blizzard`s hand.
hahahahahahahahahahahahahahahhahaha, good one.
Well I just realized there are a lot of bad overwatch players in europe…lol
continue getting the problem:
Traza a 24.105.30.129 sobre caminos de 30 saltos como máximo.
1 * * * Tiempo de espera agotado para esta solicitud.
2 20 ms 22 ms 16 ms 10.48.43.148
3 19 ms 16 ms 16 ms 10.48.41.143
4 16 ms 13 ms 16 ms 10.48.42.181
5 56 ms 68 ms 50 ms 63.245.6.236
6 50 ms 47 ms 52 ms xe-1-0-1.usa.north-miami.fl.us.nmi-teracore01.cwc.com [63.245.5.112]
7 * * 103 ms chi-b21-link.telia.net [62.115.113.19]
8 100 ms 94 ms 99 ms blizzard-ic-348622-chi-b21.c.telia.net [62.115.178.249]
9 124 ms 127 ms 124 ms ae1-br01-eqch2.as57976.net [137.221.69.33]
10 140 ms 174 ms 128 ms 137.221.65.132
11 133 ms 146 ms 128 ms et-0-0-2-br01-eqla1.as57976.net [137.221.65.68]
12 126 ms 140 ms 127 ms be1-pe01-eqla1.as57976.net [137.221.68.67]
13 130 ms 130 ms 129 ms lax-eqla1-ia-bons-02.as57976.net [137.221.66.3]
14 126 ms 129 ms 125 ms 24.105.30.129
Traza completa.
nope, they all get ur account info because they go thru the dark web where any hacker can steal all ur info
I don’t gonna use VPN. I need this works.
So the few of us with problems are left alone and in the dark. I really wish there was more communication from a blizzard.
It seems to be an issue at Level3 and (possibly) Qwest. Here’s my output from WinMTR
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| tew - 0 | 146 | 146 | 0 | 22 | 39 | 24 |
| 144-163-128-254.nlrk.centurylink.net - 0 | 146 | 146 | 42 | 44 | 96 | 44 |
| nlrk-agw1.inet.qwest.net - 0 | 146 | 146 | 42 | 45 | 127 | 44 |
| dax-brdr-01.inet.qwest.net - 0 | 146 | 146 | 54 | 58 | 154 | 61 |
| 63.235.42.30 - 50 | 146 | 73 | 54 | 56 | 80 | 56 |
| 4.69.210.145 - 92 | 146 | 13 | 55 | 56 | 58 | 57 |
| BLIZZARD-EN.ear3.Dallas1.Level3.net - 0 | 146 | 146 | 55 | 62 | 145 | 58 |
| ae1 - 0 | 146 | 146 | 88 | 99 | 165 | 96 |
| et - 0 | 146 | 146 | 88 | 99 | 195 | 94 |
| 137.221.65.122 - 0 | 146 | 145 | 88 | 99 | 207 | 97 |
| et - 0 | 145 | 145 | 87 | 403 | 6505 | 361 |
| be1 - 0 | 145 | 145 | 87 | 97 | 125 | 99 |
| lax - 0 | 145 | 145 | 87 | 97 | 167 | 95 |
| 24.105.30.129 - 0 | 145 | 145 | 87 | 98 | 163 | 94 |
|________________________________________________|______|______|______|______|______|______|
In my case, he trouble starts at 63.235.42.30 with 50% loss. This is a Qwest IP, and the next IP in the route, belonging to Level3, suffers 92% loss. I’d say the issue lies on the interconnection between Qwest and Level3, at least in my case.
I am not even getting to character select screen now
They should have that all on hand, you saying that when they have a PROBLEM THIS BIG, its not indicated anywhere in there system? cause that’s a damn cop out.
Verizon, spectrum and T-Mobile hotspot all have the same problem.
It is definitely a Blizzard issue…I can literally play any other non-blizzard game with zero issues. logs on to WoW “haha disconnected loser”
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 5 ms 1 ms <1 ms DSL-2401HN-T1C-NV.DSL-2401HN-T1C-NV [192.168.15.1]
2 20 ms 22 ms 21 ms gvt-b-se01.pae.gvt.net.br [187.115.211.224]
3 20 ms 22 ms 20 ms 191.30.8.135
4 23 ms 23 ms 23 ms 152-255-149-76.user.vivozap.com.br [152.255.149.76]
5 42 ms 43 ms 40 ms 152-255-140-45.user.vivozap.com.br [152.255.140.45]
6 39 ms 48 ms 40 ms 213.99.17.202
7 149 ms 156 ms 146 ms 94.142.98.177
8 178 ms 178 ms 177 ms 94.142.127.189
9 175 ms 174 ms 173 ms 81.173.106.21
10 226 ms 252 ms 227 ms ae1-br01-eqdc2.as57976. net [137.221.72.33]
11 249 ms 271 ms 249 ms et-0-0-2-br01-eqch2.as57976. net [137.221.65.13]
12 229 ms 226 ms 482 ms 137.221.65.132
13 430 ms 424 ms 439 ms et-0-0-2-br01-eqla1.as57976. net [137.221.65.68]
14 229 ms 228 ms 229 ms be1-pe02-eqla1.as57976. net [137.221.68.69]
15 231 ms 315 ms 231 ms 24.105.30.129
Likely, it’s a specific piece of equipment/router at the edge of an East Coast data center. That would be why East Coast users, some East Coast realms, and random instance servers are showing up on this list. Probably a backbone connection that Blizzard shares with Verizon than either one of them. That’s what makes it hard to troubleshoot.
Tracing route to 24.105.30.12 over a maximum of 30 hops
1 2 ms <1 ms <1 ms 192.168.1.1
2 2 ms 1 ms 1 ms 24.105.30.12
Trace complete.
Bingo. Or at least something very similar.
Traceroute has started…
traceroute to 137.221.105.2 (137.221.105.2), 64 hops max, 72 byte packets
1 www.routerlogin.com (192.168.1.1) 2.211 ms 2.438 ms 137.076 ms
2 10.1.178.1 (10.1.178.1) 3.475 ms 5.248 ms 5.181 ms
3 66.193.108.129 (66.193.108.129) 6.621 ms 3.620 ms 2.845 ms
4 10.208.129.45 (10.208.129.45) 8.355 ms 4.919 ms 4.857 ms
5 * ae9-80g.ar8.sea1.gblx.net (207.218.1.242) 21.790 ms 16.702 ms
6 * * *
7 ae-2-3613.edge1.seattle3.level3.net (4.69.160.73) 17.100 ms 16.139 ms 16.065 ms
8 blizzard-en.edge1.seattle3.level3.net (4.59.232.146) 18.085 ms 18.446 ms 18.093 ms
9 ae1-br01-eqse2.as57976.net (137.221.73.33) 38.658 ms 38.739 ms 39.024 ms
10 xe-0-0-0-1-br01-eqsv5.as57976.net (137.221.65.40) 38.844 ms 38.947 ms 39.142 ms
11 et-0-0-29-br02-eqsv5.as57976.net (137.221.65.117) 37.932 ms 38.782 ms 38.124 ms
12 xe-0-0-1-1-br02-eqla1.as57976.net (137.221.65.6) 39.073 ms 38.291 ms 38.447 ms
13 et-0-0-29-br01-eqla1.as57976.net (137.221.65.0) 38.835 ms 38.896 ms 39.259 ms
14 et-0-0-2-br01-swlv10.as57976.net (137.221.65.69) 39.020 ms 38.596 ms 38.958 ms
15 et-0-0-31-pe01-swlv10.as57976.net (137.221.83.67) 40.158 ms 42.139 ms 38.573 ms
16 las-swlv10-ia-bons-02.as57976.net (137.221.66.19) 39.250 ms 43.115 ms 38.839 ms
17 137.221.105.2 (137.221.105.2) 38.462 ms 43.056 ms 42.330 ms
I get it, maybe it’s an ISP problem but here we have people from all the world having the same problem
Already saw people from US/EU/BR/LAN, and all with the same problems
C’mon blizz
WoW please provide an update on probable cause(s) of the issue. If we could at least have this much info it would help us understand.