Thanks for the tip… Wont be Qing for a while
still stuck in “logging into game server” new Hampshire here
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 8 ms 10 ms 24.105.62.129
Trace complete.East coast here, near DC…just got online, everything is working fine!
after almost 5 hours it finally let me login
Guys I think the game is working fine now, let me know if I’m wrong but try logging in.
It is not just WoW. Overwatch and some other Blizz games too. The internet is like a network of roads. You take different ones to get to different cities. The trip to NY might be fine but the traffic to San Fran is at a stand still.
Same thing happens when you connect to different websites. They are physically in very different places and take different routing paths.
The good news for you, is that those other websites working means it is not something specific to your local house network or your local ISP. It is farther down the line.
Greymane is in Chicago which was seeming to have issues and Bonechewer is in Los Angeles. Two very different routing paths.
2 Likes
OMG I’M IN !!!
Dam … nothing moving
/sadface
Wonder if now that it’s fixed we will get the real reason for the outage?
Blizz seems to have finally fixed whatever was causing he issue.
not fixed in my area
1 Like
oh yeah Im really raging lmao
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Linksys25375 [192.168.1.1]
2 1 ms 1 ms <1 ms 192.168.254.254
3 * * * Request timed out.
4 6 ms 7 ms 8 ms 172.99.44.6
5 13 ms 11 ms 11 ms ae8---0.scr02.mias.fl.frontiernet.net [74.40.3.73]
6 14 ms 12 ms 11 ms ae1---0.cbr01.mias.fl.frontiernet.net [74.40.1.126]
7 * * * Request timed out.
8 * * 14 ms ae-1-51.ear2.Miami1.Level3.net [4.69.207.21]
9 12 ms 11 ms 11 ms BLIZZARD-EN.ear2.Miami1.Level3.net [4.16.176.198]
10 * * * Request timed out.
11 * * * Request timed out.
12 45 ms 47 ms * et-0-0-4-br02-eqch2.as57976.net [137.221.65.46]
13 49 ms 48 ms 46 ms be2-pe01-eqch2.as57976.net [137.221.69.71]
14 49 ms 47 ms 47 ms 24.105.62.129
Trace complete.whois appears to tell me that it’s a Blizzard IP (leased from Ripenet?). Country does show as NL, though.
still nothing for lil ole me
Still unable to log in - NJ
I logged out of battle net then tried again and it worked!
I am now able to log in and play normally.
Been awhile since I’ve run into this problem. It’s probably a pipeline issue somewhere, as Blizzard doesn’t own the entire connection between the servers and each of us. The question needing to be asked is if there are any outages or service problems with other providers along the route. It could also be a communications or protocol issue between providers, for all I know, however.
The thing is, this isn’t the first time I’ve seen this or had this happen to me, and it’s not unique to Fios, but other providers at various times.
Same issue here. From Brazil.