New Zealand being forced to LAX1

Yeah, I accept people have to go home for the weekend. But if there’s anywhere to complain about it, it’s here. And personally I’m not mad, just disappointed and upset I can’t play my favourite game :frowning:

2 Likes

Having this problem too. NZ with Vodafone fibre

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

|                                      WinMTR statistics                                   |

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

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

|                            ultrahub.hub -    0 |   59 |   59 |    0 |    0 |    6 |    0 |

|             121-75-71-254.dyn.vf.net.nz -    0 |   59 |   59 |    1 |    7 |   90 |    4 |

|                            10.200.12.25 -    0 |   59 |   59 |    8 |   10 |   14 |   11 |

|                               195.2.7.6 -    0 |   59 |   59 |  144 |  146 |  151 |  148 |

|                xe-5-1-0-xcr1.lax.cw.net -    0 |   59 |   59 |  145 |  147 |  167 |  148 |

|                    ae21-xcr2.ash.cw.net -    0 |   59 |   59 |  199 |  202 |  210 |  202 |

|                     ae0-xcr1.ash.cw.net -    0 |   59 |   59 |  199 |  202 |  234 |  202 |

|                   eqix-dc2.blizzard.com -    0 |   59 |   59 |  199 |  204 |  246 |  201 |

|              ae1-br01-eqdc2.as57976.net -    0 |   59 |   59 |  215 |  219 |  245 |  216 |

|         et-0-0-2-br01-eqch2.as57976.net -    0 |   59 |   59 |  217 |  224 |  272 |  243 |

Trace Route from the other day

Tracing route to 37.244.42.108 over a maximum of 30 hops

1 1 ms 1 ms <1 ms ultrahub.hub [192.168.1.1]
2 5 ms 5 ms 2 ms 121-75-71-254.dyn.vf.net.nz [121.75.71.254]
3 11 ms 13 ms 13 ms 10.200.12.25
4 146 ms 145 ms 147 ms vodafone-nz-ltd.10gigabitethernet6-11.core1.lax2.he.net [216.218.236.102]
5 147 ms 145 ms 145 ms v106.core1.lax2.he.net [216.218.236.101]
6 146 ms 149 ms 149 ms 100ge2-2.core1.lax1.he.net [72.52.92.121]
7 * * * Request timed out.
8 210 ms 235 ms 236 ms ae1-br02-eqla1.as57976.net [137.221.68.35]
9 177 ms 177 ms 177 ms xe-0-0-0-0-br01-eqsv5.as57976.net [137.221.65.7]
10 178 ms 180 ms 177 ms et-0-0-29-br01-eqsv5.as57976.net [137.221.65.116]
11 178 ms 180 ms 177 ms xe-0-0-0-0-br01-eqse2.as57976.net [137.221.65.41]
12 180 ms 177 ms 211 ms xe-0-0-8-br01-eqsy4.as57976.net [137.221.65.97]
13 179 ms 178 ms 184 ms et-0-0-0-pe01-eqsy4.as57976.net [137.221.85.67]
14 177 ms 177 ms 177 ms 137.221.66.133
15 179 ms 176 ms 177 ms 37.244.40.37

i guess the only option left is to quite Overwatch, sad.

Same issue for me too. :frowning: very frustrating Blizzard

eh honestly might aswell just quit. its clear blizzard are just racist against NZ they dont care enough about us. we are to small a market for them. rip overwatch. guess ill go play R6S

2 Likes

Hey again all,

We should be good on tests for this issue, it looks like you’re still getting routed to our servers the wrong way - we’ve got an internal ticket on this where we’re investigating why this is happening and seeing if we can make any headway on it. While we do so it can sometimes help if you notify Vodafone as well. This is a peering issue and they can speed things up by working with our network folks to use better peers to connect to us.

We fixed this with a couple other ISPs a few days ago but we’re still working on Vodafone.

2 Likes

Are we able to find out when this maybe expected to be working again? Just a general date from now like a week or a couple days

there is already a ticket opened with vodafone it was opened on friday IIRC

2 Likes

VFNZ are learning your routes via the Equinix route-servers.
We notice that when patches are preformed on game servers etc we see a result in traffic going via the USA

3 Likes

I did manage to connect to the Sydney 2 server but my ping was 210ms, I normally get around 40ms.
I did a tracert and these are the results
I had to remove some of the links, I hope this helps
I’m on Vodafone fibre and in Auckland
1 <1 ms <1 ms <1 ms ultrahub.hub [192.168.1.1]
2 2 ms 2 ms 3 ms 203-173-195-254.dsl.dyn.ihug.co.nz [203.173.195.254]
3 * * * Request timed out.
4 130 ms 130 ms 130 ms 10.200.12.159
5 128 ms 130 ms 130 ms 38.88.197.206
6 134 ms 128 ms 131 ms 38.88.197.205
7 130 ms 131 ms 130 ms 154.54.9.30
8 128 ms 130 ms 130 ms 129.250.3.237
9 212 ms 196 ms 198 ms 129.250.3.192
10 197 ms 199 ms 205 ms 129.250.6.129
11 197 ms 200 ms 196 ms 129.250.5.51]
12 265 ms 246 ms 247 ms 61.213.179.114
13 196 ms 199 ms 196 ms 137.221.81.35
14 195 ms 199 ms 262 ms 137.221.65.121
15 197 ms 199 ms 216 ms 137.221.85.73]
16 200 ms 198 ms 199 ms 137.221.66.135
17 198 ms 199 ms 198 ms 37.244.40.25

okay - so I am connecting to SYD2 servers, but half way through the WinMRT it states it’s connecting to LAX2, so the routing is going to America and then back to Syd2. You should be able to see that from Trace Route.

Currently playing on Quickplay to test it and add WinMRT file, but any game. I am 190+ ping. To Sydney servers without any instability on my side, I’ve got a ping check and a winMRT file for proof. Needs to be fixed ASAP with the ISP.

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

| WinMTR statistics |

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

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

| NB304N.Home - 1 | 333 | 332 | 0 | 0 | 24 | 3 |

| 254.139.252.27.dyn.cust.vf.net.nz - 1 | 333 | 332 | 17 | 25 | 112 | 23 |

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

| 10.200.12.157 - 1 | 333 | 332 | 142 | 148 | 202 | 143 |

|vodafone-nz-ltd.10gigabitethernet6-11.core1.lax2.he.nett - 1 | 333 | 332 | 142 | 147 | 202 | 147 |

| v106.core1.lax2.he.nett - 1 | 333 | 332 | 141 | 150 | 255 | 172 |

| 100ge2-2.core1.lax1.he.nett - 2 | 317 | 312 | 142 | 151 | 287 | 145 |

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

| ae1-br02-eqla1.as57976.nett - 1 | 333 | 332 | 172 | 184 | 288 | 173 |

| xe-0-0-0-0-br01-eqsv5.as57976.nett - 1 | 333 | 332 | 172 | 178 | 264 | 173 |

| et-0-0-29-br01-eqsv5.as57976.nett - 1 | 333 | 332 | 172 | 179 | 256 | 174 |

| xe-0-0-0-0-br01-eqse2.as57976.nett - 1 | 329 | 327 | 172 | 179 | 260 | 174 |

| xe-0-0-8-br01-eqsy4.as57976.nett - 1 | 329 | 327 | 172 | 184 | 308 | 173 |

| et-0-0-0-pe01-eqsy4.as57976.nett - 1 | 333 | 332 | 171 | 179 | 258 | 172 |

| 137.221.66.145 - 1 | 329 | 327 | 171 | 176 | 223 | 172 |

| 103.4.115.248 - 1 | 329 | 327 | 171 | 176 | 231 | 173 |

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

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

I have duplicated the last letter of the routers it was passing through, due to the support ticket not letting me post it, thinking they were links to different URL’s

For example .net = .nett

6 days gamers, stay strong

2 Likes

I swear to god they better fix it by tomorrow :frowning:

In my case it is routing through to LA, then through Tokyo and to Sydney and back

I just did another test, and it routed me through ORD1. Chicago - So kinda hate this atm. Really need to get it fixed.

It’s a Vodafone and blizzard issue and they are apparently fixing it right now. Other ISPs are fixed but it’s mainly Vodafone

They advise people to contact Vodafone about the connection issue

All I want to know is when the hell will this be fixed

has it been fixed yet guys?

They are going to post on this forum when it’s fixed which will probably be a while considering they haven’t still yet replied with a resolved issue

1 whole week now, DAY 7 GIVE IT UP FOR DAYYYYYYYYY 7

1 Like

Not done yet! This is ‘BLIZZARD’

1 Like