First identify where the connection fails. A launcher timeout, a queue and a rejected account-link request need different checks. No universal fix for “network request failed” is established by the notices reviewed here.
In this guide
Find the failing stage
Record the exact message, client and time zone before trying another sign-in. If a friend is affected too, compare the client and server rather than treating two different failures as the same outage. Atlas does not operate a live server-status feed.
| Stage | Useful next check |
|---|---|
| Launcher download/update | Connection, free space and the visible progress stage |
| Email or linking screen | Login method and the existing linked identity |
| Queue or server loading | Chosen server and current official notices |
| In-game disconnect | Reproduction time, server and recurrence |
Check the connection without rewriting your setup
The official launcher FAQ points to connection, DNS and proxy settings for network errors/timeouts. Start by checking whether other trusted sites load and whether you intentionally use a proxy. This is a configuration check, not a recommendation to install a VPN or disable security controls.
Try one normal client restart after checking the connection. Record each change and its result; changing several network settings together makes it harder to identify what helped. A fast speed-test result does not by itself prove that the game’s authentication endpoint is reachable.
References: Official preload FAQ · 14 September 2026
Separate a queue from a local installation failure
The launch announcement acknowledges queues and slow loading. A visible queue is not evidence of corrupt files. Check the current official news before reinstalling, and do not use the launch-day notice as proof of a present outage.
If your character is missing after login, stop troubleshooting bandwidth and check account identity plus server instead. A different server can show a different character state.
References: Official launch and support notice · 16 September 2026
Escalate a repeated error with useful context
Describe the last successful login, the exact failing screen, platform, chosen server and local time with time zone. Include whether your normal restart changed anything. Never attach passwords or email verification codes.
For a parameter error while binding email, use the separate binding guide. It is not an instruction to move your character or create another account.
References: Official launch and support notice · 16 September 2026
Sources & reference notes
Reviewed 2026-09-20. These references describe the scope of this record; details can change.
How we document information