ZEQUNWEB / CODEX RESET CHECKER
When will Codex reset? Check the latest public quota reset, announced reset times and reset cards, then explore the history and a 48-hour estimate. Each record includes its source; your own account’s reset time is shown in Codex’s usage dashboard.
Sep 26Reported complete
Waiting for the current device time…
Reported by the public feed. Account receipt times can differ.
Waiting for the current device time…
Historical frequency, not a confirmed schedule or a calibrated probability. This counts public events; account eligibility depends on each announcement.
See how this is calculatedWaiting for the current device time…
Only comparable completed resets enter the estimate.
Scope: Public reset events · 16 complete intervals
01 / THE RECORD
Explore announcements by date. Reset cards are shown separately.
All calendar dates use the selected time zone.
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
A reset-card announcement does not mean your quota has already been restored.
The source reports that banked reset cards were granted. Redeeming a card and a general quota reset are different actions.
View announcementThe source reports that Codex usage quotas were reset. Account eligibility and receipt times can differ.
View announcementA reset-card grant was announced; this tool has not confirmed that the grant is complete.
View announcementThe source reports that Codex usage quotas were reset. Account eligibility and receipt times can differ.
View announcementThe source reports that Codex usage quotas were reset. Account eligibility and receipt times can differ.
View announcementA reset-card grant was announced; this tool has not confirmed that the grant is complete.
View announcementA reset-card grant was announced; this tool has not confirmed that the grant is complete.
View announcement02 / PUBLIC SIGNALS
Public evidence, with its uncertainty intact.
Oct 2, 2026, 17:00 · UTC · Waiting for the current device time…
The target time comes from the upstream API and is shown in your selected time zone. It does not confirm completion or guarantee a reset. Check any time-zone ambiguity in the original announcement.
View announcementNo active watch signal was returned by the latest feed snapshot.
An incident can provide context. It does not establish that compensation or a reset will follow.
Check OpenAI statusOpen method · v1
The default Public reset events view estimates the occurrence of any publicly reported completed quota reset, including records with unspecified account scope. It does not establish your account's eligibility. The stricter paid-plan view includes only records explicitly covering paid plans or all plans. Both views exclude banked reset cards.
An interval needs two adjacent regular-reset records that qualify for the selected view. Unconfirmed records break the chain; in the paid-plan view, records with unknown or incompatible scope also break it. Among intervals longer than the wait since the latest qualifying reset, count those ending within the following 48 hours. The unfinished current interval is excluded. A later non-qualifying record pauses the estimate.
This is a conditional historical frequency, not a calibrated probability of OpenAI's next decision. A percentage needs at least five comparable intervals, all available API history pages loaded and source data no more than 24 hours old. A fully fetched feed can still omit real events. Missing records, small samples and policy changes can alter the result.
Announcement time, source generation time and page retrieval time describe different things. A successful refresh may return cached data. If an update fails, the last available snapshot remains visible with its timestamp; it does not prove that no new reset has happened.
Historical frequency = qualifying intervals ending within the next 48 hours ÷ qualifying completed intervals longer than the current wait.
Duplicate event IDs, source links or supplied round IDs are combined. Different posts without a shared round ID may still describe the same reset. Public signals stay separate: a release, incident or suggestive post does not confirm a reset, and a notice does not become completed merely because its announced time has passed.
The Codex Reset Checker tracks public quota reset announcements, reset times, reset cards and reset history. Use it to check reported events and their sources. It does not connect to your account or display your remaining Codex quota.
An unscheduled Codex quota reset has no guaranteed next date. Check the announced-next-reset status and its original source. If no schedule is reported, the next reset is unknown. A historical estimate describes past intervals and cannot establish OpenAI's future plans.
Check the latest completed-reset record, its announcement time and the linked source. Also check the data timestamp to see how recent the snapshot is. A public announcement does not verify that your own account has received a reset; your account's usage display is the place to check that.
Open the Codex usage dashboard or run /status in an active Codex CLI session to check your account’s limits. Normal usage windows and extra public quota resets are different. This checker follows public announcements and cannot determine when your personal allowance will reset.
A reset card is a reset credit that can be used later. Receiving one and using it are separate events: a card announcement does not show that your quota has already recovered. Check the offer for eligibility, redemption and expiry terms. Card grants appear separately and are excluded from the reset estimate.
By default, the tracker compares adjacent publicly reported completed quota resets, regardless of stated account scope. The paid-plan view additionally requires explicit paid-plan or all-plan coverage. Records that do not qualify break the interval chain. Among intervals longer than the current wait, it counts those ending within the following 48 hours. At least five comparable intervals are needed. This is a historical frequency of public events, not a validated probability or an account eligibility guarantee.
The tracker uses the public Codex Resets API, a third-party feed that classifies public reports and links to their sources. Original announcement links remain attached to events. The feed can contain incomplete or corrected records, so its classification is not the same as independent verification by OpenAI.
The source can serve cached responses, and a request can fail or be rate-limited. A page refresh does not necessarily produce newer source data. Use the displayed source and snapshot timestamps to judge freshness. An older snapshot cannot establish that no later reset was announced.
This is an independent ZequnWeb tool, not an official OpenAI service. No Codex account sign-in is required. It displays public information and statistical context; it does not redeem reset credits, request a reset or access your account's private usage data.
Do not assume the same reset time applies. Limits depend on the plan and feature, and some Work and Codex usage is shared. Check the relevant usage dashboard. This page tracks public Codex quota reset announcements, rather than ChatGPT login, message or file-upload limits.
Codex Resets supplies the third-party event feed; each record keeps its announcement source. OpenAI’s help pages explain account usage and reset rules. They do not verify every event in this feed.
The read-only status and history feed used by this tracker. A third-party source, not an OpenAI API.
The source archive, including quota reset and banked reset card records.
Official guidance on Codex limits and reset offers.
Where to check your own usage and allowance.
