ANZ Server Latency (Nov 2018)

Technical Support
Receiving high ping (180-200 ms) to the Australian (Sydney) server from Sydney (non-NBN).

Have restarted router, computer, etc, with no change.

Tracert:

Tracing route to 103.4.115.248 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 14 ms 15 ms 15 ms 10.20.23.227
3 14 ms 15 ms 15 ms syd-gls-har-agr11-be-12.tpgi.com.au [202.7.205.13]
4 16 ms 16 ms 15 ms syd-gls-har-wgw1-be-100.tpgi.com.au [203.221.3.7]
5 16 ms 16 ms 15 ms 203-219-107-194.static.tpgi.com.au [203.219.107.194]
6 16 ms 16 ms 16 ms Bundle-Ether13.ken-edge902.sydney.telstra.net [139.130.214.101]
7 16 ms 17 ms 15 ms bundle-ether14.ken-core10.sydney.telstra.net [203.50.11.96]
8 18 ms 18 ms 16 ms bundle-ether1.oxf-gw10.sydney.telstra.net [203.50.6.97]
9 19 ms 18 ms 19 ms bundle-ether1.sydo-core04.sydney.reach.com [203.50.13.94]
10 18 ms 16 ms 16 ms i-0-0-0-15.sydo10.telstraglobal.net [202.84.222.206]
11 17 ms 17 ms 16 ms unknown.telstraglobal.net [210.176.152.33]
12 17 ms 17 ms 17 ms 137.221.85.35
13 170 ms 169 ms 170 ms et-0-0-0-pe02-eqsy4.as57976.net [137.221.85.73]
14 170 ms 170 ms 172 ms 103.4.115.248

Trace complete.

------------------------

EDIT: For anyone else you can follow instructions here to trace:
https://us.battle.net/support/en/article/7870
https://us.battle.net/support/en/article/7871
Aussie Diablo 3 server is: 103.4.115.248
I'm experiencing high than usual ping as well, below my WinMTR results:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.asus.com - 0 | 44 | 44 | 2 | 3 | 12 | 2 |
| 10-20-25-4.tpgi.com.au - 0 | 44 | 44 | 24 | 32 | 64 | 32 |
| syd-apt-ros-agr11-be-23.tpgi.com.au - 0 | 44 | 44 | 26 | 34 | 63 | 32 |
| syd-apt-ros-wgw1-be-10.tpgi.com.au - 0 | 44 | 44 | 25 | 31 | 58 | 27 |
| be300.sglebbrdr11.aapt.net.au - 0 | 44 | 44 | 24 | 33 | 61 | 27 |
|TenGigE0-3-0-19.chw-edge901.sydney.telstra.net - 0 | 44 | 44 | 25 | 29 | 57 | 29 |
|bundle-ether13.chw-core10.sydney.telstra.net - 0 | 44 | 44 | 26 | 32 | 64 | 31 |
|bundle-ether1.oxf-gw11.sydney.telstra.net - 0 | 44 | 44 | 27 | 31 | 57 | 30 |
|bundle-ether2.oxf-gw10.sydney.telstra.net - 0 | 44 | 44 | 29 | 36 | 65 | 37 |
|bundle-ether1.sydo-core04.sydney.reach.com - 0 | 44 | 44 | 31 | 38 | 66 | 34 |
| i-0-0-0-15.sydo10.telstraglobal.net - 0 | 44 | 44 | 29 | 36 | 88 | 31 |
| unknown.telstraglobal.net - 0 | 44 | 44 | 25 | 28 | 61 | 26 |
| 137.221.85.35 - 3 | 40 | 39 | 0 | 30 | 65 | 27 |
| et-0-0-0-pe02-eqsy4.as57976.net - 0 | 44 | 44 | 181 | 187 | 238 | 181 |
| 103.4.115.248 - 0 | 44 | 44 | 179 | 185 | 213 | 184 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Taken today, and yes the latency is higher than what I would get from a direct connection to the default The Americas server:

Tracing route to 103.4.115.248 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 17 ms 16 ms 16 ms 210.195.63.254
3 18 ms 19 ms 21 ms 10.55.49.103
4 22 ms 22 ms 22 ms 10.55.99.174
5 51 ms 51 ms 51 ms 58.27.38.246
6 52 ms 51 ms 52 ms i-99.hkth-core02.telstraglobal.net [202.84.153.149]
7 166 ms 165 ms 165 ms i-10352.sydo-core03.telstraglobal.net [202.84.138.42]
8 165 ms 165 ms 164 ms i-0-0-0-14.sydo10.telstraglobal.net [202.84.222.194]
9 165 ms 166 ms 166 ms unknown.telstraglobal.net [210.176.152.33]
10 166 ms 166 ms 166 ms et-0-0-48-br01-eqsy4.as57976.net [137.221.85.33]
11 265 ms 264 ms 264 ms et-0-0-0-pe02-eqsy4.as57976.net [137.221.85.69]
12 266 ms 266 ms 266 ms 103.4.115.248

Trace complete.
So the jump is happening in all cases so far at et-0-0-0-pe02-eqsy4.as57976.net

Definitely been going on for a couple hours now.
Having the exact same issue.
I'm on iiNet and the CS rep told me if I disabled port blocking that it would fix the issue.
It did, but only for one run of the game.
Next time I launched I was back to bad ping.

TRACEROUTE:
traceroute to 203.7.29.248 (203.7.29.248), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.243 ms 0.242 ms 0.242 ms
2 37.244.22.2 (37.244.22.2) 0.571 ms 0.589 ms 0.660 ms
3 24.105.30.170 (24.105.30.170) 0.911 ms 0.952 ms 1.021 ms
4 137.221.66.2 (137.221.66.2) 2.108 ms 2.144 ms 2.147 ms
5 137.221.68.66 (137.221.68.66) 286.212 ms 286.249 ms 286.256 ms
6 137.221.65.57 (137.221.65.57) 98.587 ms 98.600 ms 98.591 ms
7 137.221.81.32 (137.221.81.32) 98.415 ms 98.301 ms 98.483 ms
8 4739.tyo.equinix.com (203.190.230.30) 98.727 ms 98.622 ms 98.746 ms
9 so-3-3-0.br1.syd7.on.ii.net (150.101.33.200) 215.781 ms 215.669 ms 215.738 ms
10 be-50.cr2.syd7.on.ii.net (150.101.37.12) 215.609 ms 215.657 ms 215.616 ms
11 be40.cr2.adl6.on.ii.net (150.101.33.35) 215.671 ms 215.689 ms 215.825 ms
12 po20.bras21.adl4.on.ii.net (150.101.35.183) 215.349 ms 215.390 ms 215.355 ms
13 203-7-29-248.dyn.iinet.net.au (203.7.29.248) 220.265 ms 220.428 ms 220.257 ms

30/10/2018 11:02:41 UTC
--------------------

PING:
PING 203.7.29.248 (203.7.29.248) 56(84) bytes of data.
64 bytes from 203.7.29.248: icmp_seq=1 ttl=52 time=220 ms
64 bytes from 203.7.29.248: icmp_seq=2 ttl=52 time=220 ms
64 bytes from 203.7.29.248: icmp_seq=3 ttl=52 time=220 ms
64 bytes from 203.7.29.248: icmp_seq=4 ttl=52 time=237 ms

--- 203.7.29.248 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 220.245/224.710/237.284/7.262 ms

30/10/2018 11:02:41 UTC
--------------------

MTR:
Start: Tue Oct 30 11:02:41 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0
2.|-- 37.244.22.2 0.0% 10 0.5 0.6 0.5 1.1 0.0
3.|-- 24.105.30.170 0.0% 10 0.9 0.9 0.8 1.0 0.0
4.|-- 137.221.66.2 0.0% 10 1.6 1.5 1.4 1.6 0.0
5.|-- 137.221.68.66 0.0% 10 98.5 132.3 98.5 424.1 102.6
6.|-- 137.221.65.57 0.0% 10 98.5 98.5 98.4 98.7 0.0
7.|-- 137.221.81.32 0.0% 10 98.7 98.5 98.3 98.7 0.0
8.|-- 4739.tyo.equinix.com 0.0% 10 99.0 98.8 98.6 99.2 0.0
9.|-- so-3-3-0.br1.syd7.on.ii.net 0.0% 10 215.7 215.7 215.7 215.8 0.0
10.|-- be-50.cr2.syd7.on.ii.net 0.0% 10 215.7 215.7 215.6 215.9 0.0
11.|-- be40.cr2.adl6.on.ii.net 0.0% 10 215.7 215.7 215.6 216.0 0.0
12.|-- po20.bras21.adl4.on.ii.net 0.0% 10 215.5 215.5 215.4 215.5 0.0
13.|-- 203-7-29-248.dyn.iinet.net.au 0.0% 10 220.0 222.3 220.0 238.7 5.7

30/10/2018 11:02:41 UTC
--------------------

I've just spoken to a GM and they've informed me that it's an issue with a server in Sydney, it is not on our end or Blizzards but in the middle.
(At least for my issue)
I suggest you all open tickets with Customer Service and get the necessary information to take to your ISP so we can get this sorted out as soon as possible.
One step before the server isn't exactly the middle. Sounds like it's at the server hub.
Certainly isn't my ISP, the tracerts show that.

Another tracert, 3.5 hours later (problem has been consistent while I've been playing for hours):

Tracing route to 103.4.115.248 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 23 ms 22 ms 23 ms 10-20-25-5.tpgi.com.au [10.20.25.5]
3 23 ms 24 ms 23 ms syd-apt-ros-agr11-be-24.tpgi.com.au [202.7.171.161]
4 22 ms 23 ms 23 ms syd-apt-ros-wgw1-be-10.tpgi.com.au [203.29.134.7]
5 22 ms 23 ms 23 ms be300.sglebbrdr11.aapt.net.au [203.219.107.198]
6 23 ms 23 ms 23 ms TenGigE0-3-0-19.chw-edge901.sydney.telstra.net [139.130.209.229]
7 25 ms 25 ms 24 ms bundle-ether13.chw-core10.sydney.telstra.net [203.50.11.98]
8 24 ms 24 ms 25 ms bundle-ether1.oxf-gw11.sydney.telstra.net [203.50.6.93]
9 24 ms 25 ms 24 ms bundle-ether2.oxf-gw10.sydney.telstra.net [203.50.6.94]
10 25 ms 27 ms 24 ms bundle-ether1.sydo-core04.sydney.reach.com [203.50.13.94]
11 24 ms 24 ms 23 ms i-0-0-0-15.sydo10.telstraglobal.net [202.84.222.206]
12 25 ms 24 ms 24 ms unknown.telstraglobal.net [210.176.152.33]
13 25 ms 25 ms 25 ms 137.221.85.35
14 177 ms 177 ms 178 ms et-0-0-0-pe02-eqsy4.as57976.net [137.221.85.73]
15 177 ms 177 ms 177 ms 103.4.115.248

Trace complete.
I see. I apologize, I did not mean middle in the literal sense.
I'm at a loss for what to do as I've no expertise in the matter whatsoever. Sorry for wasting your time.
It was a bit too laggy to play again, no surprise that I did another traceroute:

Tracing route to 103.4.115.248 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 17 ms 17 ms 71 ms 210.195.127.254
3 16 ms 18 ms 18 ms 10.55.49.101
4 21 ms 21 ms 21 ms 10.55.99.178
5 50 ms 51 ms 52 ms 58.27.38.246
6 52 ms 53 ms 52 ms i-95.hkth-core02.telstraglobal.net [202.84.153.141]
7 166 ms 165 ms 166 ms i-10352.sydo-core03.telstraglobal.net [202.84.138.42]
8 164 ms 163 ms 165 ms i-0-0-0-14.sydo10.telstraglobal.net [202.84.222.194]
9 166 ms 165 ms 166 ms unknown.telstraglobal.net [210.176.152.33]
10 166 ms 166 ms 166 ms 137.221.85.35
11 265 ms 265 ms 265 ms et-0-0-0-pe02-eqsy4.as57976.net [137.221.85.73]
12 264 ms 264 ms 264 ms 103.4.115.248

Trace complete.
Hey hey everyone,

Thank you all for the Winmtr's that have been posted. If anyone else is experiencing this issue please get us a Winmtr so we can get this looked into.

WinMTR
(Please put it in code blocks to make it easier to read. To do that past the report in a chat box. Then right click “Select All”-should highlight everything. Next click on the little </> symbol on the bar below the chat box.)
I am also experiencing high latency, 230 -250 for over 24 hrs now, i am in Perth western australia, hope this can be sorted out very soon.
So normally I get ~35ms and as of yesterday I am getting a constant ~210ms (not spikes but a constant high ping). I am from Australia with TPG NBN and D3 ping has always been fine until yesterday. Rest of my internet totally fine and speedy and other non Blizzard games getting usual ping.

Here is my tracert to the D3 Aus server:


C:\Users\User>tracert 103.4.115.248

Tracing route to 103.4.115.248 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192-168-1-1.tpgi.com.au [192.168.1.1]
2 8 ms 7 ms 7 ms 10-20-25-85.tpgi.com.au [10.20.25.85]
3 9 ms 8 ms 8 ms nme-apt-bur-wgw1-be-20.tpgi.com.au [203.219.155.202]
4 8 ms 9 ms 8 ms 203-219-107-206.static.tpgi.com.au [203.219.107.206]
5 8 ms 8 ms 9 ms Bundle-Ether-13.win-edge901.melbourne.telstra.net [165.228.52.1]
6 10 ms 11 ms 9 ms bundle-ether11.win-core10.melbourne.telstra.net [203.50.11.107]
7 23 ms 20 ms 20 ms bundle-ether12.ken-core10.sydney.telstra.net [203.50.11.122]
8 22 ms 22 ms 22 ms bundle-ether1.oxf-gw10.sydney.telstra.net [203.50.6.97]
9 23 ms 22 ms 22 ms bundle-ether1.sydo-core04.sydney.reach.com [203.50.13.94]
10 21 ms 21 ms 20 ms i-0-0-0-15.sydo10.telstraglobal.net [202.84.222.206]
11 37 ms 21 ms 21 ms unknown.telstraglobal.net [210.176.152.33]
12 52 ms 22 ms 22 ms 137.221.85.35
13 175 ms 175 ms 175 ms et-0-0-0-pe02-eqsy4.as57976.net [137.221.85.73]
14 175 ms 176 ms 175 ms 103.4.115.248

Trace complete.


Here are the results from the looking glass test site:

TRACEROUTE:
traceroute to 203.192.93.33 (203.192.93.33), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.281 ms 0.284 ms 0.286 ms
2 37.244.22.130 (37.244.22.130) 0.589 ms 0.609 ms 0.689 ms
3 24.105.30.150 (24.105.30.150) 1.169 ms 1.248 ms 1.309 ms
4 137.221.66.6 (137.221.66.6) 1.540 ms 1.591 ms 1.676 ms
5 137.221.68.72 (137.221.68.72) 8.502 ms 8.515 ms 8.518 ms
6 137.221.65.7 (137.221.65.7) 8.431 ms 8.471 ms 8.476 ms
7 137.221.70.32 (137.221.70.32) 8.310 ms 8.259 ms 8.245 ms
8 eqix.sv1.ppc1.com (206.223.116.6) 165.902 ms 165.456 ms 165.424 ms
9 syd-gls-har-crt1-he-0-3-0-2.tpgi.com.au (203.221.3.1) 156.996 ms 156.561 ms 156.543 ms
10 203-219-155-221.tpgi.com.au (203.219.155.221) 168.275 ms 168.322 ms 168.312 ms
11 ip-33-93-192-203.static.pipenetworks.com (203.192.93.33) 175.507 ms 179.489 ms 178.785 ms

30/10/2018 00:45:14 UTC
--------------------

PING:
PING 203.192.93.33 (203.192.93.33) 56(84) bytes of data.
64 bytes from 203.192.93.33: icmp_seq=1 ttl=52 time=175 ms
64 bytes from 203.192.93.33: icmp_seq=2 ttl=52 time=175 ms
64 bytes from 203.192.93.33: icmp_seq=3 ttl=52 time=175 ms
64 bytes from 203.192.93.33: icmp_seq=4 ttl=52 time=182 ms

--- 203.192.93.33 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 175.400/177.455/182.803/3.092 ms

30/10/2018 00:45:14 UTC
--------------------

MTR:
Start: Tue Oct 30 00:45:14 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 37.244.22.130 0.0% 10 0.5 0.5 0.5 0.8 0.0
3.|-- 24.105.30.150 0.0% 10 1.2 1.2 0.9 1.3 0.0
4.|-- 137.221.66.6 0.0% 10 1.5 1.6 1.4 2.9 0.3
5.|-- 137.221.68.72 0.0% 10 8.3 8.4 8.3 8.5 0.0
6.|-- 137.221.65.7 0.0% 10 8.7 8.5 8.4 8.8 0.0
7.|-- 137.221.70.32 0.0% 10 8.3 9.6 8.2 20.5 3.8
8.|-- eqix.sv1.ppc1.com 0.0% 10 166.8 165.2 163.2 166.8 1.1
9.|-- syd-gls-har-crt1-he-0-3-0-2.tpgi.com.au 0.0% 10 159.0 159.7 155.9 162.5 2.0
10.|-- 203-219-155-221.tpgi.com.au 0.0% 10 168.4 168.4 168.3 168.4 0.0
11.|-- ip-33-93-192-203.static.pipenetworks.com 0.0% 10 176.0 176.0 175.5 177.7 0.5

30/10/2018 00:45:14 UTC
--------------------


And here are the results from the MTR site:

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192-168-1-1.tpgi.com.au - 0 | 1648 | 1648 | 0 | 0 | 4 | 0 |

| 10.20.22-139.tpgi.com.au - 0 | 1648 | 1648 | 7 | 9 | 23 | 10 |

| nme-apt-bur-wgw1-be-20.tpgi.com.au - 1 | 1645 | 1644 | 7 | 9 | 92 | 8 |

| 203-219-107-206.static.tpgi.com.au - 1 | 1645 | 1644 | 7 | 9 | 124 | 8 |

|Bundle-Ether-13.win-edge901.melbourne.telstra.net - 0 | 1648 | 1648 | 7 | 9 | 29 | 14 |

|bundle-ether11.win-core10.melbourne.telstra.net - 0 | 1648 | 1648 | 8 | 11 | 26 | 8 |

|bundle-ether12.ken-core10.sydney.telstra.net - 0 | 1648 | 1648 | 20 | 23 | 69 | 21 |

|bundle-ether1.oxf-gw10.sydney.telstra.net - 0 | 1648 | 1648 | 20 | 23 | 74 | 27 |

|bundle-ether1.sydo-core04.sydney.reach.com - 0 | 1648 | 1648 | 20 | 23 | 71 | 26 |

| i-0-0-0-3.sydo10.bi.telstraglobal.net - 0 | 1648 | 1648 | 20 | 23 | 69 | 21 |

| unknown.telstraglobal.net - 0 | 1648 | 1648 | 20 | 23 | 56 | 21 |

| 137.221.85.35 - 0 | 1648 | 1648 | 21 | 26 | 159 | 22 |

| et-0-0-1-pe01-eqsy4.as57976.net - 0 | 1648 | 1648 | 174 | 178 | 250 | 174 |

| 137.221.66.145 - 0 | 1648 | 1648 | 174 | 176 | 194 | 176 |

| 103.4.115.248 - 0 | 1648 | 1648 | 174 | 176 | 219 | 178 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Another traceroute I've done today:

Tracing route to 103.4.115.248 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 16 ms 16 ms 16 ms 210.195.127.254
3 16 ms 16 ms 16 ms 10.55.49.101
4 22 ms 21 ms 21 ms 10.55.99.178
5 51 ms 50 ms 50 ms 58.27.38.246
6 51 ms 51 ms 51 ms i-95.hkth-core02.telstraglobal.net [202.84.153.141]
7 167 ms 165 ms 164 ms i-10352.sydo-core03.telstraglobal.net [202.84.138.42]
8 165 ms 164 ms 163 ms i-0-0-0-14.sydo10.telstraglobal.net [202.84.222.194]
9 165 ms 165 ms 165 ms unknown.telstraglobal.net [210.176.152.33]
10 166 ms 166 ms 166 ms 137.221.85.35
11 265 ms 265 ms 265 ms et-0-0-0-pe02-eqsy4.as57976.net [137.221.85.73]
12 264 ms 264 ms 264 ms 103.4.115.248

Trace complete.


Here's the MTR:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 223 | 223 | 0 | 0 | 1 | 0 |
| 210.195.127.254 - 0 | 223 | 223 | 15 | 19 | 116 | 80 |
| 10.55.49.101 - 0 | 223 | 223 | 15 | 16 | 40 | 16 |
| 10.55.99.178 - 0 | 223 | 223 | 21 | 21 | 39 | 21 |
| 58.27.38.246 - 0 | 223 | 223 | 49 | 50 | 80 | 50 |
| i-95.hkth-core02.telstraglobal.net - 0 | 223 | 223 | 50 | 51 | 54 | 53 |
| i-10352.sydo-core03.telstraglobal.net - 0 | 223 | 223 | 164 | 165 | 168 | 165 |
| i-0-0-0-14.sydo10.telstraglobal.net - 0 | 223 | 223 | 163 | 164 | 211 | 164 |
| unknown.telstraglobal.net - 0 | 223 | 223 | 164 | 165 | 184 | 165 |
| 137.221.85.35 - 2 | 212 | 209 | 165 | 170 | 342 | 166 |
| et-0-0-0-pe02-eqsy4.as57976.net - 0 | 223 | 223 | 265 | 268 | 327 | 265 |
| 103.4.115.248 - 0 | 223 | 223 | 264 | 264 | 272 | 264 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
10/30/2018 08:00 PMPosted by Joynueer
Hey hey everyone,

Thank you all for the Winmtr's that have been posted. If anyone else is experiencing this issue please get us a Winmtr so we can get this looked into.

[url="https://us.battle.net/support/en/article/27780"]WinMTR[/url]
(Please put it in code blocks to make it easier to read. To do that past the report in a chat box. Then right click “Select All”-should highlight everything. Next click on the little </> symbol on the bar below the chat box.)


Thank you for looking into this. Here's some WinMTR results from me today:

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.0.1 - 0 | 389 | 389 | 0 | 0 | 8 | 1 |

| 10-20-25-5.tpgi.com.au - 0 | 389 | 389 | 21 | 24 | 271 | 23 |

| syd-apt-ros-agr11-be-24.tpgi.com.au - 0 | 389 | 389 | 22 | 27 | 272 | 26 |

| syd-apt-ros-wgw1-be-10.tpgi.com.au - 0 | 389 | 389 | 22 | 26 | 272 | 23 |

| be300.sglebbrdr11.aapt.net.au - 0 | 389 | 389 | 24 | 32 | 275 | 24 |

|TenGigE0-3-0-19.chw-edge901.sydney.telstra.net - 0 | 389 | 389 | 22 | 29 | 269 | 24 |

|bundle-ether13.chw-core10.sydney.telstra.net - 0 | 389 | 389 | 23 | 28 | 276 | 24 |

|bundle-ether1.oxf-gw11.sydney.telstra.net - 0 | 389 | 389 | 23 | 29 | 274 | 27 |

|bundle-ether2.oxf-gw10.sydney.telstra.net - 0 | 389 | 389 | 23 | 29 | 265 | 24 |

|bundle-ether1.sydo-core04.sydney.reach.com - 0 | 389 | 389 | 23 | 31 | 273 | 24 |

| i-0-0-0-15.sydo10.telstraglobal.net - 0 | 389 | 389 | 23 | 30 | 271 | 44 |

| unknown.telstraglobal.net - 0 | 389 | 389 | 24 | 29 | 275 | 28 |

| 137.221.85.35 - 0 | 389 | 389 | 24 | 34 | 276 | 25 |

| et-0-0-0-pe02-eqsy4.as57976.net - 0 | 389 | 389 | 178 | 188 | 429 | 184 |

| 103.4.115.248 - 0 | 389 | 389 | 178 | 185 | 431 | 179 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider


And another:

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.0.1 - 0 | 356 | 356 | 0 | 0 | 3 | 0 |

| 10-20-25-5.tpgi.com.au - 0 | 356 | 356 | 21 | 25 | 62 | 24 |

| syd-apt-ros-agr11-be-24.tpgi.com.au - 0 | 356 | 356 | 23 | 35 | 72 | 25 |

| syd-apt-ros-wgw1-be-10.tpgi.com.au - 0 | 356 | 356 | 22 | 29 | 77 | 23 |

| be300.sglebbrdr11.aapt.net.au - 0 | 356 | 356 | 23 | 31 | 66 | 28 |

|TenGigE0-3-0-19.chw-edge901.sydney.telstra.net - 0 | 356 | 356 | 22 | 25 | 57 | 24 |

|bundle-ether13.chw-core10.sydney.telstra.net - 0 | 356 | 356 | 24 | 33 | 60 | 24 |

|bundle-ether1.oxf-gw11.sydney.telstra.net - 0 | 356 | 356 | 25 | 34 | 77 | 32 |

|bundle-ether2.oxf-gw10.sydney.telstra.net - 0 | 356 | 356 | 23 | 31 | 61 | 28 |

|bundle-ether1.sydo-core04.sydney.reach.com - 0 | 356 | 356 | 23 | 32 | 70 | 26 |

| i-0-0-0-15.sydo10.telstraglobal.net - 0 | 356 | 356 | 22 | 28 | 70 | 25 |

| unknown.telstraglobal.net - 0 | 356 | 356 | 24 | 31 | 82 | 28 |

| 137.221.85.35 - 0 | 356 | 356 | 24 | 37 | 151 | 78 |

| et-0-0-0-pe02-eqsy4.as57976.net - 0 | 356 | 356 | 178 | 189 | 258 | 181 |

| 103.4.115.248 - 0 | 356 | 356 | 177 | 187 | 228 | 182 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Update: We made changes to help alleviate this issue! Please retest and let us know if they helped. If not please post up a WinMTR.
10/31/2018 09:50 AMPosted by Zuvykree
Update: We made changes to help alleviate this issue! Please retest and let us know if they helped. If not please post up a [url="https://battle.net/support/article/000027780?utm_source=internal-TechForum&utm_medium=posting&utm_campaign=BlizzardCS&utm_content=solution"]WinMTR[/url].


It looks like the issue has been resolved. I don't know how it all of a sudden happened in the first place but thanks very much for fixing it in a timely fashion and not simply deflecting it. Here is the WinMTR of it working fine:

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192-168-1-1.tpgi.com.au - 0 | 1043 | 1043 | 0 | 0 | 3 | 0 |

| 10.20.22-139.tpgi.com.au - 0 | 1043 | 1043 | 7 | 9 | 20 | 12 |

| nme-apt-bur-wgw1-be-20.tpgi.com.au - 0 | 1043 | 1043 | 7 | 9 | 19 | 8 |

| 203-219-107-206.static.tpgi.com.au - 0 | 1043 | 1043 | 7 | 10 | 20 | 13 |

|Bundle-Ether-13.win-edge901.melbourne.telstra.net - 0 | 1043 | 1043 | 7 | 10 | 19 | 8 |

|bundle-ether11.win-core10.melbourne.telstra.net - 0 | 1043 | 1043 | 8 | 11 | 25 | 14 |

|bundle-ether12.ken-core10.sydney.telstra.net - 0 | 1043 | 1043 | 20 | 23 | 39 | 22 |

|bundle-ether1.oxf-gw10.sydney.telstra.net - 0 | 1043 | 1043 | 20 | 23 | 32 | 23 |

|bundle-ether1.sydo-core04.sydney.reach.com - 0 | 1043 | 1043 | 20 | 23 | 35 | 23 |

| i-0-0-0-3.sydo10.bi.telstraglobal.net - 0 | 1043 | 1043 | 20 | 23 | 111 | 24 |

| unknown.telstraglobal.net - 0 | 1043 | 1043 | 20 | 23 | 44 | 21 |

| 137.221.85.35 - 0 | 1043 | 1043 | 20 | 26 | 149 | 21 |

| et-0-0-1-pe01-eqsy4.as57976.net - 0 | 1043 | 1043 | 21 | 25 | 90 | 24 |

| 137.221.66.145 - 0 | 1043 | 1043 | 20 | 23 | 29 | 24 |

| 103.4.115.248 - 0 | 1043 | 1043 | 20 | 23 | 29 | 22 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Thanks! All back to normal now for me.
Unfortunately, it isn't for me:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 779 | 779 | 0 | 0 | 1 | 0 |
| 210.195.63.254 - 1 | 775 | 774 | 15 | 23 | 147 | 17 |
| 10.55.49.101 - 1 | 771 | 769 | 16 | 17 | 71 | 16 |
| 10.55.99.178 - 0 | 778 | 778 | 21 | 21 | 51 | 21 |
| 58.27.38.246 - 1 | 775 | 774 | 49 | 50 | 92 | 50 |
| i-99.hkth-core02.telstraglobal.net - 0 | 779 | 779 | 50 | 52 | 75 | 51 |
| i-10352.sydo-core03.telstraglobal.net - 0 | 778 | 778 | 162 | 164 | 214 | 163 |
| i-0-0-0-0.sydo10.bi.telstraglobal.net - 1 | 775 | 774 | 162 | 163 | 218 | 163 |
| unknown.telstraglobal.net - 0 | 779 | 779 | 164 | 165 | 202 | 165 |
| et-0-0-48-br01-eqsy4.as57976.net - 1 | 775 | 774 | 164 | 168 | 257 | 165 |
| et-0-0-0-pe01-eqsy4.as57976.net - 1 | 775 | 774 | 263 | 266 | 328 | 264 |
| 137.221.66.145 - 0 | 778 | 778 | 263 | 264 | 274 | 264 |
| 103.4.115.248 - 0 | 778 | 778 | 263 | 264 | 272 | 264 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider


A little more info about my connectivity: connecting to the Oceanic server, but am playing from Malaysia. My usual latency ranges from 160 - 190, and currently I'm facing anywhere between 280 - 300.
Hi, Still pretty terrible here. The game is completely unplayable. I'm near Sydney. WinMTR:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 139 | 139 | 0 | 2 | 27 | 2 |
| lo0.bras22.syd7.on.ii.net - 4 | 117 | 113 | 5 | 81 | 4091 | 6 |
| be5.cr3.syd7.on.ii.net - 4 | 117 | 113 | 5 | 81 | 4091 | 8 |
| be-50.cr2.syd7.on.ii.net - 4 | 117 | 113 | 5 | 81 | 4091 | 11 |
| ae6.cr2.syd4.on.ii.net - 4 | 117 | 113 | 4 | 82 | 4091 | 9 |
| 57976.syd.equinix.com - 4 | 117 | 113 | 5 | 81 | 4089 | 8 |
| 137.221.85.35 - 4 | 117 | 113 | 6 | 85 | 4148 | 7 |
| et-0-0-1-pe01-eqsy4.as57976.net - 4 | 117 | 113 | 6 | 84 | 4091 | 7 |
| 137.221.66.145 - 4 | 117 | 113 | 6 | 81 | 4089 | 8 |
| 103.4.115.248 - 4 | 117 | 113 | 5 | 81 | 4091 | 7 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
11/01/2018 02:07 AMPosted by MeFisto
lo0.bras22.syd7.on.ii.net - 4 | 117 | 113 | 5 | 81 | 4091 | 6 |


Your issue is within your ISP. The first hop in your ISP network shouldn't be 4000+ ping...
either your connection is absolutely saturated with data throughput or your connection is stuffed.

Join the Conversation

Return to Forum