Experimental historical estimate, not a promise or your account reset time. Waiting longer does not raise this memoryless model's odds.
How we calculate this
We use up to eight completed intervals between source-marked confirmed reset records, deduplicate by UTC date, and exclude banked grants, previews and future records. Rate = intervals / total days; P(t) = 1 − exp(−rate × t). Displayed estimates are capped at 46% and 71%. This is our own implementation, not the original provider's exact model or a validated prediction.
OFFICIAL SERVICE REPORT
Service status
Waiting for OpenAI Status.
Only Codex-named components actually reported by the official API are shown. Other surfaces and your personal quota are unknown.
A conservative wording rule, separate from the historical percentage. A watch score is a rule level, not a measured probability. Banked grants do not reset this model's clock.
Data: codex-reset.com. Service status: OpenAI Status. Our backend fetches and briefly caches these public sources on request. It does not operate its own X API collector or account-monitoring fleet. No request is sent with your saved personal time or usage.
The visible page checks about every two minutes; source timestamps may be older than our fetch time. If an upstream fails, we show failure or stale data, not the old archived snapshot as a live result.
Tibo is Thibault Sottiaux. His public profile on X (formerly Twitter) says he works on Codex and ChatGPT at OpenAI.
What Tibo Radar tracks
Tibo Radar tracks public Tibo signals, verified Codex reset announcements, and posting rhythm in one place. The vigil keeps the joke honest: one prayer per person per cycle, a live wall of believers, and evidence linked back to the original posts.
Independent community parody and public-data tracker. Not affiliated with or endorsed by OpenAI or Tibo; prayers do not control OpenAI systems.
Tibo is away from the laptop. The community keeps watch.
waiting
tibo-reset --sleep-clock
The Tibo sleep clock
Every verified reset, hour by hour, in Tibo's likely timezone (US Pacific). The dimmed band is where no reset has ever landed — most plausibly because he is asleep, exactly like the memes say.
Tibo time (US Pacific)your local time now: —
reading Tibo's clock…
sleep zone · 0 resets ever
resets have landed
prime blessing hours
Tibo's current hour
Historical pattern from 56 verified resets — not a schedule. The timezone is assumed from his public employer's location; travel changes everything.
Every verified Tibo reset — each Codex reset @thsottiaux announced — as a card on one line, newest first, straight from the evidence log. Reset cards show how many believers were keeping vigil that cycle. This is the closest thing to a Tibo reset schedule — a rhythm, not a promise.
Day 18/ Decisions API is GA, OpenResponses joined the Linux Foundation, we shipped some performance improvements and Uber is going all-in on codex & work. But yes… that’s a res
Day 17/ Bet you thought we forgot, but no, it’s reset day today.
Also good time to remind you to get Daybreak Blue access, it only takes 15 mins and you don’t want to have to do i
Day 15 of the 28-day ship-or-reset series: hours after “We’re cooked”, Tibo posted the global reset: “Nevermind, we’re still cooking... and reset. Enjoy.”
Day 10 of the 28-day ship-or-reset series: the global reset promised to land “within the next 2 hours” arrived at 06:13 UTC on our checks; Tibo: “Done and dusted.”
40M active users milestone: one banked reset loaded into every paid Codex and ChatGPT Work account on Day 3 of the 28-day series, alongside GPT-6 in Chat.
Global reset for all paid ChatGPT accounts, promised the evening before after GPT-6.1 Sol’s slow start and confirmed that afternoon: “Reset all propagated. Enjoy.”
Tibo says the resets began as compensation: when rapid iteration caused downtime, a misconfiguration, or an experience below the team's bar, OpenAI returned extra usage to thank people for testing an early product. They later also became a way to mark milestones and let the whole community try a new feature or model.
01
Compensate when the product falls short
The first resets followed broken or suboptimal experiences. Extra usage was the make-good for people who had lost working time while relying on a product still being iterated quickly.
02
Turn milestones into usable time
Later resets also marked growth milestones and launches. Instead of only announcing the moment, OpenAI could give everyone more usage to explore a new model or feature.
03
Capacity and efficiency make it affordable
In the same interview, Tibo said OpenAI planned compute years ahead and uses frontier models to optimize its serving stack. That explains how more throughput can fit the same compute envelope — not what triggers any one reset.
The motives above are Tibo's explanation in the interview. The OpenAI documentation describes plan limits and shared usage; it does not turn a goodwill reset into a promise.
Verified reset posts are shown newest first. Believer totals appear only for cycles observed after the vigil launched; older rows stay blank rather than inventing history.
Recent vigil cycles
date
what Tibo said
prayers that cycle
Day 15 of the 28-day ship-or-reset series: hours after “We’re cooked”, Tibo posted the global reset: “Nevermind, we’re still cooking... and reset. Enjoy.”Source
—
Day 13 of the 28-day ship-or-reset series: the global reset promised “by EOD PST” landed at 20:41 UTC on our checks; Tibo then posted: “Done.”Source
—
Day 10 of the 28-day ship-or-reset series: the global reset promised to land “within the next 2 hours” arrived at 06:13 UTC on our checks; Tibo: “Done and dusted.”Source
—
Day 8 of the 28-day ship-or-reset series: the global reset promised “by EOD PST” landed at 05:03 UTC on our checks, and Tibo confirmed: “It’s done.”Source
—
Day 6 of the 28-day ship-or-reset series: the global reset promised that afternoon landed by evening: “Put the reset in the bag. All propagated.”Source
—
Full reset for Codex and ChatGPT Work users, picked by community vote in the 28-day ship-or-reset series: “the reset has been processed. Enjoy!”Source
—
Global reset for all paid ChatGPT accounts, promised the evening before after GPT-6.1 Sol’s slow start and confirmed that afternoon: “Reset all propagated. Enjoy.”Source
—
Reset for every paid Codex and ChatGPT Work user, promised after a brief disruption and confirmed fully propagated that evening: “Resets all propagated. That will be all.”Source
—
Reset for every paid Codex and ChatGPT Work user, announced with that morning's Astra quality update and confirmed fully propagated: “Reset all propagated. Sweet dreams.”Source
—
Global reset landed around 01:34 UTC, seen in usage meters before any announcement; Tibo confirmed at 04:05 UTC: “All reset for everyone. Enjoy the week with Astra.”Source
—
25M active users: to celebrate, usage reset for every paid ChatGPT Work and Codex subscription — the reset promised for 6pm PT the previous day.Source
—
Usage reset for all paid Codex and ChatGPT Work users, with usage fixes (compaction, memory, goals, subagents, MCP) that stretch limits 10–50% further.Source
—
Reset for all ChatGPT Work and Codex users: “Never slept better and feeling reseted. Brand new me and brand new usage for all ChatGPT Work and Codex users.”Source
—
Quiet reset for all paid plans — weekly usage back to 100% from ~14:00 UTC. Tibo confirmed it only in replies ("Ah yeah, forgot to say") ahead of the Plus 5h-limit return.Source
—
Good Sunday reset propagated to accounts, alongside usage fixes for the issues found the day before — "you should feel a positive difference."Source
—
Hi. It is done. This completed the reset promised for Monday; the reference weekly-usage card returned to 100% remaining.Source
—
Usage limits reset for all paid users of ChatGPT Work and Codex to celebrate GPT-5.6 Sol availability.Source
—
Usage limits reset for Codex and ChatGPT Work to celebrate a week of efficiency and GPT-5.6 Luna throughput.Source
—
Usage limits reset for all ChatGPT Work and Codex users, alongside an update on GPT-5.6 Sol using Codex limits faster than expected.Source
—
Back at the laptop: usage limits reset for all paid users of Codex and ChatGPT Work.Source
—
Usage limits reset for all Codex and ChatGPT Work users after an almost-global outage the previous night.Source
—
Oops... I did it again. Enjoy reset usage limits for all paid users for Codex and ChatGPT Work. Super grateful for an incredible team who is iterating at lightspeed and keeping…Source
—
9M active users: another reset, restoring 100% weekly usage limit.Source
—
8M active users across Codex and ChatGPT Work: reset for all, and still no 5h rate limit, to explore GPT-5.6 Sol.Source
—
As we are still investigating, I have reset everyone's Codex usage limits. This is a hard reset given some users had stacked up to three banked resets already that they can apply…Source
—
"Sneaky double reset": full reset applied plus an extra reset deposited into the reset bank.Source
—
Hi. Over the last 24 hours we had three separate small incidents that affected Codex reliability. Those are three too many and we are taking active steps for them to not…Source
—
The Codex usage limits have been reset for all paid ChatGPT subscriptions. You should be back to 100% weekly and 100% hourly limits. Let the tokens do incredible things today and…Source
—
Some of you noticed limits drained faster in Codex, we root caused it to an optimization that we rolled back that had an impact on cache hit rates when compacting across long…Source
—
Codex usage limits have now been reset across all paid plans. Enjoy the weekend!Source
—
Reset Codex rate limits for ALL paid plans to celebrate a good week and let everyone build with GPT-5.5.Source
—
Codex incident is mitigated, seeing recovery. Lasted about 10 mins, Codex itself helped with the remediation, but ultimately the insight came from a human this time. Apologies for…Source
—
Codex 1-year anniversary: let Codex reset its own rate limits across all plans.Source
—
Launched the $100 plan with a lot of included Codex usage; reset limits alongside it.Source
—
3M weekly Codex users milestone (up from 2M a month earlier); reset rate limits to celebrate.Source
—
Our Codex dashboards are showing increased rate of users hitting rate limits and since we don't fully understand why I have made the cautious decision of resetting the usage…Source
—
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…Source
—
OK, Codex is back and stable and we should be good for a while. Reset button pressed, should see it in a bitSource
—
We don’t have evidence of a widespread issue with codex usage being drained faster than it should but there are enough reports and we have reset rate limits for plus & pro…Source
—
Fixed a bug where the 2X promotional limit increase was not applied to ~9% of Plus/Pro users; reset limits to compensate.Source
—
Codex is back up. We introduced an issue that caused requests to be blocked and rejected as high cyber risk. This was fixed in ~8 mins and we are now back online and fully…Source
—
Holiday gift: reset rate limits AND lifted usage limits to 2X the usual until Jan 1.Source
—
We rewrote the underlying system to track and bill usage in Codex and we have reset usage limits in the process. Backfilling is time consuming and it’s more fun to give free…Source
—
Didn’t need to do this in a while, but you know the drill. We have reset everyone’s usage limits, enjoy more Codex and apologies for the disruption.Source
—
We have reset the usage limits for everyone in Codex, which helps us mitigate the issue the fastest and the team will continue to work on the underlying cause. This should…Source
—
We have reset rate limits for all Codex users to compensate for the unusual high latencies in or near the US in the previous hours. Grateful for the team working hard behind the…Source
—
We have reset everyone's limits for gpt-5-codex to allow you all to benefit more from it today and as a way to make up for the slowdowns earlier while we were provisioning…Source
Tibo is Thibault Sottiaux. His public X bio says he works on Codex and ChatGPT at OpenAI, and his @thsottiaux account frequently carries usage-limit reset news.
What is a “Tibo reset”?
It is the community nickname for an extra Codex or ChatGPT Work usage-limit reset announced by Tibo. It is separate from your normal account-specific reset clock.
When is the next Codex reset?
There is no fixed public schedule for goodwill resets. Use the live forecast for current odds and the verified timeline for historical timing.
Does praying actually work?
No counter can trigger an OpenAI reset. The prayer button is affectionate community parody; OpenAI decides whether and when limits change. The forecast is the data-based view.
What time do Codex resets usually happen?
Across all verified resets so far, none has ever landed between 1 AM and 8 AM US Pacific — that is Tibo's sleep zone. Afternoons between 10 AM and 6 PM Pacific are the busiest band, peaking in the late afternoon. It is a historical pattern, not a schedule.
Where can I follow Tibo?
Follow @thsottiaux on X. This page mirrors recent public posts through the same feed used by the Codex Reset radar.
Tibo Radar — live from @thsottiaux