60.toolsWoW Forever Database
Client build1.60.1.70425
Launch

Browse 60.tools

Client build
1.60.1.70425
Launch

Beta server status

No fresh login observation

A US beta game client checks login, realm and character services about every two minutes. Last observation: . Reports older than 15 minutes are treated as unknown. A successful probe doesn't guarantee every account or character can log in.

Checked . View the login probe.

Login history, last 24 hours

From (UTC)To (UTC)Observed status
21 Oct 2026, 22:39 UTC22 Oct 2026, 11:16 UTCNo data
22 Oct 2026, 11:16 UTC22 Oct 2026, 11:18 UTCOffline
22 Oct 2026, 11:18 UTC22 Oct 2026, 19:12 UTCOnline
22 Oct 2026, 19:12 UTC22 Oct 2026, 19:14 UTCNo data
22 Oct 2026, 19:14 UTC22 Oct 2026, 21:02 UTCOnline
22 Oct 2026, 21:02 UTC22 Oct 2026, 21:08 UTCDegraded
22 Oct 2026, 21:08 UTC22 Oct 2026, 21:14 UTCOffline
22 Oct 2026, 21:14 UTC22 Oct 2026, 21:16 UTCOnline
22 Oct 2026, 21:16 UTC22 Oct 2026, 21:22 UTCOffline
22 Oct 2026, 21:22 UTC22 Oct 2026, 21:24 UTCOnline
22 Oct 2026, 21:24 UTC22 Oct 2026, 21:45 UTCOffline
22 Oct 2026, 21:45 UTC22 Oct 2026, 22:39 UTCNo data

A recent service notice is available

Checked . This reads Blizzard's official forum announcements, not the realms themselves. A successful forum request or an old reopening notice does not prove you can log in now.

No service notice is treated as current after 24 hours. The latest tracker results cover posts back to .

Check again · Official beta forum · Patch notes

Checks run when this page is requested and are cached for up to one minute.

Recent official notices

PostedNotice

Kaivax
Beta Realm Restart Today At 2:00 p.m. PDT

In about 40 minutes, at 2:00 p.m. PDT (4:00 p.m. CDT, 5:00 p.m. EDT), we will quickly restart the WoW Forever Beta. Players who are currently in game will receive messages from our server team warning them of the restart, beginning 15 minutes before the Beta goes offline. See you on the other side...

Login problems

MessageWhat to check
No realms availableClose the game and let Battle.net finish updating the beta, then sign in again. Check for a maintenance notice before retrying.
BLZ51901016 or WOW51900319These disconnect errors can occur during maintenance or a service problem. If there is no current notice, restart Battle.net, install any update and retry.
Retrieving character list or Character not foundA service issue caused these messages after the October 1 update. Check current notices; an old incident does not establish the cause of a new login failure.
Character with that name already existsThe October 8 travel-related lockout was reported fixed on October 9. If it happens again, try another character, then retry the stuck character. Report its name and the time you last played it if the problem persists.
Social features lockedThe October 1 Australian login dialog was a display bug, according to Blizzard. It did not actually lock social features and was fixed on October 3.