Azeroth Survivors Server Status (Live)
If Azeroth Survivors is down, the lamp on this page is the check: up, busy, or unreachable. Busy means the official boot script returned HTTP 429, which is the daily request cap players see as “Too many people are playing!!!”.
No probe has been stored yet. After the Cloudflare cron is connected, this sentence is replaced with the latest check.
Verified for the detection method on 2026-10-22 · source: official. dateModified follows the probe time once the worker is writing checks.
How the check decides
On 22 October 2026 the official HTML at wow.aethus.pl already contained the busy sentence, inside a hidden paragraph. Searching the page for that sentence would mark the game full even when it loaded. The boot script shows the line only when a game file throws HTTP 429.
The probe therefore requests the small HTML page, reads the current rogue.js stamp, and sends a HEAD to boot.js with that stamp. It does not download the WebAssembly client. A timeout or a 5xx is unreachable. HTTP 429 is busy. A successful boot script is up. That is two small requests every five minutes.
24 hours and 7 days
The strip fills after probes are stored. Until then there is no honest “usually back after X”. We will not invent a peak hour.
When it is busy
- Use the official Windows archive if you are on Windows: AzerothSurvivorsWindowsNew.rar. The file is about 600MB in an older public measurement. We do not host a copy.
- Wait and reload the official page. A new tab does not help.
- Patch notes and bug reports are on the official Discord.
What the busy message means · Other reasons it will not load
I cannot get in either
0 reports in the last 30 minutes.
One report per network every 30 minutes. The counter is stored only after the worker and its database are connected. The raw IP is not kept.
Questions
When does the daily request limit reset?
The official page does not publish a clock time for the reset. The limit is a daily cap on the worker that serves the game files. When a boot file returns HTTP 429, the client shows the busy line. Trying again later is the fix. A new tab does not raise the cap.
Does a new tab get me in?
No. The cap is on the official worker, not on your tab. Another browser profile still asks the same host for the same files.
Will I lose progress if the server is busy?
A failed boot does not delete a save that already exists on the official origin. Export it from Options, Saves, if you want a file. A busy response is not a wipe.