New Zealand being forced to LAX1

Technical Support
1

Hi, i keep being forced onto Lax 1 after restarting and also trying to open custom games in my region but no success getting back to syd1 or syd2, here is my WinMTR test results

                                  WinMTR statistics                                   |

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

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

| - 0 | 276 | 276 | 0 | 5 | 59 | 1 |

| 219-89-72-1-fibre.sparkbb.co.nz - 0 | 276 | 276 | 2 | 8 | 59 | 31 |

| 222.152.41.165 - 0 | 276 | 276 | 2 | 10 | 44 | 30 |

| 122.56.113.4 - 0 | 276 | 276 | 2 | 4 | 27 | 4 |

| ae2-6.tkbr12.global-gateway.net.nz - 0 | 276 | 276 | 2 | 4 | 42 | 3 |

| xe1-0-4.sebr3.global-gateway.net.nz - 0 | 275 | 275 | 25 | 26 | 40 | 26 |

| xe0-1-0-10.hmbr1.global-gateway.net.nz - 0 | 275 | 275 | 141 | 143 | 183 | 141 |

| ae0-10.hmbr2.global-gateway net nz - 0 | 275 | 275 | 141 | 161 | 241 | 173 |

| 4657.hkg.equinix com - 0 | 275 | 275 | 172 | 184 | 217 | 174 |

| 203.118.6.86 - 0 | 275 | 275 | 188 | 192 | 229 | 188 |

| 203.118.6.101 - 0 | 275 | 275 | 175 | 185 | 221 | 176 |

| 203.117.163.174 - 0 | 275 | 275 | 175 | 187 | 288 | 176 |

| et-0-0-48-br01-eqsg3.as57976 net - 0 | 275 | 275 | 198 | 203 | 284 | 213 |

| ge-0-0-4-br01-eqty2.as57976 net - 0 | 275 | 275 | 197 | 203 | 288 | 209 |

| et-0-0-49-br02-eqty2.blizzardonline net - 0 | 275 | 275 | 197 | 207 | 301 | 198 |

| ge-0-0-8-br02-eqsy4.as57976 net - 0 | 275 | 275 | 197 | 209 | 320 | 198 |

| et-0-0-1-pe01-eqsy4.as57976 net - 0 | 275 | 275 | 197 | 216 | 280 | 227 |

|

10 Likes
2

Same here, all day on LAX
NZ

1 Like
3

Just noticed this too, hopefully a fix will be issued soon and not like last time. :pleading_face:

Spark | NZ | LAX1 24.105.14.252

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

|                                      WinMTR statistics                                   |

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

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

|                           192.168.1.254 -    0 |  158 |  158 |    0 |    0 |    4 |    1 |

|        125-239-244-1-adsl.sparkbb.co.nz -    0 |  151 |  151 |   16 |  178 | 4081 |   17 |

|                   No response from host -  100 |   32 |    0 |    0 |    0 |    0 |    0 |

|                            122.56.113.4 -    0 |  158 |  158 |   29 |   32 |   55 |   32 |

|       ae7-2.akbr7.global-gateway.net.nz -    0 |  158 |  158 |   28 |   30 |   62 |   34 |

|  xe7-0-8-10.sjbr3.global-gateway.net.nz -    0 |  158 |  158 |  153 |  154 |  178 |  156 |

|         ae0.pabr5.global-gateway.net.nz -    0 |  158 |  158 |  153 |  155 |  178 |  165 |

|      xe-4-0-0.mpr1.pao1.us.zip.zayo.com -    0 |  158 |  158 |  153 |  155 |  198 |  161 |

|            ae9.cs1.sjc2.us.eth.zayo.com -    0 |  158 |  158 |  155 |  156 |  181 |  155 |

|           ae27.cr1.sjc2.us.zip.zayo.com -    0 |  158 |  158 |  154 |  156 |  178 |  155 |

|          ae16.mpr3.sjc7.us.zip.zayo.com -    0 |  158 |  158 |  161 |  164 |  224 |  165 |

|                eqix-ix-sv1.blizzard.com -    0 |  158 |  158 |  155 |  160 |  234 |  160 |

|              ae1-br02-eqsv5.as57976.net -    0 |  158 |  158 |  155 |  157 |  181 |  156 |

|       xe-0-0-1-1-br02-eqla1.as57976.net -    0 |  158 |  158 |  170 |  183 |  295 |  181 |
|________________________________________________|______|______|______|______|______|______|

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

same here blizzard please fix

1 Like
5

last time indeed.
Wasnt that like just under a week to fix? :hushed:

6

I think last time they mentioned that the AU server is managed by a US team and their office hours didnt match our ANZ time zones.
So it took days .

1 Like
7

So this is why I’m being shanked in the … by latency issues?

2 Likes
8

this again seriously is it a monthly event now? wrong servers, lag , hated by your team coming sept 26-who knows. but really this happens way to often

2 Likes
9

Again support is blaming our ISPs :slight_smile: round and round we go

1 Like
10

Took around 5 days or less before it was solved. Happened during a holiday in the US so this should be solved much quicker hopefully.

2 Likes
11

well that’s the thing, support hasn’t said anything yet as they probably haven’t read this yet … Even though its been an issue all day.

They wont be awake for ages yet :confused:

1 Like
12

Support won’t directly reply to posts unless they have results/answers. They are aware as I’ve just asked about it. So expect them to respond when they’ve either solved or have an update in regards to this matter.

In the meantime run a winMTR and comment below, include your ISP, Country, and connecting server IP (Example LAX1 - 24.105… etc)

13

Also been having this issue all day(LAX1), second time this has happened. Honestly it’s like blizzard want me to stop playing at this point I stg

14

I just checked am I am connecting to “syd2” with high ping (250) so maybe it is a NZ thing (CRTL+SHIFT+N) FYI for those who dont know

15

I’m on Spark Fibre as well,

Being routed to [NA]LAX1 instead of PSE2[AU] looks like we are having that issue back in July again. Are our lovely neighbours across the ditch being affected too I wonder.

16

Can confirm, getting 186ms in Nz.

17

same here, getting 170ms in nz

18

I should have 40ms ping normally, but all of sudden, from last night I get 160~190ms.
every other connection is normal with under 20~30ms, no packet loss.
Can someone please help me fix this?

So far, I have done

  1. DNS flush & using 8.8.8.8 / 8.8.4.4 to test.
  2. Power cycle router
  3. Network driver update
  4. Firewall check
  5. Turn off every other network-related programs.

Below is my traceroute result from Looking Glass.

TRACEROUTE:
traceroute to 118.92.5.138 (118.92.5.138), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.648 ms 0.767 ms 0.785 ms
2 24.105.18.3 (24.105.18.3) 0.916 ms 0.997 ms 1.130 ms
3 137.221.105.12 (137.221.105.12) 3.312 ms 3.322 ms 3.256 ms
4 137.221.66.16 (137.221.66.16) 3.261 ms 3.268 ms 3.275 ms
5 137.221.83.66 (137.221.83.66) 167.050 ms 167.073 ms 167.086 ms
6 137.221.65.68 (137.221.65.68) 166.882 ms 166.907 ms 166.892 ms
7 137.221.65.1 (137.221.65.1) 224.060 ms 223.858 ms 223.838 ms
8 137.221.65.7 (137.221.65.7) 166.532 ms 166.641 ms 166.667 ms
9 137.221.65.116 (137.221.65.116) 166.708 ms 166.649 ms 166.618 ms
10 137.221.65.41 (137.221.65.41) 166.554 ms 166.622 ms 167.516 ms
11 137.221.65.97 (137.221.65.97) 166.488 ms 166.500 ms 166.595 ms
12 137.221.85.32 (137.221.85.32) 167.079 ms 166.870 ms 168.534 ms
13 * * *
14 * * *
15 * * *

26/09/2019 14:39:36 UTC

TRACEROUTE:
traceroute to 118.92.5.138 (118.92.5.138), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.289 ms 0.301 ms 0.313 ms
2 24.105.18.3 (24.105.18.3) 0.610 ms 0.725 ms 0.813 ms
3 137.221.105.12 (137.221.105.12) 1.466 ms 1.493 ms 1.504 ms
4 137.221.66.16 (137.221.66.16) 1.396 ms 1.431 ms 1.459 ms
5 137.221.83.66 (137.221.83.66) 166.749 ms 166.782 ms 166.796 ms
6 137.221.65.68 (137.221.65.68) 166.529 ms 166.696 ms 166.688 ms
7 137.221.65.1 (137.221.65.1) 211.840 ms 211.530 ms 211.480 ms
8 137.221.65.7 (137.221.65.7) 166.755 ms 166.797 ms 166.808 ms
9 137.221.65.116 (137.221.65.116) 166.793 ms 166.808 ms 166.810 ms
10 137.221.65.41 (137.221.65.41) 166.665 ms 166.616 ms 166.581 ms
11 137.221.65.97 (137.221.65.97) 166.731 ms 166.693 ms 166.545 ms
12 137.221.85.32 (137.221.85.32) 167.040 ms 166.883 ms 166.897 ms
13 * * *
14 * * *
15 * * *

26/09/2019 14:39:36 UTC

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

— 118.92.5.138 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3007ms

26/09/2019 14:39:36 UTC

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

— 118.92.5.138 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3006ms

26/09/2019 14:39:36 UTC

MTR:
Start: Thu Sep 26 14:39:36 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.5 0.0
2.|-- 24.105.18.3 0.0% 10 0.7 0.8 0.6 1.3 0.0
3.|-- 137.221.105.12 0.0% 10 1.0 1.0 0.8 1.8 0.0
4.|-- 137.221.66.16 0.0% 10 1.1 2.8 0.8 10.0 3.1
5.|-- 137.221.83.66 0.0% 10 166.6 169.0 166.5 187.7 6.6
6.|-- 137.221.65.68 0.0% 10 166.8 170.2 166.6 188.4 7.6
7.|-- 137.221.65.1 0.0% 10 168.5 171.8 166.6 194.9 9.9
8.|-- 137.221.65.7 0.0% 10 166.7 166.8 166.6 166.9 0.0
9.|-- 137.221.65.116 0.0% 10 166.8 167.6 166.6 171.2 1.3
10.|-- 137.221.65.41 0.0% 10 166.7 166.8 166.7 167.3 0.0
11.|-- 137.221.65.97 0.0% 10 166.8 174.5 166.7 244.3 24.5
12.|-- 137.221.85.32 0.0% 10 166.8 170.6 166.6 199.4 10.1
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

26/09/2019 14:39:36 UTC

MTR:
Start: Thu Sep 26 14:39:36 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.4 0.2 1.0 0.0
2.|-- 24.105.18.3 0.0% 10 0.7 2.3 0.5 17.7 5.4
3.|-- 137.221.105.12 0.0% 10 0.9 0.9 0.8 1.2 0.0
4.|-- 137.221.66.16 0.0% 10 1.1 7.0 0.8 60.9 18.9
5.|-- 137.221.83.66 0.0% 10 166.7 171.6 166.6 210.5 13.7
6.|-- 137.221.65.68 0.0% 10 166.7 175.5 166.6 227.5 19.1
7.|-- 137.221.65.1 0.0% 10 166.7 167.1 166.6 170.9 1.3
8.|-- 137.221.65.7 0.0% 10 166.6 166.7 166.6 167.2 0.0
9.|-- 137.221.65.116 0.0% 10 166.7 166.6 166.6 166.8 0.0
10.|-- 137.221.65.41 0.0% 10 200.3 170.0 166.5 200.3 10.6
11.|-- 137.221.65.97 0.0% 10 166.6 166.7 166.6 166.8 0.0
12.|-- 137.221.85.32 0.0% 10 166.8 168.9 166.7 185.9 6.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

26/09/2019 14:39:36 UTC

19

Ever since the bastion update I have been connecting to NA server to start my game instead rerouting to sea servers, resulting in at least 170-220 ping for all my games. My last normal play was on the 13th Sep. The Bizzare part is I tried grouping with my friends and play games on sea severs, and he would get 50ping while I am at 220(Yes we are in the same game). My friend lives in Thailand and me in HK and I usually get 40 ping for my games. Thank you in advance.

20

I think this is related to a new route being used by your ISP. Maybe they have maintenance on a hub that connects you with your normal ping. The best way to test if it’s your ISP would be to try another form of internet connection, like mobile phone data. Otherwise, try a VPN (a free one is okay if you don’t have one) and see if you can get better ping with that. If the answer is yes to either of these, it’s your ISP’s routing that has changed.