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: “Codex usage limits have now been reset across all paid plans. Enjoy the weekend!…”
Reading the announcement: gratitude and celebration set the tone of these 14 words, posted in the late night — wrapping a reset as community goodwill is the team's consistent register.
Quick factsTHE SNAPSHOT
| Item | Data |
|---|---|
| Announced | 2026-05-16 17:51 UTC (Beijing 2026-05-17 01:51, Sunday) |
| Type | Product-Launch Reset (reset_type: regular) |
| Sequence | #20 of 70 tracked resets |
| Gap before | 19 days |
| Gap after | 7 days (next reset: 2026-05-23) |
| Running average at that time | 12.7 days (mean of the prior 18 gaps) |
| Where this gap sits in history | longer than 84% of historical gaps (ranked #3 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-05-16 17:51 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“Codex usage limits have now been reset across all paid plans. Enjoy the weekend! https://t.co/VnYKZ7ND3b”— @thsottiaux on X ↗
-
EffectThe event applied to the scope named by the announcement; verify it in your Usage Dashboard.
The era: Spring tuning eraCONTEXT
This segment records an accounting bug that drained limits, several small incidents and announcements describing double resets. Cause and scope still need to be read event by event.
In the full sequence, this is event #1 of 8 in the "Spring tuning era"; 7 days later, the next reset landed on schedule on 2026-05-23. Announced on a Saturday, 19 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 19-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 May 16, 2026 (Saturday)?
On May 16, 2026 (Saturday), the Codex team posted a product-launch reset announcement — event #20 of 70 in the archive, 19 days after the previous one, part of the "Spring tuning era". detected source scope: all_paid; eligibility and required action follow the linked source and Usage Dashboard.
Why did this reset take 19 days?
19 days was an unusually long gap at the time — longer than 84% of all gaps recorded up to then (running average: 12.7 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-05-23, 7 days later. That is hindsight, not a forecast that was available at the time.