There is some serious issues with the ISP used for WoW servers down under… I am constantly having connection slow downs to the magnitude of over 3000ms (yes 3 THOUSAND)… Right now it crap, but playable as long as you dont do anything but questing… But M+ and Raiding is a no go… Which is my issue as I am end game focused player… Here are the Pathping and Tracert for WoW from my home here in the Philippines to WoW Oceanic Servers in Sydney Australia. Its been this way since BFA has been released and is getting worse… To the point I am close to canceling my account because there is no reason to pay for something I can not play… BTW this is at 12 in the afternoon… By 5pm it gets so bad I can not even log in…
So to recap, right now at around Lunch time I am getting 350ish ms or higher.
By 5pm its around 800ms to over 3000ms.
By 3am in the morning it is around 175ms…
C:\Users\Joe>pathping 103.4.115.248
Tracing route to 103.4.115.248 over a maximum of 30 hops
0 MidnightRider.local [192.168.1.2]
1 192.168.1.1
2 *************.pldt.net **** (my IP Ad removed)
3 122.2.175.174.static.pldt.net [122.2.175.174]
4 210.213.133.130.static.pldt.net [210.213.133.130]
5 210.213.128.29.static.pldt.net [210.213.128.29]
6 210.213.130.170.static.pldt.net [210.213.130.170]
7 i-0-4-0-15-peer.hkth12.pr.telstraglobal.net [134.159.128.117]
8 i-99.hkth-core02.telstraglobal.net [202.84.153.149]
9 * i-10352.sydo-core03.telstraglobal.net [202.84.138.42]
10 i-0-0-0-0.sydo10.bi.telstraglobal.net [202.84.222.186]
11 unknown.telstraglobal.net [210.176.152.33]
12 et-0-0-48-br01-eqsy4.as57976.net [137.221.85.33]
13 et-0-0-0-pe01-eqsy4.as57976.net [137.221.85.67]
14 137.221.66.145
15 103.4.115.248
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 MidnightRider.local [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% dsl.******.pldt.net ******
0/ 100 = 0% |
3 6ms 0/ 100 = 0% 0/ 100 = 0% 122.2.175.174.static.pldt.net [122.2.175.174]
0/ 100 = 0% |
4 31ms 0/ 100 = 0% 0/ 100 = 0% 210.213.133.130.static.pldt.net [210.213.133.130]
0/ 100 = 0% |
5 25ms 0/ 100 = 0% 0/ 100 = 0% 210.213.128.29.static.pldt.net [210.213.128.29]
0/ 100 = 0% |
6 27ms 0/ 100 = 0% 0/ 100 = 0% 210.213.130.170.static.pldt.net [210.213.130.170]
2/ 100 = 2% |
7 119ms 4/ 100 = 4% 2/ 100 = 2% i-0-4-0-15-peer.hkth12.pr.telstraglobal.net [134.159.128.117]
0/ 100 = 0% |
8 137ms 5/ 100 = 5% 3/ 100 = 3% i-99.hkth-core02.telstraglobal.net [202.84.153.149]
0/ 100 = 0% |
9 250ms 2/ 100 = 2% 0/ 100 = 0% i-10352.sydo-core03.telstraglobal.net [202.84.138.42]
0/ 100 = 0% |
10 249ms 3/ 100 = 3% 1/ 100 = 1% i-0-0-0-0.sydo10.bi.telstraglobal.net [202.84.222.186]
0/ 100 = 0% |
11 249ms 3/ 100 = 3% 1/ 100 = 1% unknown.telstraglobal.net [210.176.152.33]
0/ 100 = 0% |
12 258ms 3/ 100 = 3% 1/ 100 = 1% et-0-0-48-br01-eqsy4.as57976.net [137.221.85.33]
0/ 100 = 0% |
13 257ms 3/ 100 = 3% 1/ 100 = 1% et-0-0-0-pe01-eqsy4.as57976.net [137.221.85.67]
0/ 100 = 0% |
14 313ms 2/ 100 = 2% 0/ 100 = 0% 137.221.66.145
2/ 100 = 2% |
15 230ms 4/ 100 = 4% 0/ 100 = 0% 103.4.115.248
Trace complete.
C:\Users\Joe>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
2 26 ms 108 ms 9 ms dsl.*********.pldt.net *******
3 9 ms 8 ms 9 ms 122.2.175.174.static.pldt.net [122.2.175.174]
4 26 ms 25 ms 26 ms 210.213.133.130.static.pldt.net [210.213.133.130]
5 27 ms 27 ms 27 ms 210.213.128.29.static.pldt.net [210.213.128.29]
6 25 ms 78 ms 25 ms 210.213.130.170.static.pldt.net [210.213.130.170]
7 * * 116 ms i-0-4-0-15-peer.hkth12.pr.telstraglobal.net [134.159.128.117]
8 116 ms 117 ms 117 ms i-99.hkth-core02.telstraglobal.net [202.84.153.149]
9 229 ms 230 ms 230 ms i-10352.sydo-core03.telstraglobal.net [202.84.138.42]
10 229 ms 228 ms 228 ms i-0-0-0-0.sydo10.bi.telstraglobal.net [202.84.222.186]
11 229 ms 229 ms 229 ms unknown.telstraglobal.net [210.176.152.33]
12 228 ms 229 ms 237 ms et-0-0-48-br01-eqsy4.as57976.net [137.221.85.33]
13 232 ms 232 ms 233 ms et-0-0-0-pe01-eqsy4.as57976.net [137.221.85.67]
14 227 ms 227 ms 227 ms 137.221.66.145
15 231 ms 231 ms 231 ms 103.4.115.248
Trace complete.
It means there’s an issue with how your ISP is pathing your connection to Blizzard’s Oceanic servers. You’ll really want to take that up with them since Blizzard doesn’t control how you connect to them, your ISP does.
The connection is good when it leaves PLDT network to the main backbone and then soon as it hits Telstra in Australia it goes to complete garbage… PLDT can only do so much and have no control over how things are routed on Telstras network…
And Blizzard doesn’t control how connections come into them or their ISP for the servers. They don’t control the internet. Your ISP can change the current one through that backbone of Telestra is the issue. Blizzard cannot.
I think your possibly little disconnected from how things work IRL… While yes your correct Blizz has no direct control, the ISP (Telstra) in this case is responsible for providing a quality product (service and backbone connection in this case). If Blizz customers (like myself) are having issues connecting to Blizz’s product (WOW in this case) due to Telstra not providing a quality service that Blizz pays them for. Then Telstra is in fact responsible to Blizz and would be required under contract to fix any issues should they arise in a timely manner. Why you would think otherwise is a real mystery here…
So hense, we report connection issues to Blizz… Then Blizz reports connection issues to Telstra… That’s how it works IRL…
Kinderfeld . Backbone providers work both ways, so any ISP that uses them can contact them to report issues as well on behalf of customers. We always do our best to assist our community when a major routing issue occurs that impacts our services. We do this by collecting data then contacting the ISP directly. In some cases we can make adjustments on our end to assist as well. With that backbone provider, we have went above and beyond but some changes will need to be done on the ISP’s connecting to it.
Which is where we left it after most reports have gone down and the overall issues appear resolved. Now if we see a greater return of issues with this provider feel free to post WinMTRs and we can always take another look. For players left with issues still we do recommend to contact your ISP first and push the issue with them first.
STILL getting issues… As you can see the connection on Telstras end towards the server hosting WoW is having major packet loss. I have no idea why you would need to me also post a WinMTR…
Yes I am a 40yo with a degree in computer programming and network management. I understand how things work technically and in real life.
As far as contacting my ISP. There is only so much my ISP can do as it has no control of how data is handled on a network they do not own. Much less a completely different country. My ISP and I are in the Philippines and Telstra is in Australia. Also if I contacted Telstra about connection issues to your server I would be quickly told to p’off. To give you an idea, I was getting 140ms when I first started using this server about 6 months ago. Which compared to using the US servers I came from I was getting 220ms due to the long distance from Philippines to the USA. I can still connect to the USA servers even right now with just around 200ms lag. I am fine with that I learned to work around it. Only reason I moved was due to time zones. But right now connecting to Aman’Thul server in Australia (which is much much closer to me) I am seeing 350ms and higher. It even got up to 1000ms last night trying to raid. But it does get so bad at times I have seen a full 10,000ms. This is due to poor line conditions connecting to the Blizzard servers. Thus this is a Telstra & Blizzard issue. Not my ISP & Myself issue…
BTW, one last bit of information… I have a full fiber optic connection straight to my office from MY ISP. My speeds are 50Mbps Down and over 100Mbps Up… Pretty hard to get much better than this…
I am also still getting issues, and looking at the MTR, it seems like hops through Telstra’s network is causing problems, hope you can look into these issues, thanks.
Country: Singapore
Ping Before: 90-100ms
Ping After: 150-400ms
The spikes in ping are the most noticeable when in an instance or when sharding to another realm.
Yep same issues I get… Sometimes it is OK enough to play, but good 3 days a week or more its crap… Seems much worse though since BFA came out for some reason… I dont really understand why that would be though… I used to get 140ms all the time… Now I am happy to just see 170ms… But I do know the biggest reason for the higher then average pings is often due to pack loss. Hopefully Blizz can talk to Telstra or who ever their paying to host their servers in Aus about this…
You are not the only one who is experiencing those issue with the network overall.
I wrote this post today, have a look:
The MS I’m getting (here in Australia, sydney, frostmourne server) is way crazy…
By the way, I’m playing a random battleground and is the same history. Big MS. As soon as i left the instance and return back to bolarus, the ms gets fine again.
This is affecting my play ability, not sure if I should playing the game with this issues. I literally don’t know how to fix it or how can i manage it.
Both of your breakdowns start before they reach our peering network. Unfortunately that extremely limits what we can do here. While your ISP may not have direct control over these nodes, they can contact the backbone ISPs to report the issue. Ultimately, these are the people your ISP chooses to pay to move your connection to Australia where the servers are located. Because they have a business deal with these ISPs and they are out of our direct network, it’s on your ISP to report it.
Because we lack this business deal with the ISP, they don’t really care what we have to say about this. If we get a very large amount of evidence we can occasionally give them data to help identify the problem, but this is not successful without a rather large number of reports.
In this case the solution is going to remain contacting your ISP to see if they have another peer they can send you along. You can also download a VPN or use your phone as a Mobile Hotspot to see if you get a better connection this way. This may change the peers you’re using to cross the ocean which could work around the problem while your ISP investigates the problem.
More than a month now since I’ve had to pay for a VPN just to avoid getting over 300+ ms (I used to get 90-100 ms before this without a VPN). Posted so many MTR’s and there hasn’t been a fix to the routing to the Oceanic server from South East Asia and East Asia. This is what happens when you drop your server in a third world country with abysmal network routing to every other country around it.
At this current time, I’m getting better latency to the US. (Which is on the other side of the world than to Australia)
I would like to point out that many in the Oceanic region may not live in Australia and the ISPs in our countries (Like Philippines currently for me) will not contact anyone… So it falls on Blizzard to do so… Thus it falls on to you… Please quit trying to pass the buck per se. The last thing Blizzard needs is more bad controversy… So please just have your technical staff make a friendly phone call instead of just treating your customers like their are nothing.
I absolutely loathe replies like this. “Contact your ISP, its their problem”. Literally almost EVERY country apart from Australia is having massive latency issues for MORE THAN 1 MONTH NOW. Are you telling me you want EVERYONE outside of Australia to contact each ISP in EACH COUNTRY? What kind of customer support is this???
Its absolutely true what they say, Blizzard is turning into EA.
The SMW3 and the ASC both are damaged and under repairs and thus the high latency. Mostly everyone connecting from Asia to oceanic servers are getting high latency. When the default SMW3 crapped out the ASC was commissioned earlier to handle the traffic but that also went into the gutters.
Good luck with that. I had PLDT for years and they don’t lift a finger to help with routing. MAIN reason why internet is worse here in Philippines is due to PLDT’s practice of not sharing with other ISP’s or using the default backbone here in Philippines, they route their traffic to HK which slows internet down for everyone.
SOURCE:
PLDT acts as the country’s own backbone, able to control all the flow of internet traffic from Philippines to the outside. ISPs are also required to pay PLDT for using its ‘fake’ backbone instead of relying to real backbone service providers like PACNET to properly handle the data exchange for this country."
[Edited by Blizzard] This thread has been inactive for some time. Please be mindful of resurrecting older threads. A new or more recent thread can be created to continue the discussion. Locking this thread.