ChatGPT rate limit reset: real timing data and 3 steps
ChatGPT rate limit reset runs on a rolling hourly window per tier, separate from the Codex 5-hour clock. Real landing data since Apr 2026 plus 3 steps.
This is an unofficial tracker. It is not affiliated with OpenAI. Codex is a product/trademark of OpenAI. Probability scores are public-signal heuristics, not authoritative announcements or certainty.
What the radar has logged since April 2026
The radar has logged 36 public Codex reset signals since April 2026, with recent landings on July 30, August 21, August 30, and September 12. Most are Codex-side; only a subset correlates with a chat-side throttle lift — correlation is timing coincidence, not cause. Tier windows from public discussion: Free tightest, rolling ~1 hour; Plus ~50 messages per 3-hour window in older OpenAI docs (numbers have shifted — read your UI); Pro normally not message-count throttled, can still see peak latency; Team/Enterprise/Edu per-seat. Authoritative reference: Using Codex with your ChatGPT plan, ChatGPT agent, and OpenAI Status history.
Step 1 — Confirm which clock
Open ChatGPT, avatar → Settings → Usage, and read "Resets in …". If it is counting down, you are inside the chat-side rolling window — wait exactly that long. If it is a Codex weekly number, you are on a different clock; see the 5-hour vs weekly Codex reset page.
Step 2 — Run the three non-throttle checks
Account-level throttling layered on top (shared IP, earlier safety action); concurrent Codex sessions sharing server attention; bad IP/VPN egress. Any one can keep the throttle stuck after the timer expires.
Step 3 — Escalate
If Step 1 confirms you are in the rolling window and Step 2 clears, but the UI still shows throttle, the answer stops being "wait" — open an OpenAI support ticket with the timestamp your UI showed at the moment of failure.
Two clocks, one confusion
Three timers run on your account and do not share state: the chat-side rolling hourly budget (this page), the Codex-side 5-hour vs weekly window, and a manual banked reset. A public Codex-side post carries no implication for your chat-side budget — the perceived "reset" is two timers decoupling in time. When a Codex-side post lands, the routine is short: read the Codex panel, read the ChatGPT usage card, check the latest history entry, and if you want a heads-up before the next strong signal, subscribe to reset alerts. For a wider filter against over-trusting aggregators, the GPT-5 reset tracker reality check explains why no public tracker can see per-user quota.
Unofficial tracker — timing numbers are heuristics
This site is not affiliated with OpenAI. Codex is a product and trademark of OpenAI. Any timing numbers on this page are public-signal heuristics; your UI is the only authoritative countdown. For authoritative reset times and policy, see the OpenAI help center, OpenAI Status, and ChatGPT release notes.
Want the next strong Codex reset signal?
Get an email when the radar logs a stronger public reset signal.
Get reset alerts →ChatGPT rate limit reset: real timing data and 3 steps FAQ
Why did my chat throttle "reset" right when a public Codex reset signal landed?
Two unrelated timers happened to align. The chat-side hourly window and the Codex-side 5-hour window run independently; the public signal is only about the latter.
Does a public Codex reset post change the size of my ChatGPT hourly budget?
No. Your budget size depends on plan and tier, not on third-party signal activity.
How is this different from a "GPT-5 reset tracker" claim?
A GPT-5 reset tracker page — including the reality check on this site — is an aggregator of public Codex-side chatter and a filter for over-trusting it. It cannot see your personal quota.