Hey all,
We pushed some changes to peering networks and ISPs that may have resolved this. Is anyone still being impacted by this routing issue? If yes please let us know. Be sure to include an MTR report if possible.
Thanks!
Hey all,
We pushed some changes to peering networks and ISPs that may have resolved this. Is anyone still being impacted by this routing issue? If yes please let us know. Be sure to include an MTR report if possible.
Thanks!
Hi there, logged in this morning and I still have about 200ms, sometimes fluctuating up to 300ms. My ISP is Vodafone NZ.
Iām not sure what to tell them if I call them up, and they donāt have an email address available to contact them and send an MTR report so everythingās mostly done by phone usually. Anyway, Iāve attached an updated MTR report:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 505 | 505 | 0 | 2 | 117 | 5 |
| 254.187.252.27.dyn.cust.vf.net.nz - 0 | 505 | 505 | 7 | 24 | 400 | 8 |
| No response from host - 100 | 102 | 0 | 0 | 0 | 0 | 0 |
| 10.200.12.157 - 1 | 501 | 500 | 132 | 136 | 296 | 133 |
| 38.88.197.206 - 0 | 505 | 505 | 131 | 135 | 288 | 137 |
|te0-1-0-1.ccr41.lax04.atlas.cogentco. com - 0 | 505 | 505 | 131 | 134 | 271 | 137 |
| ntt.lax04.atlas.cogentco. com - 0 | 505 | 505 | 146 | 149 | 274 | 147 |
| ae-2.r23.lsanca07.us.bb.gin.ntt. net - 2 | 478 | 471 | 147 | 150 | 273 | 149 |
| ae-12.r31.tokyjp05.jp.bb.gin.ntt. net - 0 | 505 | 505 | 193 | 198 | 420 | 194 |
| ae-3.r01.tokyjp08.jp.bb.gin.ntt. net - 1 | 501 | 500 | 193 | 198 | 403 | 195 |
| ae-2.a00.tokyjp03.jp.bb.gin.ntt. net - 0 | 505 | 505 | 196 | 203 | 428 | 202 |
| 61.213.179.114 - 0 | 505 | 505 | 240 | 250 | 429 | 242 |
| 137.221.81.35 - 0 | 505 | 505 | 192 | 201 | 420 | 194 |
| ge-0-0-8-br02-eqsy4.as57976. net - 0 | 505 | 505 | 192 | 201 | 420 | 220 |
| et-0-0-0-pe02-eqsy4.as57976. net - 0 | 505 | 505 | 192 | 200 | 426 | 193 |
| 103.4.115.248 - 0 | 505 | 505 | 192 | 197 | 418 | 197 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Hope this helps, thank you.
Please do all you can from your end Blizzard to communicate this issue with Oceanic ISPās - trying to contact them as individuals to report something like this (especially Vodafone) is an exercise in futility.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
192.168.1.1 - 0 | 448 | 448 | 0 | 0 | 23 | 0 |
118-92-215-254.dsl.dyn.ihug.co.nz - 0 | 448 | 448 | 8 | 17 | 131 | 28 |
10.200.12.21 - 0 | 448 | 448 | 8 | 12 | 39 | 12 |
38.88.197.206 - 0 | 448 | 448 | 141 | 146 | 184 | 147 |
te0-1-0-1.ccr41.lax04.atlas.cogentco. com - 0 | 448 | 448 | 141 | 145 | 179 | 142 |
ntt.lax04.atlas.cogentco. com - 0 | 448 | 448 | 154 | 158 | 192 | 159 |
ae-2.r23.lsanca07.us.bb.gin.ntt. net - 1 | 440 | 438 | 155 | 159 | 191 | 156 |
ae-12.r31.tokyjp05.jp.bb.gin.ntt. net - 0 | 448 | 448 | 196 | 201 | 272 | 202 |
ae-3.r01.tokyjp08.jp.bb.gin.ntt. net - 0 | 448 | 448 | 196 | 200 | 231 | 201 |
ae-2.a00.tokyjp03.jp.bb.gin.ntt. net - 0 | 448 | 448 | 196 | 201 | 229 | 202 |
61.213.179.114 - 0 | 448 | 448 | 244 | 253 | 336 | 250 |
137.221.81.35 - 0 | 448 | 448 | 196 | 204 | 303 | 246 |
ge-0-0-8-br02-eqsy4.as57976. net - 0 | 448 | 448 | 197 | 204 | 306 | 199 |
et-0-0-1-pe01-eqsy4.as57976. net - 0 | 448 | 448 | 196 | 202 | 268 | 199 |
137.221.66.133 - 0 | 448 | 448 | 195 | 200 | 232 | 202 |
37.244.40.29 - 0 | 448 | 448 | 196 | 200 | 226 | 203 |
No response from host - 100 | 89 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 89 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 89 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 89 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 89 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 89 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 89 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 89 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 89 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 89 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 89 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 89 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 89 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 89 | 0 | 0 | 0 | 0 | 0 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Hi there,
I also am with vodafone, however have a fibre optic connection, below is my results. Its only WOW BFA that seems to be an issue, tried other games like csgo and had 25ms. Thanks
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| ultrahub.hub - 0 | 3461 | 3461 | 0 | 0 | 11 | 0 |
| UNASSIGNED.static.cust.vf.net.nz - 0 | 3461 | 3461 | 2 | 19 | 252 | 2 |
| No response from host - 100 | 693 | 0 | 0 | 0 | 0 | 0 |
| 10.200.12.159 - 0 | 3461 | 3461 | 126 | 128 | 166 | 128 |
[|vodafone-nz-ltd.10gigabitethernet6-11.core1.lax2.he. net] - 0 | 3461 | 3461 | 126 | 128 | 204 | 128 |
| v106.core1.lax2.he. net - 0 | 3461 | 3461 | 127 | 131 | 232 | 133 |
| 100ge2-2.core1.lax1.he. net - 0 | 3461 | 3461 | 127 | 129 | 337 | 129 |
| No response from host - 100 | 693 | 0 | 0 | 0 | 0 | 0 |
| ae1-br02-eqla1.as57976. net - 0 | 3461 | 3461 | 157 | 166 | 290 | 159 |
| xe-0-0-0-0-br01-eqsv5.as57976. net - 0 | 3461 | 3461 | 157 | 159 | 269 | 160 |
| et-0-0-29-br01-eqsv5.as57976. net - 0 | 3461 | 3461 | 156 | 160 | 261 | 158 |
| xe-0-0-0-0-br01-eqse2.as57976. net - 0 | 3461 | 3461 | 156 | 160 | 269 | 159 |
| xe-0-0-8-br01-eqsy4.as57976. net - 0 | 3461 | 3461 | 157 | 163 | 348 | 157 |
| et-0-0-0-pe01-eqsy4.as57976. net - 0 | 3461 | 3461 | 156 | 160 | 231 | 158 |
| 137.221.66.145 - 0 | 3461 | 3461 | 157 | 158 | 173 | 157 |
| 103.4.115.248 - 0 | 3461 | 3461 | 156 | 158 | 170 | 157 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
same issue, still happening, 200+ ms since yesterday, all traffic to blizzard servers is being routed through japan.
I am with vodafone as well, same issue, and same issue with trying to contact them - weād have more luck at having Invincible drop than getting any meaningful help from Vodafone.
This is sucks, still same issue and even higher latency around 190+ ms, guess its bliz prob not ISPās. Happened only after patch released. Please fix the bug, we paid for game not paid for suffering
im with vodafone in new zealand
Im getting 200+ ms
please fix whatever has caused this, im usually getting 30ms
Using a VPN fixes it, guess weāre going to have to wait for our sh*t ISP to fix itā¦
I can fix it by using a NZ VPN, so itās definitely a ISP issue rather than a blizz one.
Iām seeing this same issue. I use Aussie Broadband in North QLD.
Itās noticeable from Asia as well, a solid 200-250ms more latency. Iām usually around 135-145ms to Oceanic realms or the other way to US realms at about 140-150ms, however today itās 350-400ms to Oceanic realms and the same 140-150ms to US realms.
I noticed my ping to US-West from NZ went high as well from 150 to 200ms today.
Same issues - Spark is my ISP. Havenāt logged in for 5 days or so, everything fine until logging in an hour ago, post-patch. Will do a test thing tomorrow when the Guy is around to do it for me.
Hi there friends!
It looks like most of the New Zealand issues should be resolved. It seems mainly Vodafone and ISPs routed through them have the issue still. We ask that you continue to post back with WinMTRs and help us out find the problem.
Thanks for being an awesome community!
/Nathardrick
Has anyone else noticed latency issues/changes to oceanic realms?
From what i can see it seems like its all routing through telstra? normally blizzard announces their routes to better paths such as peering fabrics (equinix or IX australia).
Using this aussie looking glass aggregate you can traces yourself - www(DOT)ausnog(DOT)net/tools/lg
For example Remulos - 37.244.42.179 (use tcpview or something to find the IP of the server youre connecting to):
Vocus:
traceroute to 37.244.42.179 (37.244.42.179), 30 hops max, 60 byte packets
1 175.45.91.193 (175.45.91.193) 0.444 ms 0.433 ms 0.584 ms
2 ten-2-2-0-101.bdr03.syd04.nsw.vocus.net.au (175.45.73.1) 0.868 ms 0.864 ms 0.897 ms
3 te-0-1-0-3-4.cor02.syd04.nsw.vocus.net.au (175.45.72.76) 1.592 ms 1.170 ms 1.160 ms
4 bundle-101.bdr01.syd11.nsw.vocus.net.au (114.31.192.83) 2.317 ms 2.555 ms 2.569 ms
5 bundle-ether12.ken-edge903.sydney.telstra. net (203.27.185.57) 11.263 ms 1.355 ms 11.918 ms
6 bundle-ether17.ken-core10.sydney.telstra. net (203.50.11.172) 7.682 ms 3.790 ms 8.230 ms
7 bundle-ether1.oxf-gw10.sydney.telstra. net (203.50.6.97) 2.765 ms 7.045 ms 13.301 ms
8 bundle-ether1.sydo-core04.sydney.reach. com (203.50.13.94) 7.669 ms 13.981 ms 7.595 ms
9 i-91.sydo10.telstraglobal. net (202.84.222.198) 7.448 ms 12.377 ms 5.837 ms
10 * * *
11 * * *
12 * * *
Tpg/aapt:
1 gi9-9.sglebdist01.nw.aapt.net.au (202.10.15.152) [MPLS: Label 533 Exp 0] 0 msec
gi9-9.sglebdist02.nw.aapt.net.au (202.10.15.154) [MPLS: Label 458 Exp 0] 0 msec
gi9-9.sglebdist01.nw.aapt.net.au (202.10.15.152) [MPLS: Label 533 Exp 0] 0 msec
2 bu9.sglebbrdr11.aapt.net.au (202.10.14.29) 0 msec
bu8.sglebbrdr11.aapt.net.au (202.10.14.27) 0 msec
bu9.sglebbrdr11.aapt.net.au (202.10.14.29) 4 msec
3 TenGigE0-3-0-19.chw-edge901.sydney.telstra. net (139.130.209.229) [AS 1221] 0 msec 0 msec 0 msec
4 bundle-ether13.chw-core10.sydney.telstra. net (203.50.11.98) [AS 1221] 0 msec 4 msec 0 msec
5 bundle-ether1.oxf-gw11.sydney.telstra. net (203.50.6.93) [AS 1221] 4 msec 0 msec 4 msec
6 bundle-ether2.oxf-gw10.sydney.telstra. net (203.50.6.94) [AS 1221] 0 msec 4 msec 0 msec
7 bundle-ether1.sydo-core04.sydney.reach. com (203.50.13.94) [AS 1221] 4 msec 0 msec 4 msec
8 i-91.sydo10.telstraglobal. net (202.84.222.198) [AS 4637] 0 msec 4 msec 0 msec
9 * * *
iinet: says a direct bgp session so they might be ok
Tracing the route to 37.244.42.179
1 gi1-2-950.cor1.syd6.on.ii.net (150.101.199.50) 0 msec 0 msec 0 msec
2 te-0-9-1-3.cr2.syd7.on.ii.net (150.101.40.164) 4 msec 0 msec 4 msec
3 ae6.cr2.syd4.on.ii.net (150.101.41.124) 0 msec 4 msec 0 msec
4 * * *
5 * * *
Yea dude, a few of us are.
Especially kiwis on Vodafone.
Itās noticeable from Asia as well, a solid 200-250ms more latency. Iām usually around 135-145ms to Oceanic realms or the other way to US realms at about 140-150ms, however today itās 350-400ms to Oceanic realms and the same 140-150ms ot US realms.
Hi, been trying to figure out why this has been occuring the last few days, good to know this is already being looked at.
I also thought it might be worth noting that Iāve noticed this accross multiple battlenet/blizzard games. my ping is showing high on overwatch and destiny 2 also but no other games or web services are proving to have any issue.
Based in Wellington NZ on Vodafone.
WinMTR below;
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 115 | 115 | 0 | 0 | 3 | 0 |
| 121-74-127-254.telstraclear. net - 0 | 115 | 115 | 9 | 14 | 35 | 26 |
| 10.200.12.21 - 0 | 115 | 115 | 9 | 13 | 16 | 15 |
| 38.88.197.206 - 0 | 115 | 115 | 142 | 146 | 170 | 144 |
|te0-1-0-1.ccr41.lax04.atlas.cogentco. com - 0 | 115 | 115 | 142 | 147 | 151 | 145 |
| ntt.lax04.atlas.cogentco. com - 0 | 115 | 115 | 155 | 159 | 165 | 161 |
| ae-2.r23.lsanca07.us.bb.gin.ntt. net - 6 | 98 | 93 | 154 | 158 | 170 | 156 |
| ae-12.r31.tokyjp05.jp.bb.gin.ntt. net - 0 | 115 | 115 | 213 | 218 | 232 | 216 |
| ae-3.r01.tokyjp08.jp.bb.gin.ntt. net - 0 | 115 | 115 | 211 | 215 | 222 | 212 |
| ae-2.a00.tokyjp03.jp.bb.gin.ntt. net - 0 | 115 | 115 | 211 | 215 | 230 | 215 |
| 61.213.179.114 - 0 | 115 | 115 | 258 | 271 | 345 | 266 |
| 137.221.81.35 - 0 | 115 | 115 | 209 | 219 | 308 | 255 |
| ge-0-0-8-br02-eqsy4.as57976. net - 0 | 115 | 115 | 209 | 217 | 326 | 217 |
| et-0-0-1-pe01-eqsy4.as57976. net - 0 | 115 | 115 | 209 | 216 | 271 | 213 |
| 137.221.66.145 - 0 | 115 | 115 | 210 | 214 | 222 | 214 |
| 103.4.115.248 - 0 | 115 | 115 | 209 | 213 | 219 | 212 |
Weāve gotten more reports of this and opened the investigation back up. Thanks for following up, everyone.