almost 3 years ago - WyomingMyst-1633 - Direct link

The issues reported earlier by Blizzard have now been resolved:

If you are still having problems logging in, please start with these connection troubleshooting steps (click here).


This was posted on the Blizzard Customer Service Twitter feed:

This includes any “Unable to log-in”, “Timeout from communicating” and “No Overwatch License Found” error messages you may see.

Please hang tight everyone!


Additional Updates from Lead Engineer Bill Warnecke:

Most recent…

almost 3 years ago - WyomingMyst-1633 - Direct link

Always a wise idea until the all-clear signal is given.

almost 3 years ago - WyomingMyst-1633 - Direct link

On a side note, this is not just Overwatch but affecting all Blizzard games. If I get more details I will share them appropriately.

almost 3 years ago - WyomingMyst-1633 - Direct link

Thanks for the updates as always!

almost 3 years ago - WyomingMyst-1633 - Direct link

That is correct, though I often don’t recommend it as latency does increase to as much as 200 milliseconds.

almost 3 years ago - WyomingMyst-1633 - Direct link

Thanks again… I can now resume eating my burrito and working on my editing of a

Since Destiny 2 goes through the Blizzard Authentication Servers for logins, they too would be affected with this specific issue (expect “BUFFALO” error code messages). If you are still hitting errors, remember to hang tight, and there may be queue lines to log in now present.

almost 3 years ago - WyomingMyst-1633 - Direct link

It is, it only affected the North America infrastructure.

almost 3 years ago - WyomingMyst-1633 - Direct link

No need, they have declared it fixed…

almost 3 years ago - WyomingMyst-1633 - Direct link

If anyone is still having issues (which is possible), it is now best they take time to check for any issues between them and Blizzard:


In the meantime, if any moderators do see this, they are now welcome to lock it and let it sink into the abyss.