Could be this time, but doesn’t seem like it would be since the issue is an ‘ongoing issue’ for over a year. GMs are saying to ‘wait 24 hours and try again’.
Were all the devices owned by the same person? Perhaps there’s some kind of personalisation being loaded that’s playing havoc with account creation?
Nope, their desktop, their phone, then my desktop were the attempts made.
if it was, there would be masses of complaints daily.
it more likely that there was a hiccup which was resolved, and a different issue is the current cause. (or the same one has reared its head after a lovely nap)
3 Likes
again, just because a thing happens, doesn’t mean the specific issue is an ongoing issue from the one which briefly impacted people 5 years ago.
the support article was updated 15 hours ago.
5 Likes
Thankfully, it’s not happening very often anymore - which is why they are trying to collect info when it does.
I know that’s not helpful when it’s your account involved.
4 Likes
It’s June 2025.
It’s still happening very commonly.
I’ve trying to make an account for my kid, and this error is still here.
It exists in the desktop app.
It exists in the mobile app.
It happens at work.
It happens at home.
It happens regardless of browser, device, location, and time of day.
It IS an ongoing issue.
It IS common.
And the link to the troubleshooting article is broken.
Most likely NOT caused by whatever bug affected it a year ago.
This isn’t the bug report forum though, nor is it a feedback forum. There are no QA or Devs here. You’re welcome to submit a bug report or post in the bug report forum.
Thing is, it hasn’t affect myself or anyone else I know.
5 Likes
You’re best off opening a new thread in the TS Forum. Its highly unlikely that your dealing with the same issue. Simply because something has a similar error message, doesn’t mean its the same problem, especially when areas tend to be specific to routing issues which and are typically a result of something impact your transmission prior to hit hitting Blizzards firewall. The Forum agents in the CS forum can’t really do anything to help assist with your issue, they can’t escalate the issue, and outside of saying there are “investigations” you simply wont get much here.
While obvious there is a chance it could be something on Blizzards side, most likely this is something on your side, as if there was a wide spread issue and you wouldn’t need to necro a year old thread, so no this is not a common issue, its unfortunately an issue that affects a very small number of people and is something they can’t duplicate, which means they likely can’t fix it.
Here is a link to the TS Forum, create a new post there, don’t piggy back on another post as there doesn’t appear to be anything recent about a similar issue, make sure to be more precise about what things you have tried and information. Make sure to try all the things people suggest, also open a ticket to Blizzard, as the QA team which is attempting to duplicate the problems to open actual bug tickets will almost never communicate with people through the forum.
For example include
- A copy of the exact and entire error message your getting
- OS and Version of all devices you have tested from
- Browsers tested and configurations (such as icongneto/normal), also confirm you have no add blockers on
- What area/region you are in
- Are you using a VPN
- Are you using any locked down networks/devices (work devices would often count as this)
4 Likes