When using a tunnel to escape my ISPs routing, this is what the final few hops to Sydney servers look like. From what I can tell everything from hop 7 onwards is Blizzard’s network.
6 67 ms 51 ms 51 ms 218.100.52.65
7 52 ms 51 ms 51 ms 137.221.85.33
8 51 ms 67 ms 51 ms 137.221.85.67
9 81 ms 52 ms 51 ms 137.221.66.133
10 51 ms 52 ms 51 ms 37.244.40.29
11 * * * Request timed out.
12 52 ms 51 ms 51 ms 158.115.197.22 (Sydney WoW server)
Forgoing the tunnel and letting my ISP do its thing, it looks like this (Before this started happening my ping was ~45ms)
1 <1 ms 1 ms <1 ms 192.168.5.1
2 3 ms 3 ms 3 ms
3 3 ms 3 ms 3 ms 192.168.255.250
4 3 ms 3 ms 3 ms 192.168.255.251
5 3 ms 3 ms 8 ms
6 239 ms 240 ms 239 ms 158.115.197.22 (Sydney WoW server)
It looks like there’s a tunnel between hops 5 and 6 taking a rather circuitous route, but after a dozen emails and hours on the phone with my ISP they insist nothing is wrong.
Since whatever insanity is happening seems to end within Blizzard’s network, I thought I’d try talking to a GM, and they directed me here.
I get the same behaviour when connecting to US servers, in that hop 5 is my ISP and hop 6 is the server itself, but in this case 160ms is normal
5 2 ms 2 ms 2 ms
6 159 ms 159 ms 159 ms 64.224.29.156 (US WoW server)
1 Like
Personally, I have not been able to ‘log in’ as of the last 48hrs (approximately).
I’m in the OCE area and assuming, currently, that this has been tied into the ddos attacks. But I have been through trouble-shooting and forums, trying every one of the recommended fixes;
-Updated Video Drivers,
-Cleared Cache/WTF/Interface folders,
-Reset Router,
-Uninstalled and Reinstalled Battle.net app
-Checked Firewall options to make sure they are allowing the game through,
-Analyzed and Optimized Drives
And after everything, I am still getting no further than the “Logging in to game server” screen when I try to play. Some friends have been able to get in, some made it as far as the character lists then got disconnected and couldn’t get back past “Logging in to game server” afterwards.
WOW51900328 Error - Keep getting Disconnected
That’s all the relevant information I can think of, if there is anything we can provide to assist getting this sorted please reach out.
I don’t think our issues are related. This routing has been ongoing for a month, and I have no problems connecting.
1 Like
The 192. Blah blah numbers are your network so anything just after that hop 5 and 6 would be your isp and beyond that however they route it the backbone connection usually Telstra followed by international routing and on to blizzard. I don’t believe it’s unusual routing. Unless your isp optimises gaming traffic which isn’t unusual or uncommon.
192.168.x.x are just private addresses, hops 3 and 4 are my ISPs network, not mine.
Hop 6 is the WoW server itself. And 240ms is definitely unusual, my ping should be ~45ms, if you look at the trace when I use a tunnel you can see I get 51ms
As I said the 192 is the same for everyone that has a network at home even mine start with 192the next are your isp as I said then the connection to where ever it’s going on further. And 51 ms is not a real lot I know it’s not something like 15 ms but I remember a time when in Australia we had well over 300 ms and much more in burning crusade so 51 Ms is nothing.
Did you think I meant foregoing instead of forgoing? That was a poor word choice on my part, and maybe the layout of my post was a little confusing. Those are two separate traceroutes.
I provided the first one to demonstrate what a normal traceroute looks like, and to show that the encapsulation happening between hops 5 and 6 (of the second traceroute) ends within Blizzard’s network
The second traceroute (shown in its entirety) is the problematic one, I am getting 240ms to a Sydney server, when I should get around 45.
Did you mean to copy paste that here? Or were you trying to reply to my thread comment?
Where did you collect the server IP you’re testing? The ones Blizzard posted in the past are no longer pointing at game servers, so you wouldn’t want to use those.
Additionally, it looks like those tests are missing several hops. One hop showing a high ping can mean nothing in the middle of a test if it’s configured to ignore ICMP requests (pings).
1 Like
Looks like my ISP has finally fixed this.
From the connections WoW was making while playing.
If you read the first half of the sentence you quoted, I posted the traceroute in its entirety. If you think 6 hops is a bit short, that was the point of the post. There was encapsulation happening between hops 5 and 6. Now that it’s been fixed it’s even shorter, this is the new traceroute:
Tracing route to 158.115.197.247 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.5.1
2 2 ms 2 ms 2 ms
3 22 ms 15 ms 16 ms 10.101.0.158
4 40 ms 40 ms 40 ms 158.115.197.247
Trace complete.
You can see your ping in game
1 Like