The connection between OCE and US realms is broken, world ping goes upwards of 4-500 ping, this happens to me and US players that connect to OCE realms.
This has been going on for weeks, its random if the lag happens but it is connected to the amount of data being sent ingame e.g standing not moving and the lag goes down, starting a fight in LFR and people start teleporting, its like a golf ball trying to fit through a pin hole.
I am a network engineer, iv managed to capture the moment the connection switches.
From 250ms to 200ms for no reason, when on 250ms the game is unplayable, i don’t mean 250ms OCE bad, its full packet dropping, rubberbanding etc, this happens on VPN and off, so its not ISP routing, maybe some bad BGP in Sydney.
Reply from 66.40.177.166: bytes=32 time=247ms TTL=46
Reply from 66.40.177.166: bytes=32 time=235ms TTL=46
Reply from 66.40.177.166: bytes=32 time=257ms TTL=46
Request timed out.
Reply from 66.40.177.166: bytes=32 time=246ms TTL=46
Reply from 66.40.177.166: bytes=32 time=249ms TTL=46
Reply from 66.40.177.166: bytes=32 time=253ms TTL=46
Reply from 66.40.177.166: bytes=32 time=254ms TTL=46
Reply from 66.40.177.166: bytes=32 time=252ms TTL=46
Reply from 66.40.177.166: bytes=32 time=251ms TTL=46
Reply from 66.40.177.166: bytes=32 time=246ms TTL=46
Reply from 66.40.177.166: bytes=32 time=247ms TTL=46
Reply from 66.40.177.166: bytes=32 time=240ms TTL=46
Reply from 66.40.177.166: bytes=32 time=240ms TTL=46
Reply from 66.40.177.166: bytes=32 time=243ms TTL=46
Reply from 66.40.177.166: bytes=32 time=239ms TTL=46
Reply from 66.40.177.166: bytes=32 time=241ms TTL=46
Reply from 66.40.177.166: bytes=32 time=254ms TTL=46
Reply from 66.40.177.166: bytes=32 time=252ms TTL=46
Reply from 66.40.177.166: bytes=32 time=251ms TTL=46
Reply from 66.40.177.166: bytes=32 time=250ms TTL=46
Reply from 66.40.177.166: bytes=32 time=204ms TTL=49
Reply from 66.40.177.166: bytes=32 time=204ms TTL=49
Reply from 66.40.177.166: bytes=32 time=204ms TTL=49
Reply from 66.40.177.166: bytes=32 time=204ms TTL=49
Reply from 66.40.177.166: bytes=32 time=205ms TTL=49
Reply from 66.40.177.166: bytes=32 time=204ms TTL=49
I have an exact same issue but from EU to US, so if OCE - US and EU - US have same problem, maybe it is not a problem on our side and tech support finnaly send info about this kind of issue to tech department instead of bouncing us? Purely rhetorical question…
I am asking what was the route before vs the route now. Do you have that data? I’m asking since you mentioned that there’s “maybe some bad BGP in Sydney.”
Other aspects of game are fine, but every battleground game I am forced to play with the Grobbulus/Benediction/Pagle crowd and the game is completely unplayable - sometimes 90sec+ for a Power Word: Shield to activate and then getting flagged as deserter. Genuinely unplayable.
1 1 ms 1 ms 1 ms ARCHER_VR400 [192.168.1.1]
2 5 ms 4 ms 4 ms 10.20.26.113
3 9 ms 7 ms 8 ms syd-gls-har-int1-he0-3-0-2.tpgi.com.au [203.221.3.3]
4 151 ms 151 ms 151 ms lax-b22-link.ip.twelve99.nett [213.248.95.232]
5 153 ms 180 ms 152 ms blizzard-ic-348620.ip.twelve99-cust.nett [62.115.178.247]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 231 ms 231 ms 233 ms 137.221.69.81
11 233 ms 234 ms 232 ms 137.221.67.63
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 232 ms 232 ms 232 ms 66.40.176.144
Proper ping to LAX
1 1 ms 1 ms 1 ms ARCHER_VR400 [192.168.1.1]
2 4 ms 8 ms 5 ms 10.20.26.113
3 7 ms 7 ms 7 ms syd-gls-har-int2-be100.tpgi.com.au [203.221.3.4]
4 201 ms 202 ms 208 ms ix-xe-0-0-2-0.tcore2.tv2-tokyo.as6453.nett [180.87.181.192]
5 201 ms 199 ms 199 ms if-be-33-2.ecore1.tv2-tokyo.as6453.nett [180.87.181.205]
6 201 ms 201 ms 201 ms 63.218.251.13
7 * * * Request timed out.
8 192 ms 183 ms 183 ms 63-217-21-138.static.pccwglobal.nett [63.217.21.138]
9 192 ms 186 ms 183 ms 10.65.1.234
10 182 ms 182 ms 183 ms 10.65.0.142
11 * * * Request timed out.
12 182 ms 182 ms 183 ms lax.testmy.nett [45.77.2.132]
I wasn’t asking for a ping test from the command prompt. I was looking for the actual data/list of nodes you were using before vs using now. The sarcasm and hyperbole aren’t helping the cause; I was trying to gather all the facts to ask for more help from the staff. Good luck.
1 1 ms 1 ms 1 ms ARCHER_VR400 [192.168.1.1]
2 5 ms 5 ms 4 ms 10.20.26.113
3 7 ms 7 ms 7 ms syd-gls-har-int1-he0-3-0-2.tpgi.com.au [203.221.3.3]
4 152 ms 151 ms 154 ms lax-b22-link.ip.twelve99.nett [213.248.95.232]
5 152 ms 153 ms 153 ms blizzard-ic-348620.ip.twelve99-cust.nett [62.115.178.247]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 202 ms 202 ms 202 ms et-0-0-0-pe02-evch1.as57976.nett [137.221.69.83]
11 201 ms 201 ms 202 ms 137.221.67.65
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 201 ms 200 ms 200 ms 66.40.178.15
You’re saying the current/new route is causing the problem due to a bad BGP. I responded to you based on assumed knowledge (i.e., “I am a network engineer”): What nodes/route were you using before? The traceroutes to the Blizzard servers are not going to show us the old route you took. Additionally, many of Blizzard’s nodes are configured to ignore ping requests—a common DDoS protection mechanism most network engineers know and use—hence lots of “Request timed out” responses. They are not direct evidence of a problem, especially if the behavior is intended. I was looking for comparison data, but the sour responses spoiled the troubleshooting efforts.