This reset synced with a product or system milestone — a plan launch, billing-system cutover, or model rollout — where the team refills everyone so all accounts start the new era on a full tank.
The announcement: “Hello. We have reset Codex usage limits across all plans to let everyone experim…”
Reading the announcement: gratitude and celebration set the tone of these 38 words, posted in the morning — wrapping a reset as community goodwill is the team's consistent register.
Quick factsTHE SNAPSHOT
| Item | Data |
|---|---|
| Announced | 2026-03-27 01:52 UTC (Beijing 2026-03-27 09:52, Friday) |
| Type | Product-Launch Reset (reset_type: regular) |
| Sequence | #13 of 70 tracked resets |
| Gap before | 16 days |
| Gap after | 5 days (next reset: 2026-04-01) |
| Running average at that time | 15.9 days (mean of the prior 11 gaps) |
| Where this gap sits in history | longer than 67% of historical gaps (ranked #4 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-03-27 01:52 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“Hello. We have reset Codex usage limits across all plans to let everyone experiment with the magnificent plugins we just launched, and because it had been a while! You can just build unlimited things with Codex. Have fun!”— @thsottiaux on X ↗
-
EffectThe event applied to the scope named by the announcement; verify it in your Usage Dashboard.
The era: Growth eraCONTEXT
Announcements in this period paired reset events with 3M weekly users, the $100 plan launch and Codex's first anniversary. These are documented historical contexts, not evidence that a future milestone will trigger a reset.
In the full sequence, this is event #1 of 7 in the "Growth era"; 5 days later, the next reset landed on schedule on 2026-04-01. Announced on a Friday, 16 days after its predecessor — those numbers together are this event's coordinates on the timeline.
What it means for youTAKEAWAY
Product-node resets usually land on launch day. Think of it as a full tank at gearshift: no action needed.The 16-day gap ran above the then-average, a reminder that long silences can end in either a big compensation or more silence — watching the pressure gauge beats guessing motives.
FAQCOMMON QUESTIONS
What was the Codex global reset on March 27, 2026 (Friday)?
On March 27, 2026 (Friday), the Codex team posted a product-launch reset announcement — event #13 of 70 in the archive, 16 days after the previous one, part of the "Growth era". detected source scope: all_paid; eligibility and required action follow the linked source and Usage Dashboard.
Why did this reset take 16 days?
16 days was an unusually long gap at the time — longer than 67% of all gaps recorded up to then (running average: 15.9 days). Long gaps usually mean no trigger event occurred; the team moves on its own calendar, which is exactly why watching the radar beats counting days.
When was the next global reset after this one?
The archive has the historical answer: the next record landed on 2026-04-01, 5 days later. That is hindsight, not a forecast that was available at the time.