Saludos.
Disculpa, tuviste alguna respuesta por parte de soporte Técnico, te dieron solución a tu problema?
(estoy en la misma situación, tube que desinstalar las apps y ahora no puedo reinstalarlas…)
1 Like
I am getting the Same issue, I cannot connect to battlenet. Trying to log into WOW results in the same error as well.
1 Like
same, but looks like big update for cod, so maybe that
I’ve tried everything, still getting the same error. Been unable to log in at all. I understand that there is now the usual Tuesday maintenance but that shouldn’t have been the case last night and battle net shouldn’t be affected.
Strangely, I can log into battle net on the EU, however I am still unable to log into warcraft
I’ve gone through all the troubleshooting suggestions from the forums and the response i got for my help ticket - the issue definitely isn’t on my end, or there wouldnt be this many people encountering the same problem! This is just insane to me.
We’ve been seeing some issues described here, and been gathering some information on another thread with the BLZBNTBGS000003F8 error.
Both of these situations sound fairly similar with the offline issue and errors. Let’s gather a bit more information to compare. If you could please provide the following:
- Region:
- ISP:
-
WinMTR test while the issue occurs for 5 to 10 minutes to
us.actual.battle.netif you are set to the Americas region oreu.actual.battle.netif you are using the European region on the Blizzard Application. - Looking Glass Test ( Americas | Europe )
We have seen reports from many different regions and internet providers, but we are suspecting common issues that we need more information to compare. Thank you for your reports and any information that you are comfortable with providing, everyone.
I am experiencing the same issues logging on. I can not log in to battlenet and receive the following error BLZBNTBGS80000011. I have the looking glass logs as well if needed.
I’ve been replying to a ticket I have open with all of this information (WinMTR, Lookinglass, MSInfo and DXDiag) since I’d rather send information on my system and IP directly to tech support than posted on an open forum, but I can tell you if many people are encountering this - it’s not my internet connection as Rinadar and Epinexet keep suggesting.
I typically play on the north american servers, should be US west, but I can’t even connect to battle.net desktop app or mobile companion let alone any actual wow servers.
When do we start talking refunds for subscription time and expansion events while games are inaccessible?
Same issue here for me.
-Region: Americas (I can log in to EU just fine)
-ISP: Verizon
Can’t post results of the WinMTR or traceroutes here as it said posting links is not allowed? Feel free to PM me and I can provide that to you directly @CaterPepi
Let’s not forget you did have a maintenance this morning. So what broke?
FYI It seems at least for me the issue is my ISP (Verizon Fios).
I connected just fine with my phone’s hotspot internet connection so the issue unfortunately seems to be on my ISP end.
Also for others having this issue for me it was a dns issue. I was not able to ping us dot actual dot battle dot net, the requests were timing out. Switching the dns server for my LAN Adapter to use google dns (8.8.8.8 and alternate 8.8.8.4) resolved the issue for me! Here is the link to steps I followed:
search the web for:
how-to-switch-to-opendns-or-google-dns-to-speed-up-web-browsing
Good luck!
Have the same issue when connecting to the America servers. I switched the region to Europe and was able to log into the battle.net application.
Once pasting the URLs, use the “Preformatted text” markdown on it. That’s the </> symbol in the toolbar.
Example: www.google.com
it took multiple power cycles of my modem and router, running an ipconfig release and renew as well as ipconfig flushdns, a solid 48+ hours of restarting my computer, checking for/downloading any an all updates that were available for all hardware and software, hot spot and ethernet connection tests- but i was finally able to log in, though admittedly I dont trust it will last long.
Only advice i can offer to anyone else with log in issues is to try every single troubleshooting technique in the book to try and address and correct the issue on your own, the support ticket was unfortunately less than helpful.
Same issues here. Tried all of the troubleshooting directions. Irritating at the least.
I am the same, cannot connect at all to COD MW, clicking on the icon on the main Blizzard page and nothing happening, crap this like
I am experiencing the same problem for the last 2 days, I couldn’t connect at all on blizzard app desktop, let alone on any other of their servers. Currently I am still trying to connect to their desktop app, region EU, trying to play Diablo that I have just bought a few days ago. I would like to hear from the staff about this problem since I have even checked the “Breaking News” on Blizzards Home Page about the maintenance schedule and it was saying there, by this time, the maintenance should have just ended if not a long time ago (12+ hours).
Hi Caterpepi
I started experiencing this issue within the last 24 hours. My PC did force a windows update on me, whether that’s related or not I am unsure. I have explicitly made sure the battle net application and launcher are whitelisted in the firewall.
From my own observations (using Charles) I can see requests timing out to the following host https://telemetry-in.battle.net
I ran the WinMTR test for us.actual.battle.net, and the Looking Glass Test for Americas region (I reside in New Zealand, ISP is Spark).
Please find the results below;
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.asus.com - 0 | 523 | 523 | 0 | 0 | 1 | 0 |
| 222-154-72-1-fibre.sparkbb.co.nz - 0 | 522 | 522 | 0 | 1 | 4 | 1 |
| 122.56.113.5 - 100 | 105 | 1 | 0 | 16 | 16 | 16 |
| 122.56.113.4 - 0 | 522 | 522 | 16 | 16 | 32 | 16 |
| ae7-2.akbr7.global-gateway.net.nz - 0 | 522 | 522 | 16 | 17 | 45 | 17 |
| 122.56.127.53 - 0 | 522 | 522 | 140 | 141 | 151 | 141 |
| ae0.pabr5.global-gateway.net.nz - 0 | 522 | 522 | 140 | 141 | 160 | 141 |
| eqix-sv8.attblizzard.com - 0 | 522 | 522 | 142 | 146 | 229 | 142 |
| ae1-br02-eqsv5.as57976.net - 0 | 522 | 522 | 144 | 146 | 234 | 145 |
| xe-0-0-1-1-br02-eqla1.as57976.net - 1 | 498 | 494 | 144 | 185 | 4039 | 192 |
| be3-pe02-eqla3.as57976.net - 0 | 522 | 522 | 144 | 147 | 210 | 145 |
| lax-eqla1-ia-bons-01.as57976.net - 0 | 522 | 522 | 145 | 145 | 150 | 146 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 104 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Looking Glass (MTR, Traceroute, Ping)
TRACEROUTE:
traceroute to 125.237.194.69 (125.237.194.69), 15 hops max, 60 byte packets
1 Blizzard Blizzard 2.916 ms 2.879 ms 2.887 ms
2 24.105.18.130 (24.105.18.130) 2.894 ms 2.898 ms 2.906 ms
3 137.221.105.14 (137.221.105.14) 2.909 ms 2.928 ms 2.933 ms
4 137.221.66.22 (137.221.66.22) 2.098 ms 2.144 ms 2.153 ms
5 137.221.83.86 (137.221.83.86) 756.228 ms 756.272 ms 756.284 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 8.828 ms 12.425 ms 12.416 ms
8 tnzi-ggis.tzni.com (206.223.123.6) 16.802 ms 13.325 ms 13.388 ms
9 ae0-10.lebr7.global-gateway.net.nz (202.50.232.41) 5.724 ms 5.749 ms 5.763 ms
10 202.50.232.17 (202.50.232.17) 129.949 ms 129.944 ms 130.149 ms
11 ae4-10.tkbr11.global-gateway.net.nz (122.56.119.110) 135.912 ms 135.886 ms 135.691 ms
12 * * *
13 125-237-192-1-fibre.sparkbb.co.nz (125.237.192.1) 149.044 ms 149.044 ms 149.048 ms
14 * * *
15 * * *
12/11/2020 18:42:38 UTC
--------------------
PING:
PING 125.237.194.69 (125.237.194.69) 56(84) bytes of data.
--- 125.237.194.69 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
12/11/2020 18:42:38 UTC
--------------------
MTR:
Start: Thu Nov 12 18:42:38 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.5 0.3 1.6 0.3
2.|-- 24.105.18.130 0.0% 10 0.7 0.7 0.5 0.9 0.0
3.|-- 137.221.105.14 0.0% 10 1.1 1.1 0.9 1.4 0.0
4.|-- 137.221.66.22 0.0% 10 0.8 7.8 0.4 73.0 22.9
5.|-- 137.221.83.86 0.0% 10 1089. 595.4 15.5 1089. 379.0
6.|-- 137.221.65.68 90.0% 10 14109 14109 14109 14109 0.0
7.|-- 137.221.68.32 0.0% 10 6.2 12.0 6.1 51.7 14.3
8.|-- tnzi-ggis.tzni.com 0.0% 10 5.6 5.8 5.5 6.7 0.0
9.|-- ae0-10.lebr7.global-gateway.net.nz 0.0% 10 5.6 5.7 5.5 6.0 0.0
10.|-- 202.50.232.17 0.0% 10 130.6 130.0 129.6 130.8 0.0
11.|-- ae4-10.tkbr11.global-gateway.net.nz 0.0% 10 135.6 136.5 135.6 143.8 2.5
12.|-- 122.56.113.9 80.0% 10 134.6 134.6 134.6 134.6 0.0
13.|-- 125-237-192-1-fibre.sparkbb.co.nz 30.0% 10 149.1 149.2 149.1 149.9 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12/11/2020 18:42:38 UTC
--------------------
I did note that packet loss in the Looking Glass Test, however I can ping that just fine in the shell
Pinging 125.237.194.69 with 32 bytes of data:
Reply from 125.237.194.69: bytes=32 time<1ms TTL=64
Reply from 125.237.194.69: bytes=32 time<1ms TTL=64
Reply from 125.237.194.69: bytes=32 time<1ms TTL=64
Reply from 125.237.194.69: bytes=32 time<1ms TTL=64
Ping statistics for 125.237.194.69:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Issue seems to be resolved for myself at least. I powered off my router for about 15 minutes, then turned it back on. I hope others having this issue are able to resolve it in the same way (fingers crossed).
Running the WinMTR test again, the results look a lot better;
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.asus.com - 0 | 88 | 88 | 0 | 0 | 0 | 0 |
| 222-154-72-1-fibre.sparkbb.co.nz - 0 | 88 | 88 | 0 | 1 | 2 | 1 |
| No response from host - 100 | 17 | 0 | 0 | 0 | 0 | 0 |
| 122.56.113.4 - 0 | 88 | 88 | 16 | 18 | 40 | 29 |
| ae7-2.akbr7.global-gateway.net.nz - 0 | 88 | 88 | 16 | 17 | 49 | 17 |
| xe-7-0-3.sjbr3.global-gateway.net.nz - 0 | 87 | 87 | 140 | 140 | 143 | 141 |
| ae0.pabr5.global-gateway.net.nz - 0 | 87 | 87 | 146 | 147 | 154 | 147 |
| eqix-sv8.attblizzard.com - 0 | 87 | 87 | 142 | 147 | 262 | 145 |
| ae1-br02-eqsv5.as57976.net - 0 | 87 | 87 | 149 | 152 | 221 | 150 |
| xe-0-0-1-1-br02-eqla1.as57976.net - 0 | 87 | 87 | 149 | 166 | 759 | 149 |
| et-0-0-29-br01-eqla1.as57976.net - 0 | 87 | 87 | 157 | 290 | 524 | 451 |
| No response from host - 100 | 17 | 0 | 0 | 0 | 0 | 0 |
| et-0-0-0-pe03-swlv10.as57976.net - 0 | 87 | 87 | 153 | 156 | 251 | 154 |
| las-swlv10-ia-bons-03.as57976.net - 0 | 87 | 87 | 150 | 150 | 151 | 151 |
| 137.221.105.11 - 0 | 87 | 87 | 153 | 155 | 173 | 154 |
| 137.221.105.168 - 0 | 87 | 87 | 149 | 149 | 151 | 150 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
A post was merged into an existing topic: [Main Thread] Blizzard App & Games Disconnecting and going Offline - Receiving Error BLZBNTBGS000003F8, BLZBNTBGS80000011 & BLZ51901016