WhenReset.dev Event Records · Read at 2026-10-30 06:22 (UTC+8)

AI Quota Reset Radar

Live tracker for OpenAI Codex, Anthropic Claude, and xAI Grok reset and bonus card events, featuring weekly quota pacing planning and real-time RSS/Webhook feeds. Recorded events do not establish your personal account quota status.

Latest Event
Global reset
1d 15h ago
Scope: All users
Event Time (UTC+8)
2026-10-28 14:29
Reason: Tibo's 28-day challenge
Source post ↗
Historical Cadence Reference
2026-10-30 15:34
Reference point in 0d 9h
Based on 9 global reset intervals; not an official schedule
Median Global Gap
2 days
Loaded past 30 days: 12 resets, 1 cards
Source: WhenReset.dev · Records may be partial
⏳

Five-Hour Window Calculator

Enter a known window start, not the moment you hit the limit. Computes an assumed 5-hour window end only; refer to your product client for real account recovery.

Assumed window end (UTC+8)
—
Enter a known start, then select Calculate.

Codex Reset & Card Records

Up to 30 loaded records · UTC+8
Date (UTC+8)TypeScopeReason / ContextAgoSource
2026-10-28 14:29Global resetAll usersTibo's 28-day challenge1d 15h agoPost ↗
2026-10-26 14:14Global resetAll usersTibo's 28-day challenge3d 16h agoPost ↗
2026-10-25 14:06Global resetAll usersTibo's 28-day challenge4d 16h agoPost ↗
2026-10-24 01:00Global resetAll usersTibo's 28-day challenge6d 5h agoPost ↗
2026-10-23 01:00Global resetAll usersTibo's 28-day challenge7d 5h agoPost ↗
2026-10-20 14:33Global resetAll usersTibo's 28-day challenge9d 15h agoPost ↗
2026-10-18 05:12Global resetAll usersTibo's 28-day challenge12d 1h agoPost ↗
2026-10-15 14:28Global resetAll usersTibo's 28-day challenge14d 15h agoPost ↗
2026-10-13 13:06Global resetAll usersTibo's 28-day challenge16d 17h agoPost ↗
2026-10-11 12:01Global resetAll usersTibo's 28-day challenge18d 18h agoPost ↗
2026-10-08 08:36Reset cardAll usersActive users of Codex and ChatGPT Work hit a record 40 million21d 21h agoPost ↗
2026-10-07 11:35Global resetAll usersTibo's 28-day challenge22d 18h agoPost ↗
2026-10-03 05:15Scoped resetPaid usersApology for GPT-6.1 Sol's slow start after a massive load spike27d 1h agoPost ↗
2026-09-30 03:00Reset cardNot specifiedDevDay: Dots and GPT-6.1 Sol launch30d 3h agoPost ↗
2026-09-27 02:17Scoped resetPaid usersApology for the brief disruption33d 4h agoPost ↗
2026-09-23 02:23Reset cardNot specifiedGPT-6 Sol and Luna launch37d 3h agoPost ↗
2026-09-12 16:09Global resetAll usersQuality issues after the Astra launch47d 14h agoPost ↗
2026-09-08 09:56Global resetAll usersAstra launch51d 20h agoPost ↗
2026-09-05 08:39Reset cardNot specifiedAstra rolled out early54d 21h agoPost ↗
2026-09-04 07:12Reset cardPaid users without Astra accessNo Astra access yet55d 23h agoPost ↗
2026-08-31 10:29Scoped resetPaid users25M active users59d 19h agoPost ↗
2026-08-30 04:43Scoped resetPaid usersUsage-limit issues61d 1h agoPost ↗
2026-08-28 00:35Global resetAll usersNot specified in this record63d 5h agoPost ↗
2026-08-24 08:46Reset (scope unspecified)Not specifiedUsage issues66d 21h agoPost ↗
2026-08-21 19:43Reset cardPaid users20M active users69d 10h agoPost ↗
2026-08-13 09:01Global resetAll users15M users77d 21h agoPost ↗
2026-08-11 08:27Reset (scope unspecified)Not specifiedNot specified in this record79d 21h agoPost ↗
2026-08-09 04:29Scoped resetPaid usersGPT-5.6 Sol available everywhere82d 1h agoPost ↗
2026-08-01 11:32Global resetAll usersCelebrating an efficient week89d 18h agoPost ↗
2026-07-29 12:09Global resetAll usersSol usage draining too fast92d 18h agoPost ↗
Latest Event
Reset card
37d 5h ago
Scope: Paid users
Event Time (UTC+8)
2026-09-23 00:31
Reason: Opus 5.5 launch
Source post ↗
Historical Cadence Reference
2026-09-09 23:20
Reference point passed 50d 7h ago
Based on 9 global reset intervals; not an official schedule
Median Global Gap
7.9 days
Loaded past 30 days: 0 resets, 0 cards
Source: WhenReset.dev · Records may be partial
⏳

Five-Hour Window Calculator

Enter a known window start, not the moment you hit the limit. Computes an assumed 5-hour window end only; refer to your product client for real account recovery.

Assumed window end (UTC+8)
—
Enter a known start, then select Calculate.

Claude Reset & Card Records

Up to 30 loaded records · UTC+8
Date (UTC+8)TypeScopeReason / ContextAgoSource
2026-09-23 00:31Reset cardPaid usersOpus 5.5 launch37d 5h agoPost ↗
2026-09-05 04:08Scoped resetMax plansResponse to Astra launch; official wording is the long weekend55d 2h agoPost ↗
2026-09-02 02:35Global resetAll usersFable 5.1 launch58d 3h agoPost ↗
2026-07-16 11:58Global resetAll usersNot specified in this record105d 18h agoPost ↗
2026-07-10 02:01Global resetAll usersNot specified in this record112d 4h agoPost ↗
2026-07-02 05:16Global resetAll usersFable 5 back120d 1h agoPost ↗
2026-06-20 08:05Global resetAll usersweekend131d 22h agoPost ↗
2026-06-19 10:50Scoped resetPro and Max users with incorrect limitsWrong weekly limit shown132d 19h agoPost ↗
2026-06-13 10:24Global resetAll usersNot specified in this record138d 19h agoPost ↗
2026-06-10 05:48Global resetAll usersFable 5 launch142d 0h agoPost ↗
2026-06-02 01:35Scoped resetPaid usersExcess subagents burned usage150d 4h agoPost ↗
2026-05-16 02:00Global resetAll usersweekend167d 4h agoPost ↗
2026-04-24 01:44Global resetAll usersClaude Code quality issues189d 4h agoPost ↗
2026-04-17 04:02Global resetAll usersOpus 4.7 long-context limit calculation issue196d 2h agoPost ↗
Latest Event
Global reset
27d 4h ago
Scope: All users
Event Time (UTC+8)
2026-10-03 02:05
Reason: Not specified in this record
Source post ↗
Historical Cadence Reference
2026-10-13 03:15
Reference point passed 17d 3h ago
Based on 6 global reset intervals; not an official schedule
Median Global Gap
10 days
Loaded past 30 days: 1 resets, 0 cards
Source: WhenReset.dev · Records may be partial
⏳

Five-Hour Window Calculator

Enter a known window start, not the moment you hit the limit. Computes an assumed 5-hour window end only; refer to your product client for real account recovery.

Assumed window end (UTC+8)
—
Enter a known start, then select Calculate.

Grok Reset & Card Records

Up to 30 loaded records · UTC+8
Date (UTC+8)TypeScopeReason / ContextAgoSource
2026-10-03 02:05Global resetAll usersNot specified in this record27d 4h agoPost ↗
2026-09-06 02:24Global resetAll usersNot specified in this record54d 3h agoPost ↗
2026-09-01 23:45Global resetAll usersNot specified in this record58d 6h agoPost ↗
2026-08-27 01:23Global resetAll usersThe post also announces Bot access for SuperGrok and Cursor Pro subscribers64d 4h agoPost ↗
2026-08-14 01:49Global resetAll usersGrok 4.6 launch77d 4h agoPost ↗
2026-07-16 06:58Reset (scope unspecified)Not specifiedGrok Build open-sourced105d 23h agoPost ↗
2026-07-16 04:44Global resetAll usersGrok Build open-sourced106d 1h agoPost ↗
2026-07-09 01:57Global resetAll usersGrok 4.5 launch113d 4h agoPost ↗
Quota Planning Tool

Weekly Quota Planner Calculator

Enter your percentage used and next reset time to estimate pacing, exhaustion risks, and recommended daily quota budgets.

%
Pace Verdict
Evaluating...
Estimated from current burn rate
Projected Total Usage
—
At your current pace until reset
Daily Budget Recommendation
—
Remaining quota distributed daily
Time Remaining
—
Until scheduled reset
💡

Calculating usage pacing and recommended daily budgets from your input...

Subscriptions & Multi-Channel Feeds

Reset Alerts & Automation Feeds

Subscribe via standard RSS 2.0, connect custom Webhooks for team bots, or enable instant browser desktop notifications.

📡

Real-Time RSS Feed

Standard RSS 2.0

Subscribe in NetNewsWire, Feedly, Follow, or your favorite reader to receive global reset and card announcements automatically.

🤖

Feishu & Webhook Bot Alerts

Automated Bot Alerts

Poll our public /api/reset/data endpoint via GitHub Actions to deliver live reset alerts to Slack, Discord, or Feishu groups.

🔔

Browser Desktop Alerts

Zero Installation

Enable system-level desktop notifications on this device. While this tab remains active in background, alerts pop up upon new resets.

Quota Rules & Frequently Asked Questions

What is the difference between global resets, scoped resets, and reset cards?

Only records explicitly scoped to all users are designated as global resets. Other resets retain their documented scope (such as paid, affected, or max plans). Reset card entries record bonus issuance events and do not imply an automatic reset for all accounts. Eligibility and expiry details can be found in the linked source post. None of these records establish your individual remaining quota.

Can my quota recovery time be computed from when I hit the limit?

No. The moment you hit the limit does not equal the window start. The calculator only adds 5 hours to your known window start, showing the assumed window end. Different products and tiers may have varying limits; always consult the time and quota shown directly inside the product.

How is the historical interval reference point calculated?

From loaded records, the median gap between up to 10 distinct global reset timestamps is computed and added to the latest global reset time. Reset cards and scoped resets are excluded. If fewer than two global resets are loaded, no reference point is displayed. This is purely a historical arithmetic point, not an official schedule.

Where do records for Codex, Claude, and Grok come from?

T Salon queries the WhenReset.dev records API upon page request with a 5-minute cache. Records link directly to original posts by official teams and technical leads. When unreachable, the page indicates temporary unavailability.

How does the weekly quota planner calculator work?

Enter your current percentage used and your next personal reset time as shown in your product client. The calculator estimates your hourly burn pace, remaining time until reset, and recommended daily quota budget. All calculations run client-side with data stored only in local storage.