Hi,
Since earlier this week all the Oceanic servers have jumped from 30ms to over 180ms. This holds true for all the servers hosted on the 103.4.115.x range. I've tested all of them on the link and the results are consistent with in game reports.
https://wow.gamepedia.com/Americas_region_realm_list_by_datacenter
Please can you inform us as to why this has happened? Traceroute results below showing last 4 hops. (latency is one hop away from destination)
12 30 ms 30 ms 28 ms 210.176.152.33
13 28 ms 27 ms 28 ms 137.221.85.33
14 182 ms 182 ms 182 ms 137.221.85.69
15 183 ms 182 ms 183 ms 103.4.115.248
Can confirm. Am experiencing the exact same in both WoW and HotS.
My Traceroute results to Oceanic WoW servers (103.4.115.248):
11 17 ms 16 ms 17 ms unknown.telstraglobal.net [210.176.152.33]
12 17 ms 17 ms 17 ms et-0-0-48-br01-eqsy4.as57976.net [137.221.85.33]
13 170 ms 169 ms 171 ms et-0-0-0-pe01-eqsy4.as57976.net [137.221.85.67]
14 171 ms 170 ms 170 ms 137.221.66.145
15 171 ms 171 ms 171 ms 103.4.115.248
Latency sits at a perfect 171ms in both games, up from around 20.
My Traceroute results to Oceanic WoW servers (103.4.115.248):
11 17 ms 16 ms 17 ms unknown.telstraglobal.net [210.176.152.33]
12 17 ms 17 ms 17 ms et-0-0-48-br01-eqsy4.as57976.net [137.221.85.33]
13 170 ms 169 ms 171 ms et-0-0-0-pe01-eqsy4.as57976.net [137.221.85.67]
14 171 ms 170 ms 170 ms 137.221.66.145
15 171 ms 171 ms 171 ms 103.4.115.248
Latency sits at a perfect 171ms in both games, up from around 20.
Can confirm too. Please investigate
More substantial thread here with people posting WinMTR's etc. to resolve the issue if you wanted to post your results!
https://us.battle.net/forums/en/wow/topic/20769588414
https://us.battle.net/forums/en/wow/topic/20769588414
Really hope this is fixed soon. As someone in Asia on an OCE server this is unplayable for pvp - 140ms up to 300ms. Been unplayable for days.
The last hop before the latency jump Looks like some sort of Blizzard peer link in the NL (Netherlands) , odd.
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf
% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.
% Information related to '137.221.64.0 - 137.221.95.255'
% Abuse contact for '137.221.64.0 - 137.221.95.255' is 'peering@blizzard.com'
inetnum: 137.221.64.0 - 137.221.95.255
netname: BLIZZARD
country: NL
admin-c: BP5978-RIPE
tech-c: BP5978-RIPE
status: ASSIGNED PA
mnt-by: MNT-BLIZZARD
created: 2018-08-27T19:57:32Z
last-modified: 2018-08-27T19:57:32Z
source: RIPE
person: Blizzard Peering
address: 1 Blizzard Way
phone: +1-949-955-1380
nic-hdl: BP5978-RIPE
mnt-by: MNT-BLIZZARD
created: 2016-09-07T17:19:11Z
last-modified: 2018-08-24T18:24:09Z
source: RIPE # Filtered
% This query was served by the RIPE Database Query Service version 1.92.6 (ANGUS)
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf
% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.
% Information related to '137.221.64.0 - 137.221.95.255'
% Abuse contact for '137.221.64.0 - 137.221.95.255' is 'peering@blizzard.com'
inetnum: 137.221.64.0 - 137.221.95.255
netname: BLIZZARD
country: NL
admin-c: BP5978-RIPE
tech-c: BP5978-RIPE
status: ASSIGNED PA
mnt-by: MNT-BLIZZARD
created: 2018-08-27T19:57:32Z
last-modified: 2018-08-27T19:57:32Z
source: RIPE
person: Blizzard Peering
address: 1 Blizzard Way
phone: +1-949-955-1380
nic-hdl: BP5978-RIPE
mnt-by: MNT-BLIZZARD
created: 2016-09-07T17:19:11Z
last-modified: 2018-08-24T18:24:09Z
source: RIPE # Filtered
% This query was served by the RIPE Database Query Service version 1.92.6 (ANGUS)
I wonder if they failed the region servers over to the another DC to try and resolve the other in game lag (which appeared to be server lag). Either way, hope the routing issue or DC failover is resolved. The silence when this is a monthly paid for service is disturbing.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192-168-1-1.tpgi.com.au - 0 | 255 | 255 | 0 | 0 | 1 | 0 |
| 10-20-25-155.tpgi.com.au - 0 | 255 | 255 | 5 | 6 | 7 | 6 |
| adl-adc-lon-wgw1-be-100.tpgi.com.au - 0 | 255 | 255 | 6 | 6 | 10 | 7 |
| 203-219-199-154.tpgi.com.au - 0 | 255 | 255 | 6 | 6 | 11 | 6 |
|Bundle-Ether12.way-edge902.adelaide.telstra.net - 0 | 255 | 255 | 6 | 6 | 14 | 7 |
|bundle-ether10.way-core10.adelaide.telstra.net - 0 | 254 | 254 | 6 | 7 | 10 | 7 |
|bundle-ether16.exi-core10.melbourne.telstra.net - 0 | 254 | 254 | 17 | 18 | 27 | 19 |
|bundle-ether12.chw-core10.sydney.telstra.net - 0 | 254 | 254 | 27 | 28 | 30 | 29 |
|bundle-ether1.oxf-gw11.sydney.telstra.net - 0 | 254 | 254 | 27 | 28 | 31 | 29 |
|bundle-ether2.oxf-gw10.sydney.telstra.net - 0 | 254 | 254 | 30 | 31 | 35 | 30 |
|bundle-ether1.sydo-core04.sydney.reach.com - 0 | 254 | 254 | 30 | 31 | 33 | 32 |
| i-0-0-0-15.sydo10.telstraglobal.net - 0 | 254 | 254 | 29 | 30 | 67 | 30 |
| unknown.telstraglobal.net - 0 | 255 | 255 | 30 | 31 | 53 | 31 |
| 137.221.85.35 - 0 | 254 | 254 | 28 | 30 | 79 | 29 |
| et-0-0-1-pe01-eqsy4.as57976.net - 0 | 254 | 254 | 184 | 186 | 247 | 184 |
| 137.221.66.145 - 0 | 254 | 254 | 184 | 184 | 186 | 184 |
| 103.4.115.248 - 0 | 254 | 254 | 184 | 184 | 186 | 184 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
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 6 ms 5 ms 6 ms 10-20-25-155.tpgi.com.au [10.20.25.155]
3 7 ms 6 ms 6 ms adl-adc-lon-wgw1-be-100.tpgi.com.au [203.219.199.3]
4 7 ms 7 ms 7 ms 203-219-199-154.tpgi.com.au [203.219.199.154]
5 7 ms 7 ms 7 ms Bundle-Ether12.way-edge902.adelaide.telstra.net [139.130.121.165]
6 8 ms 8 ms 8 ms bundle-ether10.way-core10.adelaide.telstra.net [203.50.11.152]
7 17 ms 18 ms 19 ms bundle-ether16.exi-core10.melbourne.telstra.net [203.50.6.231]
8 29 ms 28 ms 28 ms bundle-ether12.chw-core10.sydney.telstra.net [203.50.11.124]
9 29 ms 29 ms 28 ms bundle-ether1.oxf-gw11.sydney.telstra.net [203.50.6.93]
10 32 ms 31 ms 31 ms bundle-ether2.oxf-gw10.sydney.telstra.net [203.50.6.94]
11 32 ms 33 ms 32 ms bundle-ether1.sydo-core04.sydney.reach.com [203.50.13.94]
12 32 ms 30 ms 32 ms i-0-0-0-15.sydo10.telstraglobal.net [202.84.222.206]
13 67 ms 32 ms 31 ms unknown.telstraglobal.net [210.176.152.33]
14 29 ms 29 ms 29 ms 137.221.85.35
15 185 ms 185 ms 185 ms et-0-0-1-pe01-eqsy4.as57976.net [137.221.85.71]
16 184 ms 184 ms 184 ms 137.221.66.145
17 185 ms 185 ms 184 ms 103.4.115.248
Trace complete.
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192-168-1-1.tpgi.com.au - 0 | 255 | 255 | 0 | 0 | 1 | 0 |
| 10-20-25-155.tpgi.com.au - 0 | 255 | 255 | 5 | 6 | 7 | 6 |
| adl-adc-lon-wgw1-be-100.tpgi.com.au - 0 | 255 | 255 | 6 | 6 | 10 | 7 |
| 203-219-199-154.tpgi.com.au - 0 | 255 | 255 | 6 | 6 | 11 | 6 |
|Bundle-Ether12.way-edge902.adelaide.telstra.net - 0 | 255 | 255 | 6 | 6 | 14 | 7 |
|bundle-ether10.way-core10.adelaide.telstra.net - 0 | 254 | 254 | 6 | 7 | 10 | 7 |
|bundle-ether16.exi-core10.melbourne.telstra.net - 0 | 254 | 254 | 17 | 18 | 27 | 19 |
|bundle-ether12.chw-core10.sydney.telstra.net - 0 | 254 | 254 | 27 | 28 | 30 | 29 |
|bundle-ether1.oxf-gw11.sydney.telstra.net - 0 | 254 | 254 | 27 | 28 | 31 | 29 |
|bundle-ether2.oxf-gw10.sydney.telstra.net - 0 | 254 | 254 | 30 | 31 | 35 | 30 |
|bundle-ether1.sydo-core04.sydney.reach.com - 0 | 254 | 254 | 30 | 31 | 33 | 32 |
| i-0-0-0-15.sydo10.telstraglobal.net - 0 | 254 | 254 | 29 | 30 | 67 | 30 |
| unknown.telstraglobal.net - 0 | 255 | 255 | 30 | 31 | 53 | 31 |
| 137.221.85.35 - 0 | 254 | 254 | 28 | 30 | 79 | 29 |
| et-0-0-1-pe01-eqsy4.as57976.net - 0 | 254 | 254 | 184 | 186 | 247 | 184 |
| 137.221.66.145 - 0 | 254 | 254 | 184 | 184 | 186 | 184 |
| 103.4.115.248 - 0 | 254 | 254 | 184 | 184 | 186 | 184 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
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 6 ms 5 ms 6 ms 10-20-25-155.tpgi.com.au [10.20.25.155]
3 7 ms 6 ms 6 ms adl-adc-lon-wgw1-be-100.tpgi.com.au [203.219.199.3]
4 7 ms 7 ms 7 ms 203-219-199-154.tpgi.com.au [203.219.199.154]
5 7 ms 7 ms 7 ms Bundle-Ether12.way-edge902.adelaide.telstra.net [139.130.121.165]
6 8 ms 8 ms 8 ms bundle-ether10.way-core10.adelaide.telstra.net [203.50.11.152]
7 17 ms 18 ms 19 ms bundle-ether16.exi-core10.melbourne.telstra.net [203.50.6.231]
8 29 ms 28 ms 28 ms bundle-ether12.chw-core10.sydney.telstra.net [203.50.11.124]
9 29 ms 29 ms 28 ms bundle-ether1.oxf-gw11.sydney.telstra.net [203.50.6.93]
10 32 ms 31 ms 31 ms bundle-ether2.oxf-gw10.sydney.telstra.net [203.50.6.94]
11 32 ms 33 ms 32 ms bundle-ether1.sydo-core04.sydney.reach.com [203.50.13.94]
12 32 ms 30 ms 32 ms i-0-0-0-15.sydo10.telstraglobal.net [202.84.222.206]
13 67 ms 32 ms 31 ms unknown.telstraglobal.net [210.176.152.33]
14 29 ms 29 ms 29 ms 137.221.85.35
15 185 ms 185 ms 185 ms et-0-0-1-pe01-eqsy4.as57976.net [137.221.85.71]
16 184 ms 184 ms 184 ms 137.221.66.145
17 185 ms 185 ms 184 ms 103.4.115.248
Trace complete.
Could also possibly related to all the TPG customers, folks on NBN dont have the same issue
10/31/2018 02:15 AMPosted by TrygorCould also possibly related to all the TPG customers, folks on NBN dont have the same issue
I am on NBN and TPG but there are guildies with same issue. Who are also on NBN and not with TPG
Howdy!
This appears to be a routing issue to the server. We are currently looking into this to see if we can help reach out and resolve it. We have seen reports a VPN can help reroute and resolve this issue in the mean time.
Thank you!
This appears to be a routing issue to the server. We are currently looking into this to see if we can help reach out and resolve it. We have seen reports a VPN can help reroute and resolve this issue in the mean time.
Thank you!
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 02:15 AMPosted by TrygorCould also possibly related to all the TPG customers, folks on NBN dont have the same issue
In on Optus 4G and experience the same issue so not just TPG
10/30/2018 11:40 PMPosted by TrygorThe last hop before the latency jump Looks like some sort of Blizzard peer link in the NL (Netherlands) , odd.
Just off topic here - If your talking about the nodes at -
13 28 ms 27 ms 28 ms 137.221.85.33
14 182 ms 182 ms 182 ms 137.221.85.69These are not actually in the Netherlands. Because Blizzard have their own ASN they have over 55,000 IP addresses registered to them. As I doubt any single ISPs will have that many on hand they need to use multiple ISPs to register them all.... some are in Europe.
The true test is to grab a looking glass test on a server that's based in Sydney then using that run either a traceroute or ping to that IP address and compare it to one to uva.nl (which actually is based in the Netherlands). If a node were in the Netherlands then a hop from Sydney -> Netherlands is around ~238 ms on the looking glass tests i've done. For the nodes above I get <2ms indicating they are in Sydney.
Here's a list of Australian looking glass utilities - https://www.ausnog.net/tools/lg
Sorry for steering this thread a little off course !
10/31/2018 04:04 PMPosted by TrinitasIn on Optus 4G and experience the same issue so not just TPG
Interesting. Can you post your MTR and pathping data ?
Posted in the other thread but posting here so it gets seen. I am on optus 4g as well and I am still having issues after the fix. Here is my WinMTR
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 794 | 794 | 0 | 1 | 16 | 1 |
| 10.88.0.254 - 0 | 794 | 794 | 16 | 161 | 560 | 232 |
| 10.194.29.145 - 0 | 794 | 794 | 20 | 50 | 371 | 50 |
| No response from host - 100 | 159 | 0 | 0 | 0 | 0 | 0 |
| 210.49.118.34 - 0 | 794 | 794 | 17 | 50 | 372 | 45 |
| 10.194.122.2 - 0 | 794 | 794 | 17 | 49 | 372 | 44 |
| 10.194.122.9 - 0 | 794 | 794 | 20 | 49 | 372 | 48 |
| 10.194.122.218 - 0 | 794 | 794 | 23 | 49 | 371 | 43 |
| 10.194.122.213 - 0 | 794 | 794 | 16 | 49 | 373 | 52 |
| No response from host - 100 | 159 | 0 | 0 | 0 | 0 | 0 |
| hu0-6-0-0.22rrpr01.optus.net.au - 0 | 794 | 794 | 17 | 50 | 372 | 47 |
|Bundle-Ether38.chw-edge903.sydney.telstra.net - 0 | 794 | 794 | 23 | 50 | 372 | 43 |
|bundle-ether17.chw-core10.sydney.telstra.net - 0 | 794 | 794 | 21 | 51 | 372 | 49 |
|bundle-ether1.oxf-gw11.sydney.telstra.net - 0 | 794 | 794 | 24 | 52 | 370 | 47 |
|bundle-ether2.oxf-gw10.sydney.telstra.net - 0 | 794 | 794 | 22 | 52 | 372 | 47 |
|bundle-ether1.sydo-core04.sydney.reach.com - 0 | 794 | 794 | 24 | 52 | 373 | 47 |
| i-0-0-0-15.sydo10.telstraglobal.net - 0 | 794 | 794 | 17 | 50 | 372 | 39 |
| unknown.telstraglobal.net - 0 | 794 | 794 | 25 | 51 | 373 | 47 |
| 137.221.85.35 - 0 | 794 | 794 | 19 | 54 | 374 | 42 |
| et-0-0-0-pe02-eqsy4.as57976.net - 0 | 794 | 794 | 156 | 187 | 553 | 177 |
| 103.4.115.248 - 0 | 794 | 794 | 161 | 189 | 564 | 185 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| homerouter.cpe - 0 | 335 | 335 | 0 | 0 | 4 | 0 |
| 10.251.255.254 - 0 | 335 | 335 | 18 | 136 | 241 | 161 |
| 10.194.36.17 - 0 | 335 | 335 | 14 | 23 | 86 | 19 |
| 10.194.125.2 - 0 | 335 | 335 | 11 | 22 | 81 | 19 |
| 10.194.125.13 - 0 | 335 | 335 | 12 | 23 | 87 | 24 |
| No response from host - 100 | 67 | 0 | 0 | 0 | 0 | 0 |
| 210.49.110.218 - 0 | 335 | 335 | 12 | 23 | 86 | 24 |
| No response from host - 100 | 67 | 0 | 0 | 0 | 0 | 0 |
| 10.194.125.209 - 0 | 335 | 335 | 16 | 25 | 49 | 23 |
| No response from host - 100 | 67 | 0 | 0 | 0 | 0 | 0 |
| te0-0-1-0.o6lxpr01.optus.net.au - 0 | 335 | 335 | 13 | 23 | 83 | 19 |
|Bundle-Ether14.wel-edge902.perth.telstra.net - 0 | 335 | 335 | 15 | 23 | 83 | 22 |
|bundle-ether7.wel-core3.perth.telstra.net - 0 | 335 | 335 | 14 | 25 | 91 | 28 |
|bundle-ether3.fli-core10.adelaide.telstra.net - 0 | 335 | 335 | 41 | 55 | 80 | 53 |
|bundle-ether16.win-core10.melbourne.telstra.net - 0 | 335 | 335 | 53 | 61 | 78 | 63 |
|bundle-ether12.ken-core10.sydney.telstra.net - 0 | 335 | 335 | 64 | 73 | 88 | 65 |
|bundle-ether1.oxf-gw10.sydney.telstra.net - 0 | 335 | 335 | 61 | 74 | 88 | 75 |
|bundle-ether1.sydo-core04.sydney.reach.com - 0 | 335 | 335 | 59 | 74 | 92 | 75 |
| i-0-0-0-4.sydo10.bi.telstraglobal.net - 0 | 335 | 335 | 62 | 74 | 134 | 96 |
| unknown.telstraglobal.net - 0 | 335 | 335 | 65 | 72 | 89 | 70 |
| 137.221.85.35 - 0 | 335 | 335 | 61 | 78 | 213 | 71 |
| et-0-0-1-pe01-eqsy4.as57976.net - 0 | 335 | 335 | 210 | 224 | 284 | 216 |
| 137.221.66.145 - 0 | 335 | 335 | 205 | 215 | 279 | 222 |
| 103.4.115.248 - 0 | 335 | 335 | 210 | 217 | 233 | 222 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
A turtle has made it to the water
Been out all day only just catching up on news now; is this resolving the regional issue that's been going on for three months or was this a separate issue?
Seems like the servers are still experiencing this issue; I get regular lag spikes.