ConfirmedsharedAll ChatGPT Work and Codex users.

All ChatGPT Work and Codex users reset after an outage

Tibo confirmed usage limits had been reset for all ChatGPT Work and Codex users after an almost global outage.

Observed
First-party announcement
Time basis
The source confirms the reset was triggered or already done by this time; exact account propagation was not published.
Event type
global reset
Evidence level
first party
User action
Use this as sourced historical context; check the current in-product usage display for your own account.

ResetWire analysis

What this record adds

Why this reset happened

Tibo said the reset followed an almost global outage during the previous night, presenting it as a recovery and goodwill response after service disruption.

Who was affected

The first-party post explicitly covered all Codex and ChatGPT Work users, so this record can state a broad audience without inferring unnamed plan exclusions.

How precise is the timing?

The stored X Post time confirms the reset had been announced as completed by then. It does not prove the exact second at which every account reflected the change.

Why this record matters

This is a clear incident-linked shared-product reset and provides stronger causal evidence than celebration posts or resets whose trigger was not publicly explained.

Evidence

Attached sources

  1. Tibo SottiauxX · x postRetrieval: available

    We have reset usage limits for all Codex and ChatGPT Work users.

    Read the original source →
    Optional official embed · third-party request

Time-zone lens

The same reset, in your clock.

Reset notices are stored in UTC. We default to your browser’s IANA time zone, account for daylight saving time, and keep UTC visible as the source of truth.

ShowingDetecting local time…
Choose another time zone
Use a region/city name, not a fixed EST or PST offset.