The method
Every number needs a little context.
Public announcements, readable history, and clear limits on what we know.
Full reset
A provider restores usage limits for a stated group. Not necessarily every account, plan or model.
Banked credit
A reset granted for later redemption. It does not necessarily refill usage immediately.
Boost / change
A temporary multiplier, policy update or capacity change. Kept out of full-reset interval statistics.
Sources and evidence
Verified: a named primary source with the announcement, timestamp and receipt. Verification proves what was said, not whether your account received it.
Reported: secondary records without our own primary receipt. Historical dashboard records can include these, with source labels.
Sample: illustrative archive entries. Excluded from reset metrics, forecasts and alerts.
Read the original sources →Statistics you can compare
Dashboard totals use the current calendar year in UTC. Full-reset announcements within 12 hours are merged. Average and longest waits use only gaps between those full resets.
Banked credits, boosts and policy changes have separate counts. Missing historical records can affect all statistics. No events in our record does not mean no resets happened.
Forecasts use a separate historical model window, show sample sizes and backtest errors, and remain experimental.
How alerts reach you
Reviewed, verified reset announcements are published in the site's public feed. A scheduled Cloudflare Worker checks that feed every 15 minutes and queues matching alerts.
Email requires confirmation. You choose providers and reset types. Delivery retries are tracked; duplicate event/subscriber pairs are not queued again. Unsubscribing stops future sends.
Alerts depend on source review and mail delivery. We do not promise instant detection or a reset for your own plan. Forecasts, samples and rumors never trigger email.
Choose your alerts →Where data lives
Public history, evidence and model inputs live in GitHub and are served by Cloudflare Pages.
Private subscriptions and delivery records live in Cloudflare D1. Email addresses and browser subscription keys never go into GitHub. “Please reset” wishes are saved only in your browser.
Privacy and retention →Provider policy reality check
Gemini: Google documents daily Code Assist and Gemini CLI quotas, including 1,500 requests per user per day for Standard and 2,000 for Enterprise. That proves quota replenishment exists; it does not prove discretionary “reset” announcements. Google quota docs ↗
Cursor: Cursor documents two monthly usage pools and says included usage resets with the billing cycle. This tracker does not treat Cursor as having a public goodwill-reset ritual. Cursor usage docs ↗
xAI / SpaceX: A corporate relationship or acquisition claim does not merge Grok and Cursor histories. Events stay attached to the product whose limits the source names.