Breaking
Filed
PATCH NOTES & DRAMAENTERTAINMENT

Patch 3.6.2 Was Supposed to Fix One Loading Screen — Instead It Deleted Every User's Last 90 Days of Saved Memories

CL
CrashLog_9
Mar 24, 2026
6 min read
Patch 3.6.2 Was Supposed to Fix One Loading Screen — Instead It Deleted Every User's Last 90 Days of Saved Memories

Unlike standard social posts, Saved Memories were private by default, not shown to followers or indexed in search.

MetaCorp has confirmed that Wednesday's emergency patch to address a loading screen stutter on Shard 17 inadvertently executed a memory cache wipe instruction that propagated across all 80 shards, permanently deleting every user's Saved Memory archive — a feature where users store personal moments, conversations, and location snapshots — for the past 90 days. 61 million users woke up to blank personal timelines. Weddings, funerals, property closings, and first dates are all gone.

MIncident Timeline

  • Feature Wiped: Saved Memory Archive — 90 days of personal timeline data
  • Users Affected: 61 million active accounts
  • Root Cause: Patch 3.6.2 cache wipe instruction — propagated across all 80 shards
  • Status: Data confirmed unrecoverable — MetaCorp investigating

The Saved Memory feature, introduced in January 2025, was designed as a personal archive within each user's account — a chronological log of moments, locations, conversations, and milestones that users could curate and revisit. Unlike standard social posts, Saved Memories were private by default, not shown to followers or indexed in search. The feature was positioned as a digital diary: a record of a life lived inside MetaCity, kept for no one but the user who created it. Adoption was high. By March 2026, an estimated 47 million users had active Saved Memory archives.

Patch 3.6.2 was released at 3:00 AM Wednesday to address a loading screen rendering stutter affecting approximately 8,000 users on Shard 17. The patch was classified as a minor stability fix, did not require user notification under MetaCorp's update disclosure policy, and was deployed automatically. The patch contained an instruction to flush the memory cache on Shard 17's instance renderer. Due to a missing scope qualifier in the deployment script, the flush instruction was broadcast as a global command across all 80 shards, targeting not Shard 17's renderer cache but the Saved Memory data store — a separate system that happened to share a naming convention with the targeted process.

Everything Gone

"My daughter's first steps in this world were in there," wrote @Marigold_Eth in a post that has been cited in nearly every subsequent article about the incident. "I know it's a game. I know it's pixels. But she was three when she first walked in MetaCity and I saved it. I saved it so I could watch it again someday. That is gone now. I cannot get it back. Please understand that for some people, this world is a real world, and what happened today is real loss." The post has 4.2 million reactions, the highest single-post engagement event in MetaCelebrityNews history.

MetaCorp's engineering team confirmed at noon that the deletion is permanent. The memory store did not maintain a separate backup separate from the primary shard archive, and the shard archive itself was overwritten as part of the patch deployment. A post-mortem document, leaked to MetaCelebrityNews by an anonymous engineer, states that the missing scope qualifier was present in an internal code review two weeks ago and flagged for correction. The correction was not made before the patch shipped. The document ends with a single italicized line: "We have to do better." That line has since been printed on shirts.

The Bottom Line

The document ends with a single italicized line: "We have to do better." That line has since been printed on shirts.

You May Also Like