High MS on Oceanic Servers

Support Technical Support
1

I’ve been getting 300+ms to the oceanic servers in both Diablo 3 and World of Warcraft since about a month ago. Been going through the ringer of reinstalling WoW checking addons. Resetting and redoing the whole network and reinstalling windows. I’ve now contacted both Blizzard CS and Optus CS each telling me it’s the other guys fault and i need to contact them for them to uno reverse card.

Here is the Traceroute from the .txt file

Tracing route to 103.4.115.248 over a maximum of 30 hops

1 6 ms 5 ms 5 ms n110-20-96-1.rdl3.qld.optusnet. com.au [110.20.96.1]
2 * * * Request timed out.
3 8 ms 8 ms 7 ms hu0-4-0-0.44rdpr01.optus.net.au [124.19.61.189]
4 8 ms 6 ms 7 ms Bundle-Ether20.woo-edge903.brisbane.telstra. net [165.228.15.33]
5 9 ms 6 ms 9 ms bundle-ether12.woo-core30.brisbane.telstra. net [203.50.11.242]
6 21 ms 19 ms 18 ms bundle-ether4.stl-core30.sydney.telstra. net [203.50.13.155]
7 17 ms 24 ms 17 ms bundle-ether1.chw-edge903.sydney.telstra. net [203.50.11.177]
8 304 ms 302 ms 304 ms twi3639888.lnk.telstra. net [139.130.85.38]
9 237 ms 235 ms 236 ms et-0-0-49-br02-eqsy4.as57976. net [137.221.85.49]
10 244 ms 244 ms 243 ms xe-0-0-1-3-br02-eqla1.as57976. net [137.221.65.36]
11 435 ms 439 ms 439 ms xe-0-0-0-0-br02-lgpy1.as57976. net [137.221.65.65]
12 246 ms 244 ms 247 ms 137.221.84.83
13 242 ms 241 ms 249 ms icn-lgpy1-ia-bons-01.as57976. net [137.221.66.97]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 232 ms 233 ms 234 ms 103.4.115.248

Trace complete.

I have no clue where to go from here and it’s only the Oceanic Servers i’m having an issue with. I normally get around 180-240ms for NA servers and thats what i’m getting.

Trace Route to Central America

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 7 ms 6 ms 7 ms n110-20-96-1.rdl3.qld.optusnet.com.au [110.20.96.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 20 ms 19 ms 19 ms mas1-hu0-5-0.ig.optusnet.com.au [198.142.249.246]
7 175 ms 175 ms 175 ms 203.208.148.205
8 175 ms * 175 ms 203.208.171.117
9 175 ms 174 ms 174 ms lax-b23-link.ip.twelve99. net [213.248.83.124]
10 176 ms 175 ms 175 ms blizzard-ic-348621.ip.twelve99-cust. net [62.115.178.201]
11 229 ms 437 ms 440 ms ae1-br01-eqla1.as57976. net [137.221.68.33]
12 * * * Request timed out.
13 * * * Request timed out.
14 222 ms 223 ms 225 ms 137.221.69.81
15 223 ms 223 ms 225 ms 24.105.62.129

Trace complete.

I’m stumped and i have no clue what i’m looking at, Hoping someone on the forums has a clue to whats going on or something I can give Optus or Blizzard to fix

2

As a third party who has no monetary interest in either company, I can tell you the problem is in Optus and/or Telstra’s network. The data you posted clearly shows a huge ping jump from the Sydney node to the next one.

3 Likes
3

I appreciate that

1 Like
4

I am having the same issue. See Tracert results below.

It has nothing to do with optus or telstra. The issue is that OCE players for some reason are routed through NL servers 137.221.84.xx and 137.221.85.xx once they create a connection to the OCE Sydney server 137.221.65.97. The fall over is on server 137.221.66.xx as it does not exist, and is not a registered part of the blizzard AS57976 domain network.

As soon as Blizzard stops trying to force OCE players through the NL servers for groups and raids, we will stop having this issue of massive latency spikes.

  3     3 ms     3 ms     3 ms  adl-apt-pir-crt2-be200.tpgi.com.au [203.219.182.66] 
  4     2 ms     3 ms     3 ms  adl-adc-lon-crt2-be10.tpgi.com.au [203.219.107.22] 
  5     4 ms     3 ms     3 ms  adl-adc-lon-wgw1-be-100.tpgi.com.au [203.219.199.3] 
  6     3 ms     3 ms     3 ms  be300.akingbrdr11.aapt.net.au [203.219.199.154] 
  7     4 ms     3 ms     4 ms  Bundle-Ether15.fli-edge903.Adelaide.telstra.net [210.23.157.77] 
  8     4 ms     6 ms     6 ms  bundle-ether11.fli-core10.adelaide.telstra.net [203.50.6.14] 
  9    12 ms    14 ms    12 ms  bundle-ether5.win-core30.melbourne.telstra.net [203.50.6.229] 
 10    25 ms    24 ms    26 ms  bundle-ether3.stl-core30.sydney.telstra.net [203.50.13.130] 
 11    24 ms    24 ms    24 ms  bundle-ether1.chw-edge903.sydney.telstra.net [203.50.11.177] 
 12    25 ms    25 ms    25 ms  twi3639888.lnk.telstra.net [139.130.85.38] 
 13   189 ms   204 ms   190 ms  et-0-0-49-br02-eqsy4.as57976.net [137.221.85.49] 
 14   189 ms   189 ms   189 ms  xe-0-0-1-3-br02-eqla1.as57976.net [137.221.65.36] 
 15   388 ms   410 ms   219 ms  xe-0-0-0-0-br02-lgpy1.as57976.net [137.221.65.65] 
 16   191 ms   191 ms   190 ms  137.221.84.83 
 17   190 ms   190 ms   190 ms  icn-lgpy1-ia-bons-01.as57976.net [137.221.66.97] 
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21   188 ms   187 ms   188 ms  103.4.115.248
5

Blizzard doesn’t choose how your connection is routed, they develop games. That stuff is handled by your ISP and their peering partners. Any issue along that path would need to be escalated in a ticket by your ISP.

1 Like
8

That IP may have been registered in the Netherlands, but that’s not the physical location of it. Either way, Blizzard also isn’t responsible for how you connect to voice services. The industry standard is to not offer any form of connection troubleshooting; Blizzard just offered it as a courtesy in the past.

Edit: Removing response to a comment that was deleted.

2 Likes