Due to the failure of Blizzard’s technical support team to engage with me on the following issue; Very odd WinMTR/Tracert results connecting to Sydney Servers - #3 by Haadrak-1644, and due to the fact that I am unable to make support tickets which Blizzard’s technical ssupport team has also failed to engage with me over the past 5 days; Can't submit ticket - #5 by Haadrak-1644, I have been informed by Consumer Affairs Victoria that unless Blizzard’s technical support team chooses to engage with me I will be left with no choice but to pursure legal action against Blizzard-Activision for the refund of all Overwatch related costs for failure to provide the service promised, within the Victorian Civil and Administrative Tribunal.
I do not want to do this. However when I have made a series of reasonable requests that have gone unanswered for a week, I see this as the only remaining option. I would have also preferred to make this a private email but seeing as how you have no outward email addresses with which I can contact you on, or phone numbers, and seeing as how the ticketing system doesn’t work, this appears to be the only option.
2 Likes
Do it. This is a shambles atm. We need something. I’ll support you in this as best I can. I’m in Melbourne and playing Overwatch recently is a disgrace.
You think they will feel threatened by your bluff? You are nothing to them, they wont even bat an eye.
Please note, I do believe there is ISP issues right now with Australia. Any current WinMTRs will be helpful (the one in your linked thread will be too old to be considered reliable).
Did the problem start after switching ISP or was it happening before the switch?
The problem began after switching ISPs. I have, however, spoken to the ISP already about potential problems that might be ISP related and they have said that they do not think there is an issue within their network. Now unless someone can think of something I have missed I am going to suggest that this might just be a problem on Blizzard’s end.
Also to the person saying that the WinMTR results are out of date. Firstly, this wouldn’t have been an issue if someone had responded a week ago, secondly here are some additional WinMTR results, taken from today. As you can see, they are, unchanged.
| Host - % |
Sent |
Recv |
Best |
Avrg |
Wrst |
Last |
| 192.168.1.1 - 0 |
239 |
239 |
0 |
0 |
3 |
0 |
| loop119171320.bng1.vdc03.mel.aussiebb .net - 0 |
239 |
239 |
8 |
11 |
22 |
10 |
| be2.core2.nextdc-s1.syd.aussiebb .net - 0 |
239 |
239 |
18 |
23 |
34 |
28 |
| hundredgige0-0-0-9.core1.vdc03.mel.aussiebb .net - 0 |
239 |
239 |
20 |
23 |
28 |
24 |
| hundredgige0-0-0-16.core1.vdc01.syd.aussiebb .net - 0 |
239 |
239 |
20 |
22 |
28 |
21 |
| be1.core2.vdc01.syd.aussiebb .net - 0 |
239 |
239 |
20 |
23 |
28 |
21 |
| 137.221.66.139 - 0 |
239 |
239 |
20 |
22 |
28 |
24 |
| 37.244.40.33 - 0 |
239 |
239 |
20 |
23 |
28 |
23 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
48 |
0 |
0 |
0 |
0 |
0 |
Hey again,
Thanks for following up with us on this.
If the problem started after switching ISPs then it’s likely related to how the signal is being sent through the internet (routed.)
The winMTR test itself does not have any packet loss or unusual latency spikes within the ISP network itself, so they might be right that it’s not a problem with their network. However the winMTR test does NOT display any peer networks. So we have no way to verify if the problem is happening after the data leaves their network and goes through their peers.
Basically every ISP uses what’s called a “routing table” to send their users data through the internet. Every ISP manages their own tables so most of them will be different depending on what service you’re using. Some ISPs only peer with specific networks as well depending on their business needs. This is why some routing issues will only affect certain ISPs and not others.
I have seen some users test routing issues by moving through different networks. Since it was already working on Telstra that should be enough evidence to provide the ISP to have them reach out to their Tier 2 or 3 agents, who can work with their network engineers on peering issues. However I have seen some players use what’s called a VPN to further verify.
A VPN will send all your data to their own servers before sending it back out to the internet. Due to this they have their own routing tables (different from the ones your ISP uses.) This should be an effective way to test for possible routing problems.
Even if that works, it’s not a fix, it’s just a test method. Though it does act as further evidence to push the ISP to reach out to their peers about this problem.
Keep in mind that VPN services are unsupported. It’s just something I commonly see fans do to test these types of issues. For setup of any VPN service please contact the VPN provider.