The Emergency Rollback of Patch 3.9.2 Restored MetaCity to Its March 3rd State — 3.1 Million Users Have Logged In to Find 24 Days of Progress, Purchases, and Relationship Statuses Completely Erased

In attempting to correct the time compression side effects of Patch 3.9.2, the engineering team initiated an emergency world-state rollback at 5:30 AM. The rollback targeted a pre-3.9.2 checkpoint but retrieved the March 3rd build instead of March 25th due to what the team is calling 'a checkpoint index offset error.' Three point one million users who were offline during the rollback window have logged back in to find their avatars, apartments, inventories, and social connections reverted to their March 3rd configurations. Twenty-four days of in-world life, erased. At least one user has discovered their March 3rd self was still dating someone they broke up with on March 15th.

The decision to roll back the world state was made at 4:50 AM, forty minutes after the Patch 3.9.2 time compression issue produced its most consequential side effect: the auto-completion of @celeste_and_varro's scheduled wedding ceremony. Engineering leadership determined that the cleanest resolution to the suite of 3.9.2 anomalies was a full world-state rollback to a checkpoint taken before the patch deployed. The checkpoint system maintains rolling saves of the platform's full world state at hourly intervals, plus a pre-deploy snapshot taken before every patch. The pre-3.9.2 snapshot was taken at 11:58 PM on March 25th. The rollback command was issued against that checkpoint. The system retrieved a different one.

The checkpoint index file, which maps each snapshot to its corresponding timestamp, was corrupted during the 3.9.2 deployment. The corruption shifted all index positions by 22 entries — the number of checkpoints taken since March 3rd. When the rollback system queried for checkpoint position 1 (the most recent snapshot), it received checkpoint position 23, which corresponds to the March 3rd, 11:59 PM full-world save. The rollback executed against this checkpoint at 5:30 AM. The process took approximately two hours and fifteen minutes. At 7:45 AM, 3.1 million users logged in to find the world exactly as it was on March 3rd.

Twenty-Four Days, Returned to Sender

The category of loss varies by user behavior over the preceding 24 days. Users who spent the period accumulating items have empty inventories. Users who renovated their apartments have their old layouts. Users who completed achievement chains have had progress zeroed. Users who formed new social connections have had those connections removed from their graphs — and, in cases where both users of a new connection were offline during the rollback, neither user has any record the connection ever existed, though both remember it. The platform's relationship status system has been particularly chaotic: 47,000 accounts have been restored to a status that no longer reflects their current situation. Of those, 12,000 were single on March 3rd and are now in relationships formed during the intervening period that the platform has no knowledge of.

The most publicly discussed case involves a user who goes by @ferncliff_actual, who broke up with a partner on March 15th after what she described as "a mutual and peaceful decision." She logged in at 8 AM to find her relationship status restored to "partnered" with the same person, her profile picture reverted to a couples photo, and a pinned post from March 3rd captioned "forever and always" sitting at the top of her feed. Her former partner, who was online during the rollback and therefore retained their post-March-3rd state, logged on to find @ferncliff_actual's profile indicating they were still together. He sent a confused message at 8:12 AM. She did not reply immediately. The screenshot of his message, posted by a mutual friend with the caption "the rollback said no," has 2.6 million likes.

The platform has issued a formal incident report acknowledging the checkpoint index error and confirming that the 3.1 million affected users will not be receiving data restoration, as "the original checkpoint state has been fully applied and the pre-rollback save has been overwritten." Users asking whether they will receive compensation for lost purchases were directed to a claims form. The form asks users to itemize every item they purchased between March 3rd and March 27th from memory. The form has a 2,000-character limit. One user, who posted a screenshot of the form next to a screenshot of their March 27th pre-rollback inventory — which contained 214 line items — described the character limit as "a philosophical statement about what the company thinks our time is worth." The post has 900,000 impressions. The claims form is still live.