High latency on iiNet Limited and ServersAustralia ISP

200+ ping
AUS
ISP: iinet
My usual ping is 40ms and now 250+

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |  767 |  767 |    0 |   54 | 1006 |   93 |
|                              172.22.0.1 -    1 |  762 |  761 |    3 |   90 | 1284 |  232 |
|            be21.450.cr2.mel10.on.ii.net -    1 |  747 |  742 |    5 |   95 | 1294 |  233 |
|                be180.cr2.adl6.on.ii.net -    1 |  747 |  742 |  140 |  235 | 1389 |  399 |
|                 ae32.cr1.per4.on.ii.net -    1 |  754 |  751 |  141 |  237 | 1288 |  327 |
|                          150.101.34.171 -    1 |  758 |  756 |   43 |  154 | 1360 |  379 |
|             po0-3-1.bdr1.sin1.on.ii.net -    1 |  754 |  751 |  139 |  238 | 1363 |  331 |
|                   38895.sgw.equinix.com -    1 |  758 |  756 |  141 |  234 | 1365 |  411 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  154 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider`Preformatted text`

so bad how you lock the main thread saying it’s partially fixed. what sort of support is this

1 Like

Looks like iiNet is routing sub-optimally with one of their Sydney core routers. traceroute to syd2:

traceroute to 37.244.42.120 (37.244.42.120), 30 hops max, 60 byte packets
 1  10.1.0.1 (10.1.0.1)  0.277 ms  0.408 ms  0.562 ms
 2  lo0.bras2.mel11.on.ii.net (150.101.32.130)  16.243 ms  17.492 ms  18.606 ms
 3  be12.cr2.mel10.on.ii.net (150.101.35.175)  21.523 ms  22.201 ms  24.723 ms
 4  be51.cr2.mel11.on.ii.net (150.101.34.41)  33.371 ms  36.010 ms  37.117 ms
 5  be55.cr3.syd2.on.ii.net (150.101.33.36)  38.485 ms  39.561 ms  41.585 ms
 6  ae15.cr1.syd4.on.ii.net (150.101.41.121)  40.877 ms  27.724 ms  27.842 ms
 7  ae3.cr2.syd4.on.ii.net (150.101.41.123)  25.324 ms  27.296 ms  28.820 ms
 8  57976.syd.equinix.com (45.127.173.41)  177.439 ms  178.805 ms  180.346 ms
 9  et-0-0-49-br02-eqsy4.as57976.net (137.221.85.49)  33.792 ms et-0-0-49-br01-eqsy4.as57976.net (137.221.85.47)  182.618 ms  183.953 ms
10  et-0-0-0-pe01-eqsy4.as57976.net (137.221.85.67)  37.563 ms et-0-0-0-pe02-eqsy4.as57976.net (137.221.85.69)  38.877 ms et-0-0-0-pe02-eqsy4.as57976.net (137.221.85.73)  39.557 ms
11  137.221.66.133 (137.221.66.133)  202.035 ms 137.221.66.135 (137.221.66.135)  43.175 ms  43.995 ms
12  37.244.40.45 (37.244.40.45)  45.110 ms 37.244.40.37 (37.244.40.37)  26.335 ms  27.292 ms
13  * * *
14  * * *
15  37.244.42.120 (37.244.42.120)  35.807 ms  46.230 ms  25.796 ms

Note the jump in latency from ae3.cr2.syd4.on.ii.net to 57976.syd.equinix.com. There’s also nothing on iiNet’s network status page indicating that there’s an issue and that they’re routing around it.

Not sure how this is a Blizzard issue.

300+ Ping for 3 days now.
When connected to syd2, it keeps fluctuating between 60 - 120 and on PSE1 its 300+
I’m with TPG in Melbourne

EDIT - Normal ping is 40

from new caledonia
provider nautile.nc
05/07/2019 at 11.30pm

Blockquote
|-----------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|-----------------------------------------------|------|------|------|------|------|------|
| Mik-6B3306ABD29- 0 | 531 | 531 | 0 | 0 | 6 | 0 |
| gw-ntl-d.col.as45345.net- 96 | 111 | 5 | 12 | 13 | 17 | 12 |
| mx1-c7200d.bas.as45345.net- 96 | 111 | 5 | 13 | 13 | 15 | 13 |
| 202.87.128.205- 96 | 111 | 5 | 13 | 14 | 19 | 13 |
| unknown.telstraglobal.net- 96 | 111 | 5 | 35 | 37 | 39 | 36 |
| unknown.telstraglobal.net- 96 | 111 | 5 | 36 | 37 | 41 | 38 |
| i-90.sydp-core03.telstraglobal.net- 96 | 111 | 5 | 0 | 37 | 38 | 38 |
| 202.84.140.30- 96 | 111 | 5 | 86 | 88 | 93 | 87 |
| i-25154.sgcn-core01.telstraglobal.net- 96 | 111 | 5 | 129 | 131 | 140 | 129 |
| 202.84.219.173- 96 | 111 | 5 | 129 | 134 | 154 | 129 |
| 99.82.176.50- 96 | 111 | 5 | 130 | 138 | 160 | 131 |
| No response from host- 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host- 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| 52.93.10.35- 96 | 111 | 5 | 0 | 132 | 138 | 131 |
| 52.93.11.65- 96 | 111 | 5 | 0 | 130 | 132 | 129 |
| 52.93.11.78- 96 | 111 | 5 | 0 | 132 | 140 | 130 |
| 52.93.9.181- 96 | 111 | 5 | 0 | 134 | 139 | 131 |
| 52.93.10.93- 96 | 111 | 5 | 0 | 133 | 142 | 142 |
| No response from host- 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host- 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host- 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host- 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host- 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host- 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host- 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host- 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host- 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host- 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host- 100 | 107 | 0 | 0 | 0 | 0 | 0 |
| No response from host- 100 | 107 | 0 | 0 | 0 | 0 | 0 |
|___________|||||||
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

TRACEROUTE:
traceroute to 58.6.226.253 (58.6.226.253), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  2.642 ms  2.640 ms  2.727 ms
 2  24.105.18.131 (24.105.18.131)  3.395 ms  3.402 ms  3.403 ms
 3  137.221.105.12 (137.221.105.12)  2.886 ms  2.963 ms  3.044 ms
 4  137.221.66.20 (137.221.66.20)  3.327 ms  3.348 ms  3.753 ms
 5  137.221.83.68 (137.221.83.68)  8.225 ms  8.240 ms  8.245 ms
 6  137.221.65.68 (137.221.65.68)  8.094 ms  5.788 ms  5.875 ms
 7  137.221.68.32 (137.221.68.32)  6.089 ms  6.099 ms  6.262 ms
 8  * * *
 9  be1.br2.lax1.on.ii.net (150.101.33.59)  190.120 ms  190.143 ms  189.721 ms
10  te-0-0-1-5.cr3.syd2.on.ii.net (203.16.213.62)  218.550 ms  218.581 ms be1.br1.lax1.on.ii.net (150.101.33.58)  189.659 ms
11  be-50.cr2.syd2.on.ii.net (150.101.33.78)  218.588 ms xe-1-1-1.br1.syd4.on.ii.net (203.16.213.66)  190.009 ms be50.cr2.syd2.on.ii.net (150.101.33.78)  218.911 ms
12  be52.cr3.syd2.on.ii.net (150.101.41.120)  189.367 ms  189.718 ms be56.cr2.bne8.on.ii.net (150.101.33.187)  218.792 ms
13  be50.cr2.syd2.on.ii.net (150.101.33.78)  189.340 ms  189.466 ms po10.bras21.bne8.on.ii.net (150.101.34.102)  218.428 ms
14  be56.cr2.bne8.on.ii.net (150.101.33.187)  189.791 ms *  189.800 ms
15  po10.bras21.bne8.on.ii.net (150.101.34.102)  189.145 ms *  189.127 ms


05/07/2019 11:11:40 UTC
--------------------

TRACEROUTE:
traceroute to 58.6.226.253 (58.6.226.253), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  11.881 ms  11.869 ms  11.893 ms
 2  24.105.18.131 (24.105.18.131)  10.442 ms  10.468 ms  10.478 ms
 3  137.221.105.12 (137.221.105.12)  11.907 ms  11.949 ms  11.976 ms
 4  137.221.66.20 (137.221.66.20)  35.057 ms  35.376 ms  35.401 ms
 5  137.221.83.68 (137.221.83.68)  16.114 ms  16.139 ms  16.169 ms
 6  137.221.65.68 (137.221.65.68)  11.441 ms  6.939 ms  6.945 ms
 7  137.221.68.32 (137.221.68.32)  6.689 ms  10.301 ms  6.268 ms
 8  * * *
 9  be1.br2.lax1.on.ii.net (150.101.33.59)  190.135 ms  190.620 ms  190.795 ms
10  be1.br1.lax1.on.ii.net (150.101.33.58)  189.817 ms te-0-0-1-5.cr3.syd2.on.ii.net (203.16.213.62)  218.491 ms be1.br1.lax1.on.ii.net (150.101.33.58)  190.237 ms
11  be-50.cr2.syd2.on.ii.net (150.101.33.78)  218.432 ms xe-1-1-1.br1.syd4.on.ii.net (203.16.213.66)  190.414 ms 150.101.34.43 (150.101.34.43)  189.915 ms
12  be56.cr2.bne8.on.ii.net (150.101.33.187)  218.670 ms be52.cr3.syd2.on.ii.net (150.101.41.120)  189.810 ms  189.817 ms
13  po10.bras21.bne8.on.ii.net (150.101.34.102)  218.385 ms be50.cr2.syd2.on.ii.net (150.101.33.78)  189.462 ms po10.bras21.bne8.on.ii.net (150.101.34.102)  218.281 ms
14  be56.cr2.bne8.on.ii.net (150.101.33.187)  189.697 ms  189.592 ms *
15  po10.bras21.bne8.on.ii.net (150.101.34.102)  189.066 ms  189.037 ms *


05/07/2019 11:11:40 UTC
--------------------

PING:
PING 58.6.226.253 (58.6.226.253) 56(84) bytes of data.

--- 58.6.226.253 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms



05/07/2019 11:11:40 UTC
--------------------

PING:
PING 58.6.226.253 (58.6.226.253) 56(84) bytes of data.

--- 58.6.226.253 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms



05/07/2019 11:11:40 UTC
--------------------

MTR:
Start: Fri Jul  5 11:11:40 2019 Blizzard  1.|-- Blizzard                0.0%    10    0.3   0.3   0.2   0.4   0.0
  2.|-- 24.105.18.131                0.0%    10    0.6   0.6   0.5   1.1   0.0
  3.|-- 137.221.105.12               0.0%    10    0.6   0.6   0.5   0.7   0.0
  4.|-- 137.221.66.20                0.0%    10    0.9   4.5   0.8  31.3   9.5
  5.|-- 137.221.83.68                0.0%    10    5.8   5.8   5.7   5.9   0.0
  6.|-- 137.221.65.68                0.0%    10  141.0  35.4   5.7 141.0  49.2
  7.|-- 137.221.68.32                0.0%    10    6.8  17.7   5.8  43.8  15.0
  8.|-- ???                         100.0    10    0.0   0.0   0.0   0.0   0.0
  9.|-- be1.br2.lax1.on.ii.net       0.0%    10  189.7 189.8 189.6 189.9   0.0
 10.|-- be1.br1.lax1.on.ii.net       0.0%    10  189.7 198.4 189.6 218.6  13.9
 11.|-- xe-1-1-1.br1.syd4.on.ii.net  0.0%    10  189.7 196.6 189.5 218.7  12.1
 12.|-- be52.cr3.syd2.on.ii.net      0.0%    10  218.7 204.2 189.4 218.8  15.3
 13.|-- po10.bras21.bne8.on.ii.net   0.0%    10  189.4 201.0 189.3 218.5  14.9
 14.|-- be56.cr2.bne8.on.ii.net     40.0%    10  189.5 189.6 189.5 189.9   0.0
 15.|-- po10.bras21.bne8.on.ii.net  60.0%    10  189.1 189.2 189.1 189.3   0.0
 16.|-- ???                         100.0    10    0.0   0.0   0.0   0.0   0.0


05/07/2019 11:11:40 UTC
--------------------

MTR:
Start: Fri Jul  5 11:11:40 2019 Blizzard  1.|-- Blizzard               0.0%    10    0.2   0.9   0.2   5.9   1.6
  2.|-- 24.105.18.131               0.0%    10    0.5   0.6   0.5   0.7   0.0
  3.|-- 137.221.105.12              0.0%    10    0.6   0.7   0.6   1.2   0.0
  4.|-- 137.221.66.20               0.0%    10    0.9   2.6   0.9  15.3   4.5
  5.|-- 137.221.83.68               0.0%    10    5.8   6.0   5.7   8.4   0.8
  6.|-- 137.221.65.68               0.0%    10  566.7  71.9   5.6 566.7 175.1
  7.|-- 137.221.68.32               0.0%    10    5.8   5.9   5.8   6.0   0.0
  8.|-- ???                        100.0    10    0.0   0.0   0.0   0.0   0.0
  9.|-- be1.br2.lax1.on.ii.net      0.0%    10  191.0 190.1 189.7 191.0   0.0
 10.|-- be1.br1.lax1.on.ii.net      0.0%    10  190.0 198.5 189.6 218.9  13.9
 11.|-- 150.101.34.43               0.0%    10  218.5 207.3 189.5 218.7  14.6
 12.|-- be56.cr2.bne8.on.ii.net     0.0%    10  189.4 204.1 189.4 219.0  15.5
 13.|-- po10.bras21.bne8.on.ii.net  0.0%    10  218.3 203.9 189.3 218.4  15.2
 14.|-- be56.cr2.bne8.on.ii.net    30.0%    10  189.6 189.8 189.5 190.8   0.0
 15.|-- po10.bras21.bne8.on.ii.net  0.0%    10  189.4 189.4 189.1 191.2   0.6
 16.|-- ???                        100.0    10    0.0   0.0   0.0   0.0   0.0


05/07/2019 11:11:40 UTC
--------------------

PC iiNET. Now when I joined by myself in QP it put me in SEA with 170ms, but I am playing now in a group in Mystery Heroes and ping is 40ms. Not sure whats a goin on

I’m getting the same…180ms solo queue and down to 40 when in group

There’s a lot more info in this Whirlpool thread discussing the issue. Skimming through it looks like AWS not announcing routes properly: https://forums.whirlpool.net.au/thread/31wl8zv3?p=3

THIS IS NOT ISP RELATED!

Still getting put on LAX1 instead of SYD2 with Telstra.

Ever since I started connecting to SYD2 instead of PSE2 the game has felt broken even WoW has similar issues but much less noticeable

Can anyone tell me what happened to PSE2? Or why the Syd2 is showing as a peer in the Netherlands?? What happened to AWS?

Also while I’m on a rant why is there only 1 server for the whole of Australia our country is the same size as the United States Perth players with 80ms ping should not be forced to play with 1. People with 20ms higher ping that don’t speak their language or 2. Play with east coast players on 6ms ping.

Update. My ping is fluctuating really bad from 120-200

I can confirm that, like in April, using a VPN solves the issue for now. There’s a few freebies around that’ll offer enough data for a night’s worth of games. I’m using Tunnelbear at the moment and my ping is back to 40ish. not perfect but better than 180

Hello there,

Auckland, NZ based player here (ISP: Spark). I am still being connected to overseas servers occasionally, getting 150 - 250 ping.

I don’t think this is related to those two ISPs. I’m on Telstra NBN, based in Brisbane, playing on PC, and I’m having issues still. Usually I’d be getting a 42ms ping but I can’t get lower than 157ms now. Seems I’m even getting placed on syd2 as well.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                           mymodem.modem -    1 | 1042 | 1041 |    1 |   74 |  159 |   53 |
|   gateway.qb09.brisbane.asp.telstra.net -    1 | 1042 | 1041 |    9 |   87 |  229 |   92 |
|                            203.50.25.20 -    1 | 1042 | 1041 |   11 |   88 |  171 |   47 |
|bundle-ether20.chw-core10.sydney.telstra.net -    1 | 1042 | 1041 |   21 |   99 |  182 |   34 |
|bundle-ether1.oxf-gw11.sydney.telstra.net -    1 | 1042 | 1041 |   23 |   99 |  185 |   34 |
|bundle-ether2.oxf-gw10.sydney.telstra.net -    1 | 1042 | 1041 |   23 |  100 |  185 |   46 |
|bundle-ether1.sydo-core04.sydney.reach.com -    1 | 1042 | 1041 |   22 |   98 |  179 |  171 |
|           i-91.sydo10.telstraglobal.net -    1 | 1042 | 1041 |   17 |   97 |  178 |   57 |
|               unknown.telstraglobal.net -    1 | 1042 | 1041 |   22 |  103 |  244 |  171 |
|                           137.221.85.35 -    1 | 1042 | 1041 |   19 |  103 |  237 |   91 |
|         et-0-0-0-pe02-eqsy4.as57976.net -    1 | 1042 | 1041 |   21 |   99 |  227 |   73 |
|                          137.221.66.135 -    1 | 1042 | 1041 |   24 |   99 |  184 |   75 |
|                            37.244.40.21 -    1 | 1042 | 1041 |   23 |   98 |  183 |   43 |
|                   No response from host -  100 |  210 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  210 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  210 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  210 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  210 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  210 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  210 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  210 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  210 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  210 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  210 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  210 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  210 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  210 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  210 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  210 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  210 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Whats worse is that sometimes you believe its fixed and get your old ping back and then join competitive for a couple and have your normal experience and then next one bang your suspended. How the hell do you expect us to continue to test this even when we have reported and you are aware of the issue and you report issues as partially resolved. I tested the AI create game and had mixed results, then got in a few QP matches and pings sub 40. Join competitive for one match and complete without issues and then next one lose SR and banned…

How can the issue have affected so many ISP’s in unison? are all these ISP’s to blame and now changing their routing to accommodate blizz servers? doubt it!

You guys made the change, please correct it with iinet promptly.

edit: I’m getting connected via SYD2 also and still
having the ping issues

I have high Latency also 150 - 300 MS normal is 40MS
been happening the last few days since season 17

ISP Optus

2019-07-04T14:00:00Z

This is such a bad experience for me an I am done OW for a while. Basically rolling the dice every game to hope I would land on a local server. I know this going to take you a while to get this fixed, but please make an announcement on twitter or the blizzard launcher once you have addressed the issue.

1 Like

Telstra NBN, wife and I last 3 nights try to join competitive grouped for placements. Sit in skirmish forever with no other players except us and placement matches wont start. Only happened since the new patch. QP works but is laggy.

Your main issue is your wifi/modem you shouldn’t be getting more than 1-2ms on your first hop (to your router) over Ethernet and no more than ~6ms over wifi, I can see you’re getting average latency to your router of 74ms that’s not good fix that first. Also in Brisbane you should be getting less than 40ms I’m in Townsville and when it’s good it’s 46ms and I’m like 19ms from Brisbane.

Thanks for the continued reports, everyone!

We are currently investigating two separate issues affecting Oceanic players. Please refer to the thread which describes your issue:

High latency on regional servers

Being placed in incorrect regional servers