How to read the history
Each record includes its type, announcement or first-observation time, source and verification context. Times follow the selected timezone while stored values remain UTC.
An announcement timestamp may differ from the moment an individual account updates. Propagation can take time, so the record preserves its time basis.
Full Resets
A Full Reset enters completed history only when the source describes usage as restored or propagating broadly. Future-facing language remains an announcement.
A broad reset statement still may not prove that every plan, region or usage window changed at exactly the same moment.
Banked Resets
Banked Reset events are stored separately from immediate Full Resets. The timeline keeps eligibility and source context whenever available.
Whether a user receives a credit, when it expires and where it can be redeemed are account-specific questions answered by Usage and the original source.
Interval statistics
Lifetime average, recent-ten average and longest wait are calculated from completed regular reset records. Banked events, duplicate sources, future timestamps and unknown types are excluded.
Because a few long gaps can distort an average, AIReset also uses P25, P75 and recent pace. These describe history rather than create a countdown.
Data boundaries
The archive is cross-checked against public sources. Source links preserve the original text; Chinese views use curated historical translations or model-generated summaries when configured.
Unverified rumors are not promoted into completed history. Public archives can still be incomplete, so the original source and account interface remain decisive.