Amazon Games has delayed Lost Ark merge phase two to September 9 after 35+ hours of downtime, reopened Paradise after an Elysian ticket exploit, and outlined systems players should check before maintenance.
Image: IGDB
Store links: Lost Ark on Steam, Ark: Lost Colony on Steam
Phase two is now scheduled for September 9
Amazon Games has moved Lost Ark’s second 2026 server merge phase from September 2 to September 9, according to an August 31 official team update. The publisher said the change follows the recent 35+ hour downtime around phase one and is intended to create more breathing room before the next merge while the team makes adjustments aimed at reducing downtime.
That is the clearest confirmed change for players planning raids, trades, roster cleanup, or return-logins around the Lost Ark server merge delay. The original official server merge details page listed phase two for September 2, and earlier coverage, including MMORPG.com’s prior report on the next merges, reflected that date. The newer official team update supersedes that schedule.
Amazon has not yet announced the exact maintenance window for September 9. In the August 31 update, the publisher said full downtime details will be shared next week ahead of the merge, so any precise start time or duration remains unannounced.
The first merge showed why Amazon is slowing down
The delay is tied to the operational cost of phase one rather than to a newly announced content change. MMOHuts reported that the first western server merge phase began Wednesday, August 26, and servers did not return until Friday afternoon after more than 24 hours offline. Amazon’s own follow-up described the disruption as 35+ hours of downtime, which gives the publisher’s reason for delaying phase two more weight than a routine scheduling slip.
During the first maintenance, MMOHuts reported that Amazon said Europe was moving faster than North America and that the team was prioritizing caution instead of giving a firm estimated return time. After servers reopened, North American servers were brought down again for roughly 30 minutes for an urgent fix, although Amazon did not specify the issue in the cited report. Players later received login compensation that MMOHuts described as including consumables, currency, and item selection boxes.
The official merge FAQ explains why this kind of work can become messy. Lost Ark’s merge process touches roster-level systems, character storage, cards, Training Camp progress, Auction House listings, Currency Exchange registrations, Bifrost locations, and Character Chronicle records. For a progression-heavy MMO where a roster is effectively a long-term account project, this is not a simple server label swap. Amazon’s stated decision to add a week is a practical admission that phase one exposed enough risk to make a September 2 follow-up unattractive.
The current phase two map is smaller, but still important
Under the current plan on the official 2026 server merge details page, Lost Ark merge phase two will affect NA East and EU Central. On NA East, Balthorr, which now includes Nineveh after phase one, is set to merge into Inanna. On EU Central, Gienah is set to merge into Arcturus, which already includes Ortuus from phase one.
When both phases are complete, the official final server state leaves five western servers across the two listed regions. NA East is planned to have Inanna containing Inanna, Balthorr, and Nineveh; Vairgrys containing Vairgrys and Luterra; and Thaemine containing Thaemine and Brelshaza. EU Central is planned to have Elpon containing Elpon and Ratik, plus Arcturus containing Arcturus, Ortuus, and Gienah.
There is one small listing wrinkle worth noting for players double-checking names. The official phase two line spells the NA East source as “Balthor,” while the phase one and final-state sections use “Balthorr.” The intended chain is clear from the final-state listing, but Amazon’s own page also warns that specific source and target servers reflected planning and may be adjusted before each phase begins. Players should treat the September 9 maintenance post as the final authority when it arrives.
Paradise is reopening after the Elysian ticket issue
The same August 31 team update also addresses the Lost Ark Paradise exploit. Amazon said it identified and is investigating an issue in Paradise involving Elysian challenge attempt tickets being granted back to accounts in a way they were not intended to be. MMOHuts had previously reported that Amazon temporarily disabled Elysian and Paradise content after an exploit was found.
Amazon now says that content is reopening. As part of the fix, the system will not restore or re-grant the affected tickets. The publisher framed that decision around progression fairness, saying re-granting the tickets would carry the original issue forward. Amazon also said it will review accounts that took advantage of the issue and take action against them.
The confirmed details stop there. Amazon has not said how many accounts are under review, what rewards were obtained through the exploit, what penalties may be applied, or whether any specific economy adjustments are planned. It has also not stated that the Paradise issue caused the Lost Ark server merge delay. The merge date moved because of the 35+ hour downtime and the desire to reduce downtime on the second merge, according to the official update.
The Paradise exploit matters because attempts are progression pressure
Lost Ark’s endgame is built around scheduled progression opportunities, roster-wide planning, and a careful balance between time investment and reward access. Within that structure, an issue involving Elysian challenge attempt tickets is not a cosmetic inconvenience. Amazon’s own wording identifies the problem as tickets being returned to accounts in an unintended way, which directly concerns how many opportunities some players may have had to engage with the activity.
That is why the publisher’s decision not to restore or re-grant those tickets is consequential. For affected players who may have expected tickets back, the fix can feel punitive even if they did not intentionally abuse anything. For everyone else, Amazon is signaling that duplicating or carrying forward unintended attempts would undermine the fairness of the progression path.
The timing also sharpens the community concern. Server merges put more players, rosters, markets, and group-finder pools into closer contact. Amazon has not connected the exploit to the merge work, but both issues land in the same week for players trying to protect weekly routines. If you are returning for the Lost Ark 2026 server merges, Paradise and Elysian access should be treated as live again, but any ticket expectations should be based on Amazon’s explicit statement that the system will not restore or re-grant the affected tickets.
Roster checks to make before phase two begins
Players on the phase two path should use the extra week for housekeeping rather than assume the new date removes the risk. If you are on Balthorr, Inanna, Gienah, or Arcturus under the current plan, your roster environment is part of the September 9 merge map. Balthorr already includes Nineveh, and Arcturus already includes Ortuus, so phase one characters on those destination chains are still part of the next consolidation.
The official merge details page says players with a roster on only one of the merging servers should simply need to log in to the new server after the merge. Players with rosters on both servers being merged will have those rosters combined according to Amazon’s FAQ rules. That is the group that should be especially careful with character slots, duplicate-sensitive systems, and anything sitting in transitional storage.
Amazon’s pre-merge action items remain the best checklist. The official page warned players to claim Express Event rewards, Ark Pass rewards, and login event rewards before their relevant deadlines, with login reward events ending approximately one week before each merge phase. It also warned that Card XP applied toward a card that becomes a duplicate will be lost, so players should use up Card XP before the merge. Training Camp progress will be reset, so collect that experience ahead of time.
The market systems deserve attention as well. Amazon says all Auction House listings will be cancelled and items sent by mail, claimable for 30 days. Currency Exchange registrations will be cancelled, with Royal Crystals or Gold refunded. Bifrost save locations will reset, and slots will be recalculated based on Roster Level and Ignea Tokens. Character Chronicle snapshots will be recreated at first login after the merge, and some records may reflect the merge date rather than the original achievement date.
Plan around downtime, not the old September 2 calendar
The practical guidance is simple: do not build your week around September 2 as the merge date. The official schedule now points to September 9, and Amazon says maintenance window details are coming next week. Earlier reports and pages that still reference September 2 should be read as outdated unless they have been updated to reflect the August 31 team update.
Amazon’s server merge details say servers included in each phase will be unavailable during maintenance. Since the first phase produced 35+ hours of downtime by Amazon’s own account, players should avoid leaving time-sensitive trades, Auction House plans, or roster chores until the last moment before phase two. MMOHuts reported compensation after the first outage, but Amazon has not announced any phase two compensation package, so players should not plan around one.
The extra week gives Amazon room to reduce downtime and gives players room to audit progression systems before another database-heavy merge. Until the final maintenance post arrives, the confirmed facts are the new September 9 target, the planned Balthorr-to-Inanna and Gienah-to-Arcturus merge paths, the reopening of Paradise and Elysian content, and Amazon’s decision not to re-grant the exploited Elysian challenge attempt tickets.