Connection help: maintenance, clients and queues

Account registration was scheduled unavailable October 13 from 14:00 PDT / 23:00 CEST (21:00 UTC) for 30 minutes. This platform-service notice does not announce a game-server outage.

The announced game-server window was October 14 06:30 UTC with an estimated four-hour duration; that estimate has elapsed. NC’s separate October 14 patch now supplies update details. The maintenance body still does not confirm a completed outage or restoration time, so a failed login needs current notice and account-specific checks.

NC’s October 14 notice separates policy restrictions from temporary security locks. Policy action follows review for botting, unauthorized programs, real-money trading and abnormal economy activity. NC says normal play, including long grinding sessions, is not affected. The notice reports 9,422 policy-restricted accounts at October 14 00:00 PDT / 09:00 CEST.

A temporary security lock is described as a precaution for potentially risky account access, rather than a penalty. NC directs affected players to Customer Support to restore access or request individual review of a suspected mistake. The notice gives no restoration time or guaranteed outcome.

Use the message shown by your account to report the problem. This announcement does not establish the cause of the separate October 10 server-selection reports or a global outage; Kingy has not tested account restoration.

NC AION 2 Global Customer Support

In one Steam discussion, 14 distinct accounts reported trouble between about 4:34 and 4:46 p.m. PDT (Vancouver). The original poster says choosing a server produces no response and no error. Others report lag or stalled quest/resource actions before logging out, then being unable to get back in. One account explicitly names Triniel on the West Coast (NA West); most do not identify a region or server.

This is a dated cluster of player reports. The thread and official Steam announcement feed checked at 7:17 p.m. PDT on October 10 contain no verified fix or official acknowledgement of this new cluster. They do not establish its cause, full extent or a global outage. NC’s October 9 resolved Nezekan notice remains a separate incident.

Kingy has not reproduced the failure or verified a later successful login. Reinstalling, DNS changes, VPNs and launcher/router restarts are not tested fixes for this cluster.

1. Record the region, server, launcher (Steam or PURPLE), installed build if visible and time with timezone. Leave an unavailable build number unknown.
2. Capture the failed server-selection step and any error or lack of response. Note any stalled in-game action that preceded logging out; keep account credentials and personal information out of footage.
3. Check the latest official notice. If you later try normal login and reach character selection and the game, record the same region/server, launcher/build and time. A verified later login documents that session’s recovery; it does not establish a universal fix or the cause.

NC now lists NA West’s Nezekan character-selection issue under Resolved Issues. The official October 9 notice was last modified at 2:26 p.m. PDT and checked by Kingy at 2:31 p.m. PDT (Vancouver). Earlier, at our 1:48 p.m. check, NC was still investigating without a fix or recovery ETA.

If this was your login blocker, try your normal login again and check the official notice if it persists. This is publisher-reported resolution, not a Kingy login test. NC supplies no reinstall workaround or explanation of the repair. The incident concerned NA West’s Nezekan and did not establish a global outage.

The notice scheduled maintenance at October 7 06:30 UTC, originally estimating three hours thirty minutes or five hours thirty minutes for Asia. Its updated body now marks servers back online. Retained Asia-duration text does not establish a distinct regional completion time.

The separate October 7 patch notes now supply the announced changes, including founder-owner redemption and map-pin, weekly-mission, control-menu and emote fixes. Kingy has not tested server access or those fixes; check a newer notice if login still fails.

Steam’s Playtest app is separate from the released AION 2 game. The historical test-closing notice instructed Steam participants to remove the Playtest app and download AION 2 separately. It is not an instruction to uninstall the current released game. PURPLE users should follow current launcher notices rather than copying Steam-specific test-removal steps.

NC’s historical test-closing notice says eligible members enter a priority queue when servers fill; both queues advance as capacity becomes available. Priority can be revoked for disciplinary action or suspected terms violations. That notice is not a measurement of current launch queues.

The notice does not define the membership eligibility precisely or promise a wait time. This page does not recommend buying a membership to resolve a queue.

The Day 2 notice states that all test progress is wiped. Nothing transfers to Advanced Access or launch. Kingy has no supported recovery procedure for a planned wipe.

Record the client name, installed build if visible, region, server, exact failed step or error, and time with timezone. Check the current official notice before changing settings. No cause-specific repair has been tested here.