I have another friend with similar issue from Singapore as well, both of us are on the same ISP called M1
welll… that makes 3.
basically from what i understand from our 3 main ISPs here in Singapore.
Singtel and Starhubs = ingame latency as high as 2k plus becus of some server routing…
M1 = unable to patch now… ok nice…
4 here. Singapore using M1.
5 Here, Playing from Singapore too
Chinese ISP address is what I saw Asphyxiate. Well it looks like we are at the root of the issue. Something is up with the M1 ISP. What it could be I’m not sure.
Any chance of testing a VPN?
ah m1 is a ISP in singapore. ahahha but yea i know that a Chinese company is supplying them with the modems and routers.
I suspect the case is that the ISP is blocking the patch from downloading (becus ISP themsevles may have their own firewall)… i can try to call the customer service centre to look into it… but i may need the ip address of patch server to inform them to allow the patch download…
Edit:
As for VPN i don’t mind trying it out if u can recommend one.
I don’t know what you might have available there in the way of VPNs. I was looking at that M1 ISP. They supply routers that have Killer network prioritization software. That can be problematic with Wow.
whats a Killer network Prioritization software? ok nvm i just googled it… anyway to get around it? like a manual download patch or something.
Ok… solved. the issues was the ISP. i used hotspot VPN to get around the whole thing and it started to download. thankfully the patch is a 35mb patch. hence the download was not long.
oh well… seems like an M1 issue then… cause im also on M1
Good to see Asphyxiate. You may want to detail how you did that for the other folk on the thread. No doubt there will be more looking at this as well.
basically it is just downloading hotspot vpv, turning it on (don’t need to pay any cash or subsciption to turn it on) then launch battle.net launcher and download the patch.
I was able to fix it using nordvpn as well as mudfish, so any vpn could work just an ISP issue
M1 user as well - looks like there’s definitely something fishy about the ISP connectivity. Am switching to TPG to attempt to download the patch.
… and done.
Hey all! Thank you for your reports so far. We have been seeing reports of issues with M1 ISP with different Blizzard Application errors. I’ve updated the title of this thread to reflect the issue a bit better and help gather more information for M1 users.
For each of you, could we gather a WinMTR test? Use the Host/IP: 37.244.26.18
For those who have found hotspot works to download the patch, does the game work fine and its just the patch service?
If you are not on the M1 Singapore ISP, please create a separate thread.
Hi,
I will post my MTR later when i get home. (Currently at work reading this).
The game works just fine. The issue is only the patch services it seems. Something preventing the file from downloading.
About M1 ISPs:
I suspect it is the security systems of the ISP have imposed on themselves. Normally these security systems are related to:
- Blocking of Adult content websites
- Blocking of Pirate websites
- Blocking of unknown files that maybe flagged as harmful viruses.
- Etc.
Hence i think their system may have flagged the patch file or patch server as a possible threat, hence they blocked it.
Game works fine just the patch service for M1. Here is my WinMTR test to 37.244.26.18
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
- 0 | 265 | 265 | 0 | 0 | 1 | 0 |
175.156.192.1 - 0 | 265 | 265 | 2 | 17 | 73 | 2 |
254.246.65.202. - 0 | 265 | 265 | 1 | 2 | 12 | 2 |
253.246.65.202. - 0 | 265 | 265 | 1 | 3 | 41 | 2 |
9.246.65.202. - 0 | 265 | 265 | 2 | 3 | 9 | 3 |
37.246.65.202. - 0 | 265 | 265 | 2 | 3 | 7 | 2 |
134.246.65.202. - 0 | 265 | 265 | 3 | 4 | 47 | 4 |
- 0 | 265 | 265 | 3 | 4 | 31 | 4 |
- 0 | 265 | 265 | 3 | 5 | 44 | 4 |
- 0 | 265 | 265 | 71 | 74 | 110 | 72 |
- 0 | 265 | 265 | 71 | 72 | 83 | 72 |
- 0 | 265 | 265 | 69 | 71 | 103 | 71 |
- 0 | 265 | 265 | 71 | 73 | 91 | 73 |
- 1 | 258 | 256 | 72 | 73 | 84 | 73 |
- 0 | 265 | 265 | 72 | 75 | 104 | 72 |
61.213.179.114 - 0 | 265 | 265 | 72 | 74 | 105 | 73 |
- 0 | 265 | 265 | 227 | 229 | 293 | 227 |
- 3 | 237 | 232 | 0 | 256 | 4452 | 184 |
- 0 | 265 | 265 | 227 | 228 | 229 | 228 |
No response from host - 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 53 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 53 | 0 | 0 | 0 | 0 | 0 |
________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| - 0 | 94 | 94 | 0 | 0 | 0 | 0 |
| 1.0.156.175 - 0 | 94 | 94 | 1 | 4 | 24 | 3 |
| 250.246.65.202.- 0 | 94 | 94 | 1 | 1 | 6 | 1 |
| 249.246.65.202.- 0 | 94 | 94 | 1 | 1 | 23 | 2 |
| 138.246.65.202.- 0 | 94 | 94 | 2 | 3 | 22 | 3 |
|ix-ae-56-0. - 0 | 94 | 94 | 2 | 3 | 41 | 3 |
|if-ae-7-2 - 0 | 94 | 94 | 1 | 2 | 24 | 3 |
| ae-9. - 0 | 94 | 94 | 67 | 75 | 109 | 82 |
| ae-5 - 0 | 94 | 94 | 68 | 80 | 101 | 76 |
| ae-2t - 0 | 94 | 94 | 68 | 80 | 101 | 77 |
| ae-17 - 0 | 94 | 94 | 70 | 82 | 108 | 79 |
| ae-3. - 0 | 94 | 94 | 71 | 83 | 105 | 78 |
| ae-1. - 0 | 94 | 94 | 71 | 84 | 106 | 77 |
| 61.213.179.114 - 0 | 94 | 94 | 71 | 77 | 102 | 80 |
| et-0-0-48-br01-eqty2. - 0 | 94 | 94 | 227 | 231 | 316 | 254 |
| xe-0-0-0-1 - 6 | 72 | 68 | 171 | 357 | 3310 | 172 |
| be1- - 0 | 94 | 94 | 227 | 228 | 229 | 228 |
| No response from host - 100 | 18 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 18 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 18 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 18 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 18 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 18 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 18 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 18 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 18 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 18 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 18 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 18 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 18 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
that section with the 3k ping looks suspicious
Thank you for the connection tests and following up! I’m glad to hear the in-game the connection or latency is doing fine. We’re still gathering information for those running into issues with the patch server. There is an underwater sea cable fault (APCN-2) that is impacting some SEA region connections that is likely related to the patch server issues. So far reports have shown VPN/Hotspot works around the issue.
@Äsphyxiàté, the 3k spike isn’t too much of a concern. This looks to just be some firewall or mitigation occurring as the next hop goes back to normal, but we’ll continue to monitor and check for new tests
yo… so today things just went south in-game. The in-game latency went off the charts.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % Sent Recv Best Avrg Wrst Last router - 0 78 78 0 0 1 0 1.0.156.175. - 0 78 78 1 15 166 1 182.246.65.202. - 0 78 78 1 1 2 1 181.246.65.202. - 0 78 78 1 1 10 1 134.246.65.202g - 0 78 78 2 3 41 3 57976 - 0 78 78 2 3 14 2 et-0-0-48-br02 - 0 77 77 384 386 433 433 ge-0-0-4-br02- - 0 77 77 384 386 429 385 xe-0-0-1-1-br01- - 0 77 77 384 386 422 385 xe-0-0-0-0-br01- - 0 77 77 384 386 418 385 xe-0-0-8-br01- - 0 78 78 215 220 346 240 et-0-0-0-pe02- - 0 77 77 384 386 443 385 103.4.115.248 - 0 77 77 384 384 386 385 ________________________________________________ ______ ______ ______ ______ ______ ______ WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I’m seeing the same latency on this thread. Something is up with the backbone.
https://us.forums.blizzard.com/en/wow/t/high-ms-on-oceeanic-server-for-past-few-days/118788