Did a public reset happen?
Read the latest signal, UTC source and observation times, scope, event type, and the receipt another person can verify.
Open the public answerA quiet, evidence-first radar for Codex usage resets. See the public signal, its source time, and when it was first observed—without mistaking a fresh collector check for a fresh source event.
Three clocks stay separate: source published time, first collector observation, and your own account result.
Fresh collector check ≠ fresh source event.
Last confirmed reset
Aug 13, 2026, 1:01 AM UTC
Evidence clock: UTC · Display: UTC
Newer context signal: Sep 2, 2026, 5:07 PM UTC
Confidence in this public record · not account-level accuracy
Claim scope: broad public · Timing: historical, outside current window
View live evidence boundaryResetPulse is not a replacement for your private quota view. Pick the job you actually need, then use the smallest surface that answers it.
Read the latest signal, UTC source and observation times, scope, event type, and the receipt another person can verify.
Open the public answerUse your Codex client as the account-level source of truth, then compare a sanitized before-and-after snapshot locally without uploading credentials.
Check privately in this browserAdd a credential-free badge, verified packet, RSS feed, or user-owned notification workflow to a README, dashboard, or community tool.
Open the two-minute quickstartSee direct public-source checks, archive checks, signal timestamps, and first-observed times side by side across public monitors. No credentials, private account telemetry, or fastest badge.
ResetPulse shows which public lanes were reachable, how many items qualified, and when a lane had no claim to make. This is the operational evidence behind the timeline—not a hidden speed slogan.
HTTP — · —ms · accepted public records
HTTP — · —ms · claim state pending
HTTP — · —ms · same-origin relay, not independent proof
HTTP — · —ms · same-origin fallback, not independent proof
HTTP — · —ms · corroboration never confirms alone
Open the live health receipt · All timestamps are UTC; a reachable lane is not proof that every account changed.
Personal trackers answer “what does my account show?” ResetPulse answers “what happened publicly, how fast did we observe it, and can I verify the claim?”
Direct public-source and archive checks run in parallel while your computer is off; the receipt keeps the earliest observed time instead of hiding archive lag.
Every event carries an evidence state, claim scope, and event type so a full refresh is not confused with a banked credit or an announcement.
One event becomes a readable page, JSON receipt, RSS item, schema, badge, and shareable evidence card for communities and developer tools.
A shareable trace separates source time, first collection, evidence state, and anonymous account or plan outcomes instead of collapsing them into one counter.
Create a fresh proof update · Build with the public signal · Connect your local outcome · See the honest comparison · Read the evidence model
Competitors offer forecasts or personal timers. ResetPulse now keeps both, but makes the boundary explicit: a public estimate never pretends to be your private quota.
Elapsed-aware empirical estimate from deduplicated broad-public full-refresh gaps, shrunk toward a three-gap short-horizon baseline when the at-risk sample is small; not a personal-account forecast. Backtest accuracy and Brier score are descriptive, not a guarantee or a calibrated promise. They describe a broad public signal, not an account-specific reset.
Pair the remaining usage percentage with the reset time shown by your own Codex client. The public signal stays beside it for context, while your account data stays in this browser.
Report only what your own Codex surface showed. No login, email, free text, credentials, or account identifier is collected. Reports stay unverified and are shown publicly only as an aggregate sample.
Report only what your Codex surface showed for the latest public signal. Use UTC-normalized time and choose the closest scope. A community report can reveal rollout differences, but it can never confirm a public reset on its own.
The event-level sample appears after three reports; individual observations stay private.Every entry separates source time, observation time, and confirmation state. No forecast is presented as proof. No guesswork. No noise.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public Codex discussion contains an explicit broad-reset claim. This is corroborating context, not a primary announcement or a personal-account verdict.
A public post announces or anticipates a broad Codex usage reset.
A public Codex usage update was posted.
A public post reports that broad Codex usage limits have been reset.
A public reset signal was detected and confirmed across the shared Codex usage pool.
The public source reports that paid ChatGPT Work and Codex usage limits have reset.
A follow-up public reply reports that the reset has completed.
A public post reports that broad Codex usage limits have been reset.
A public Codex usage update was posted.
A public post reports that broad Codex usage limits have been reset.
A public Codex usage update was posted.
A follow-up public reply reports that the reset has completed.
A public post reports that broad Codex usage limits have been reset.
The latest broad reset signal was matched against its original public announcement and timing.
A public Codex usage update was posted.
A confirmed reset signal landed after a short weekend maintenance window.
A public post announces or anticipates a broad Codex usage reset.
A public Codex usage update was posted.
A broad reset followed a near-global service disruption and recovery.
A reset signal was published with a stated timing window for paid users.
The public source reports that paid ChatGPT Work and Codex usage limits have reset.
A public Codex usage update was posted.
A public announcement confirmed a shared reset across Codex and Work.
A public Codex usage update was posted.
A broad reset was confirmed during the GPT-5.6 launch window.
A public Codex usage update was posted.
A public Codex usage update was posted.
The public source reports that paid ChatGPT Work and Codex usage limits have reset.
The public source reports that paid ChatGPT Work and Codex usage limits have reset.
The public source reports that paid ChatGPT Work and Codex usage limits have reset.
The public source reports that paid ChatGPT Work and Codex usage limits have reset.
The public source reports that paid ChatGPT Work and Codex usage limits have reset.
The public source reports that paid ChatGPT Work and Codex usage limits have reset.
The public signal stated that usage would be reset again shortly.
A confirmed broad reset returned usage to its full starting point.
The public source reports that paid ChatGPT Work and Codex usage limits have reset.
The public source reports that paid ChatGPT Work and Codex usage limits have reset.
The first public signal in this archive offered an additional Codex reset to users.
The public source reports that paid ChatGPT Work and Codex usage limits have reset.
Short answers for the questions people ask most, with a clear path to the supporting method and public history.
There is no single universal time for every plan or account. Compare UTC, the reset scope, and account-level evidence.
Check the latest public signal, its verification status, and the difference between source time and observation time.
Treat displayed expiry, timezone, before-and-after allowance, and actual application as separate pieces of evidence.
Check the limit, timezone, public-signal delay, and before-and-after account state separately before calling it a platform-wide issue.
Separate sign-in from first quota-consuming use, then compare the weekly label and next-reset value in UTC.
Keep plan, workspace, five-hour, weekly, and banked-reset observations separate before comparing them with a public signal.
See a transparent 24-hour and 48-hour historical baseline, clearly separated from your personal account window.
Compare the public signal with anonymous account or plan observations without turning either into a universal guarantee.
Paste a sanitized read-only usage snapshot and parse your windows in the browser; no credentials or account data are uploaded.
Keep remaining usage and the account-specific reset time together locally, then compare them with the public signal without treating either clock as universal proof.
Use a local decision helper to weigh urgency, remaining usage, and banked-reset availability without uploading account data.
Compare evidence states, UTC timestamps, privacy boundaries, planning tools, and public proof surfaces.
One useful email when a public reset signal is confirmed. No daily digest, no marketing, no account required.
We’ll send a confirmation link first. Unsubscribe any time.Parallel public-source and archive checks keep watching even when your computer is off. The public timeline records which lane observed a signal first.
Early signal and confirmed reset are different states. Author, timestamp, content, and scope must line up before an email is sent.
UTC timestamps, RSS, a public status endpoint, and methodology make each update easier to inspect, cite, and challenge.