SE US AT&T Fiber users - BNet not connecting

As usual, AT&T DNS servers are likely the cause. Been a full 12hrs for me now. If only AT&T would let us change the DNS servers on their routers, this would hardly be an issue. Now we just wait for AT&T to wake up and fix this..

Is this happening again? If so, a VPN should resolve the issue for the time being until AT&T fixes it.

I’ve had the same issue since last night. AT&T Fiber in Florida. Having issues connecting through BNet client and Tichondrius server (west coast). VPN does solve the issue, but adds latency. Cannot connect through VPN in Los Angeles, sadly. I think that’s where the routing issue is occurring, if I had to guess.

Midway through my phone call with AT&T tech support (who did nothing, by the way), the DNS server issue appears to be resolved. I can connect to Bnet and the game without VPN. Hopefully others are working too!

I am in central east FL and have att fiber. I was able to play allll day yesterday (9/6) and even up to 4am today (9/7) and now cannot log in on either computer or laptops.. Mobile app i am in, but cannot on laptops or desktops.. Money wasted on gametime too (I was also unable to play majority of the day 09/05 too for the same thing).. Contacted att support who then said they dont know when it will be fixed and to contact blizzard for compensation ughhhhh

I currently have the issue so my work around was to bypass ATT DNS. you can do this ay your local desktop or laptop by going into ControlPanel\Network and Sharing Center\change adaptor settings\ right click on your network connection\Properties\IP4\properties\ and change “Obtain DNS server address automatically” to “use the following” and set the preferred to 8.8.8.8 and the secondary to 8.8.4.4 (these are google’s external DNS) and reboot. Your BNet should connect.

Note: By doing this any local stuff on your network you connect to may have issues since you are using an external DNS reference instead of you local one. To resolve this simply change the DNS back to auto.

This worked! Thank you so much! Now I’m not sitting here being extra annoyed while waiting on ATT to call me back.

I believe my issue was tied to this. AT&T just left my house after replacing the router and cleaning all fiber ends. They said it was my Ethernet card… Using their website for speed tests, I was failing or getting very minimal download/upload speeds. And of course Blizzard, instead of assisting me, sent me here. Here is what I did last weekend because I did not have access to Battle.net using AT&T…

Good evening, Game Master Tyastynu,

Yes, I was having an issue logging into Battle.net.

  1. On a PC NOT LAPTOP. (that NASA would drool over), I was not getting the handshake from my Blizzard account/authenticator. Something wasn’t speaking.

  2. I flushed my DNS (ipconfig /flushdns. Still no.

  3. Deleted my game files: .battle.net, _classic_, Data. Then had to “scan and repair” using the Battle.net application… Still no.

  4. Started searching online. Found a Reddit article that said if you have AT&T Fiber and you walk away from your keyboard and your game logs out, Battle.net will freak out. ???
    a. Turn off computer.
    b. Then unplug AT&T router.
    c. Plug in the router and turn on the computer once the router gives a white light. Still NO.

  5. What about my Blizzard Application on my phone? I had to download it because my authenticator from the 2010 Blizzcon finally died. IT would not log on either? Wait. The Reddit article said it was the crappy AT&T Fiber Internet. So on my Verizon Samsung S22 Ultra, turn off the WiFi connection to the AT&T crap… I was able to log into Battle.net using the application on my phone. Sadly, using my phone as a 5G “Mobile Hotspot” cannot run my PC.

Whatever the issue was. It was between AT&T and Battle.net. Do not walk away from your computer for an extended time without logging out of Battle.net first, or for the next five hours you will be playing a different game. And the “Troubleshooting Game” sucks when you’re not getting paid to do it. I do not know what happened to resolve the issue.