Cant connect to battlenet from Mexico with Totalplay ISP
2 Likes
Same here. I guess blizzard blocked a bunch of IP ranges from where the bots were attacking yesterday. Hopefully we will hear something and get back to normal soon. What makes me angry is the lack of aknowledgement or response from blizzard.
Oh; and dont even bother talking to totalplay, they told me to “restart your modem”
This is something that we’re tracking at the moment. If you’re seeing this issue while on Totalplay, please run and post a WinMTR test. When posting the results, please format it by encasing it in a set of ~~~ like so:
~~~
WinMTR Contents
~~~
I am having the same issue but I cannot login into the forum or run the test, this started since yesterday’s night.
Edit. I managed to send my results to my phone and post it, please give us some insight, my subscription was just charged yesterday, this is a weekend and no way to play
Hi, this is the WinMTR info i got while on Totalplay. I hope this can help you to solve the problems fasters, let me know if i can do something else to help.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.100.1 - 0 | 62 | 62 | 2 | 11 | 128 | 6 |
| 10.146.0.1 - 0 | 62 | 62 | 4 | 16 | 69 | 10 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| 10.180.59.75 - 0 | 62 | 62 | 5 | 16 | 132 | 10 |
| 10.180.200.172 - 2 | 59 | 58 | 14 | 24 | 78 | 17 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 13 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.100.1 - 0 | 33 | 33 | 2 | 6 | 32 | 8 |
| 10.146.0.1 - 0 | 33 | 33 | 5 | 18 | 74 | 8 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| 10.180.59.75 - 0 | 33 | 33 | 7 | 16 | 68 | 9 |
| 10.180.200.172 - 0 | 33 | 33 | 14 | 21 | 82 | 15 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 7 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
Ping Type: ICMP
Packet Size: default
TTL: default
Timeout: 3000
Count: 3
Interval: 1000
General Timeout: not used
PING battle.net (137.221.106.104)
connection timeout 1
connection timeout 2
connection timeout 3
--- ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 12052ms
traceroute to battle.net (137.221.106.104), 30 hops max
Hop 1:
From 192.168.100.1, 2 ms
Hop 2:
From 10.110.128.3, 5 ms
Hop 3:
*
Hop 4:
From 10.180.59.71, 5 ms
Hop 5:
From 10.180.200.172, 12 ms
Hop 6:
*
Hop 7:
*
Hop 8:
*
Hop 9:
*
Hop 10:
*
Hop 11:
*
Hop 12:
*
Hop 13:
*
Hop 14:
*
Hop 15:
*
Hop 16:
*
Hop 17:
*
Hop 18:
*
Hop 19:
*
Hop 20:
*
Hop 21:
*
Hop 22:
*
Hop 23:
*
Hop 24:
*
Hop 25:
*
Hop 26:
*
Hop 27:
*
Hop 28:
*
Hop 29:
*
Hop 30:
*
Traceroute complete: 30 hops, time: 13402 ms
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.100.1 - 0 | 213 | 213 | 0 | 0 | 3 | 0 |
| 10.148.192.2 - 0 | 213 | 213 | 2 | 6 | 95 | 3 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| 10.180.59.75 - 0 | 213 | 213 | 3 | 5 | 35 | 6 |
| 10.180.200.172 - 0 | 213 | 213 | 10 | 11 | 25 | 11 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 43 | 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 |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.100.1 - 0 | 18 | 18 | 0 | 0 | 1 | 1 |
| 10.148.192.2 - 0 | 18 | 18 | 3 | 7 | 33 | 3 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| 10.180.59.75 - 0 | 18 | 18 | 4 | 5 | 15 | 15 |
| 10.180.200.172 - 0 | 18 | 18 | 11 | 12 | 16 | 11 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Any ETA on a fix? This was obviously a consequence of yesterday’s DDoS. Please don’t leave us in the dark. We don’t know if this could take hours or days to get fixed.
1 Like
i have the same problem, called totalplay support and got the same answer
You can use a VPN or Mobile Hotspot to play. Obviously this isnt a solution and you might end up with terrible latency or a locked account but if you have to this is your go-to option right now. I would also like an update from a blue poster. Hopefully this will get fixed today.
Same here, whats happen
I cannot log in or access the support sites, the forum is the only place that works for me. It cannot be that the only day off can not enjoy the game. I pay for it. If I can’t access the support where I find help?
My ISP is Total Play in Mexico.
Same here, on Totalplay too
Will there be compensation for this? Payment for the game that they do not give it to me, it is not free, two days have passed and it was easy for them to block malicious traffic and in the same way affect the legal traffic of consumers.
I contacted Totalplay and they stated that this is an issue with Blizzard and not them, they also stated that they have not made any changes to cause that issue.
1 Like
Finally a real answer from Totalplay. Good to know its not them. Lets hope this gets fixed today.
I’m in Canada and cannot log into Thalnos Server = keeps disconnecting. I feel ya brother from another mother.
1 Like
I use Total Play in Tijuana, Mexico. I can’t access even the support website from Blizzard other than using my celullar data. I have not seen any good progress on fixing this nor a note about acknowledging the problem.
I also called Total Play to see if they can move my service to a different IP range but that can not. It seems like I am going to have to wait for news in the coming hours/days and a reimbursement maybe?
3 Likes