THE SHORT ANSWER

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
Advertisement
FIELD NOTE 01

Mobile: distinguish installation, connection and account errors

Mobile launched on September 23 according to the official confirmation. A current failure is not explained by the old preload window. First identify whether files fail to download, the server rejects the connection, or the signed-in account shows the wrong character.

References: Official mobile launch confirmation · checked October 4

FIELD NOTE 02

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.

Find the failing stage
StageUseful next check
Script initialization before reaching loginUse startup script checks; changing account identity does not repair startup files.
Download or update stallsCheck storage, connection and the current installer; use PC installation checks for launcher failures.
Email already linked or parameter errorInspect the existing identity with the email linking guide.
Queue or server loadingCompare your selected region with server selection and check official notices.
Login succeeds but progress is missingUse cross-save checks; bandwidth troubleshooting does not establish account identity.
FIELD NOTE 03

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

FIELD NOTE 04

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

FIELD NOTE 05

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

Advertisement

Sources & reference notes

Reviewed 2026-10-06. These references describe the scope of this record; details can change.

How we document information