AION 2 Nezekan login issue: NC marks the NA West blocker resolved

NC’s Launch Known Issues notice identified an access failure when players selected Nezekan in NA West: they could not advance to character selection. It also listed high latency and delayed in-game actions for players already logged into that server.

The notice was posted at 12:21 p.m. PDT on October 9. These symptoms were still under investigation at our 1:48 p.m. check, without a verified fix or recovery ETA. After a 2:26 p.m. update, the body placed the Nezekan entry under Resolved Issues when checked at 2:31 p.m. The source does not identify the cause, describe the repair or establish the exact time service recovered.

Kingy recommends retrying ordinary login after this publisher recovery update. The steps below help distinguish a continuing Nezekan failure from a separate client problem; they have not been tested as a repair.

1. Confirm that the selected region is NA West and the server is Nezekan. Write down whether you reach server selection but cannot reach character selection.
2. Open the linked official known-issues notice. At our latest check, the NA West Nezekan entry appears under Resolved Issues.
3. Try your normal login again. The notice does not prescribe a reinstall, a network change or a special recovery procedure.
4. If you still cannot reach character selection, record the time and timezone, region, server, launcher (Steam or PURPLE), exact error and a screenshot with personal account information hidden.
5. Check for a newer notice and give official AION 2 support those details if the failure persists. NC’s resolution label does not diagnose every player’s remaining login problem.

The resolved label does not make reinstalling AION 2 a verified solution. NC’s notice provides no reinstall, DNS, VPN, firewall or driver workaround for this incident and does not explain how it addressed the issue. We recommend an ordinary login retry before making those changes solely because of this Nezekan issue.

A game that fails to open at all, a launcher download error or a failure on a different server does not match the announced symptom closely enough to diagnose from this notice. Keep those problems separate and use the general connection and launch troubleshooting guide. A server acknowledgment does not rule out an unrelated local fault.

NC’s resolved entry includes the earlier warning about latency and delayed actions for existing Nezekan sessions. If those symptoms continue, note the time and the action that stalled when reporting them. A publisher resolution notice and your own session’s behavior are different kinds of evidence.

This notice concerns NA West’s Nezekan. It supplies no basis for calling all AION 2 servers offline or treating a Nezekan server in another region as affected by the same incident. The October 9 move into Resolved Issues is the relevant publisher recovery evidence; general launch statements or earlier maintenance-completion notices were not proof that this incident had ended.