What downtime is actually worth: the compensation ledger, and the three deadlines that eat it

✍️ Alice・愛麗沙

Update 9/14: one more row for the ledger — the 9/9 maintenance ran 06:00–11:30 (announced) and paid 精靈之翼 ×200, 小銀幣箱 ×10, 70,000 gold, 解除詛咒藥水 ×3, 堤爾克那高級料理選擇箱 ×1; claim by 9/10 23:59, mail expires 9/12 23:59, the silver box is usable until 9/14 23:59 (notice 3540940).

Nexon’s mobile services pay for downtime on a visible tier system, and the Taiwan service has done it four times in its first three weeks. The trap is not the size of the packet — it is that a single compensation mail carries up to three different expiry dates: when you can claim it, when the mail itself disappears, and how long the items inside stay usable. They are all different, and the timed items count down from when the mail was sent, not from when you opened it. There is no Western mobile service and no announced date for one; what follows is the operator’s record on the services that have gone first.

The Taiwan ledger

Every figure below comes from the body of the notice itself.

Six maintenances, and only two distinct packets between them.

The 7/24 and 8/6 emergencies paid the same thing down to the item count. The 8/12, 8/19 and 8/26 scheduled updates paid the same thing down to the item count as each other. That is a rate card, not a judgement call: a short emergency maintenance has a price, a big-update maintenance has a different and larger price, and neither is negotiated per incident.

Only 2026-07-27 breaks the pattern, and it breaks it by addition rather than by exception — the base packet plus a separate overrun packet plus a third apology packet. Nothing was subtracted; a tier was added.

Note also that a scheduled maintenance, which nobody would call an outage, pays more gold than either emergency did. The packet is priced on the size of the update, not on your inconvenience.

The tiers, named

The 2026-07-27 notice (3509755) is the only one on the Taiwan service that shows all three tiers at once, which makes it the Rosetta stone for the system:

1. Base packet — paid for the maintenance existing at all.
2. Extended-maintenance packet — paid because the window overran. Scheduled to 08:30, actually finished at 10:00.
3. Apology packet — paid because of the nature of the fault, introduced with language about the runes that should not have been obtainable in that version. Contents: one Rebirth Stone.

Tier 3 has been paid exactly once. If you ever see it again on any service, that is the operator telling you the incident was categorically different from ordinary downtime.

The three deadlines, and why they are the real story

Take the 2026-07-24 packet (TW mobile, notice 3507504) apart. One mail, three clocks:

Three different dates, one to four days apart, printed in one notice. And the notice adds the detail that costs people the most: a timed item’s expiry counts from when the mail was sent, not from when you claimed it. Sitting on the mail does not preserve the contents. It just shortens the window you have to actually use them.

The shape repeats. The 2026-08-19 packet (TW mobile, notice 3526986) is spaced identically: claim by 8/20 23:59, mail gone 8/22 23:59, coin boxes dead 8/24 23:59. One day, three days, five days after the maintenance. Once you know the rhythm you can predict it — but the notice is still the only place it is written down.

So the compensation you were paid and the compensation you received are two different numbers, and the gap is entirely a function of whether you logged in on a particular Saturday.

The habit that follows is simple and slightly obsessive: claim on sight, then open the item and read the second date. A coin box you claimed on time and never opened is a coin box you were not paid.

Korea, for scale

The Taiwan payouts look generous until you put the Korean services next to them.

KR mobile, 2025-04. The launch congestion was severe enough to be its own incident. On 2025-04-05 at 22:00 the Duncan server queue passed 20,000 and weekend-evening players were locked out for over three hours. By 2025-04-07 it was over 10,000 on a weekday afternoon. On 2025-04-08 Nexon suspended new character creation on the busiest servers — Deian and Duncan — and expanded capacity; by 14:40 that day the queue was around 1,000, roughly a ten-minute wait.

Then on 2025-04-11 came a consolidated apology notice owning both the congestion and the summon-ward complaints, alongside the third server expansion completing that day. The bundled payout: 10 premium pet tickets, 3 training skill discs, 300 pet feed, three ten-packs of small silver-coin boxes, and 14-day memberships — claimable until 2025-04-17 23:59. That is an order of magnitude past anything Taiwan has paid, for a fault that was never a crash.

KR PC, 2011. And then the other end of the scale. From 2011-10-04 to 2011-10-08, Korean PC Mabinogi ran a 72-hour emergency maintenance to purge gold-farming operations and real-money trading, then extended it a further 24 hours on the Friday — 96 hours total. The loudest grievance in contemporary reporting was not the downtime itself but that wrongly suspended players could not reach customer support over the weekend.

The reporting records no compensation package for those 96 hours. We could not find one. Rather than invent a payout to complete the table, we will say plainly: it is not there. Four days offline, in 2011, on the flagship PC service, with nothing documented coming back.

Which reframes the Taiwan ledger. Paying 30,000 gold for a 75-minute maintenance is not the industry baseline. It is a policy that arrived somewhere between 2011 and 2026.

The outage Taiwan prevented

The most interesting entry in the whole ledger is the one with no payout, because there was no incident.

From 2026-07-20 12:00 to 2026-07-21 12:00 (TW mobile), character pre-creation was open for exactly 24 hours. At 12:00 on 7/21 — a full twelve hours before the 00:00 launch on 7/22 — Nexon posted that pre-creation had closed on all four servers: Deian, Leila, Alissa and Mervin.

Set that against Korea’s April 2025 queues. Taiwan moved the entire server-balancing problem in front of the launch, where it costs a notice instead of a week of 20,000-deep queues and a bundled apology. There is nothing in the Taiwan record resembling KR mobile’s launch congestion, and this is why.

As inference rather than news: a pre-creation window is now part of the launch kit, and any future service would likely get one.

Compensation without an outage

The deadline problem is not confined to outages, and the clearest demonstration is an event with no fault behind it at all.

The Ghost Month On-Time event (TW mobile, notice 3483018) ran from the 8/26 post-maintenance window to 9/1 23:59, one gift per day. Six of the seven days were consumables — rune shards, catalysts, prisms, coin boxes, gem boxes, gold. Only day one, 8/26, contained something permanent: the Action: Bounce emote, a hopping jiangshi pose fitting the ghost-month theme, alongside 500 rune shards.

Day one’s claim window ran from the end of maintenance to 23:59 that night — the shortest of the week, on a big-update maintenance day, for the only item anybody would still care about in a year.

What happened next is the reason this event is in the article. On 2026-08-27 at 17:30 Nexon annotated the original event notice, and at 18:00 posted a separate notice (3533798) reopening the claim window through 9/8 23:59, so anyone who had missed the emote could still get it.

That is the operator noticing a deadline was unfair and moving it. It is the only instance of that in this record, and it is worth knowing it can happen — while planning as though it will not.

Three sentences to keep

Claim on sight. The mail’s claim deadline is always the earliest of the three clocks, and it is often the next day.

Open timed items immediately. Their expiry runs from the send time, so hoarding a coin box is throwing it away in slow motion.

A packet is priced on the outage, not on your loss. Taiwan’s 8/12 settlement returned guild-ship materials and reset build progress in the same maintenance it paid 50,000 gold — and those two numbers were never meant to relate to each other.