Resets per month
- 1
- 2
- 4
- 6
- 6
- 3
- 5
- 12
- 10
- 8
- 5
Global Codex reset and history
Latest confirmed reset
Next reset (estimate)
Based on the median of 61 observed gaps (3 days). Not a fixed date.
- Documented events
- 62
- Median gap between resets
- 3 days
- Shortest to longest gap
- 0.2 to 67.7 days
Development over time
Time between resets
July 29, 2026 at 04:09 AM UTC: 1 dayAugust 1, 2026 at 03:32 AM UTC: 3 daysAugust 8, 2026 at 08:29 PM UTC: 7.7 daysAugust 11, 2026 at 12:27 AM UTC: 2.2 daysAugust 13, 2026 at 01:01 AM UTC: 2 daysAugust 21, 2026 at 11:43 AM UTC: 8.4 daysAugust 24, 2026 at 12:46 AM UTC: 2.5 daysAugust 25, 2026 at 06:00 PM UTC: 1.7 daysAugust 27, 2026 at 04:35 PM UTC: 1.9 daysAugust 29, 2026 at 08:43 PM UTC: 2.2 daysAugust 31, 2026 at 02:34 AM UTC: 1.2 daysSeptember 3, 2026 at 11:12 PM UTC: 3.9 daysSeptember 5, 2026 at 12:39 AM UTC: 1.1 daysSeptember 7, 2026 at 07:24 PM UTC: 2.8 daysSeptember 8, 2026 at 04:05 AM UTC: 0.4 daysSeptember 12, 2026 at 08:09 AM UTC: 4.2 daysSeptember 22, 2026 at 06:23 PM UTC: 10.4 daysSeptember 26, 2026 at 12:07 AM UTC: 3.2 daysSeptember 26, 2026 at 06:17 PM UTC: 0.8 daysOctober 2, 2026 at 09:18 PM UTC: 6.1 daysOctober 7, 2026 at 03:35 AM UTC: 4.3 daysOctober 8, 2026 at 03:44 AM UTC: 1 dayOctober 10, 2026 at 10:16 PM UTC: 2.8 daysOctober 11, 2026 at 04:01 AM UTC: 0.2 days
Why resets happened
- Incident15
- Compensation2
- Milestone7
- Launch6
- Promotion3
- Banked reset7
- No reason stated22
Source agreement
- 2 of 4 sources14
- 3 of 4 sources47
- 4 of 4 sources1
Individual resets explained
Open an event to see its publicly stated reason and source coverage. If no clear reason is available, that is stated explicitly.
No reason stated3 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 3 of the 4 monitored sources.
No reason stated2 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 2 of the 4 monitored sources.
No reason stated2 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 2 of the 4 monitored sources.
No reason stated3 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Incident3 of 4 sources
Why this reset?
The public record links this reset to a technical incident, recovery, or an ongoing investigation.
Source coverage
This event is listed by 3 of the 4 monitored sources.
No reason stated3 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 3 of the 4 monitored sources.
No reason stated2 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 2 of the 4 monitored sources.
Banked reset2 of 4 sources
Why this reset?
This was a banked reset that could be redeemed separately from the account.
Source coverage
This event is listed by 2 of the 4 monitored sources.
No reason stated4 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 4 of the 4 monitored sources.
No reason stated2 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 2 of the 4 monitored sources.
No reason stated2 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 2 of the 4 monitored sources.
Banked reset2 of 4 sources
Why this reset?
This was a banked reset that could be redeemed separately from the account.
Source coverage
This event is listed by 2 of the 4 monitored sources.
Banked reset2 of 4 sources
Why this reset?
This was a banked reset that could be redeemed separately from the account.
Source coverage
This event is listed by 2 of the 4 monitored sources.
Milestone2 of 4 sources
Why this reset?
The reset was granted for a publicly stated user or growth milestone.
Source coverage
This event is listed by 2 of the 4 monitored sources.
No reason stated3 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 3 of the 4 monitored sources.
No reason stated3 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 3 of the 4 monitored sources.
No reason stated2 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 2 of the 4 monitored sources.
Incident3 of 4 sources
Why this reset?
The public record links this reset to a technical incident, recovery, or an ongoing investigation.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Banked reset2 of 4 sources
Why this reset?
This was a banked reset that could be redeemed separately from the account.
Source coverage
This event is listed by 2 of the 4 monitored sources.
Milestone3 of 4 sources
Why this reset?
The reset was granted for a publicly stated user or growth milestone.
Source coverage
This event is listed by 3 of the 4 monitored sources.
No reason stated2 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 2 of the 4 monitored sources.
Launch3 of 4 sources
Why this reset?
The reset accompanied a model, product, or feature launch.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Launch3 of 4 sources
Why this reset?
The reset accompanied a model, product, or feature launch.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Launch3 of 4 sources
Why this reset?
The reset accompanied a model, product, or feature launch.
Source coverage
This event is listed by 3 of the 4 monitored sources.
No reason stated3 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Incident3 of 4 sources
Why this reset?
The public record links this reset to a technical incident, recovery, or an ongoing investigation.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Milestone3 of 4 sources
Why this reset?
The reset was granted for a publicly stated user or growth milestone.
Source coverage
This event is listed by 3 of the 4 monitored sources.
No reason stated3 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Milestone3 of 4 sources
Why this reset?
The reset was granted for a publicly stated user or growth milestone.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Milestone3 of 4 sources
Why this reset?
The reset was granted for a publicly stated user or growth milestone.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Banked reset2 of 4 sources
Why this reset?
This was a banked reset that could be redeemed separately from the account.
Source coverage
This event is listed by 2 of the 4 monitored sources.
Banked reset2 of 4 sources
Why this reset?
This was a banked reset that could be redeemed separately from the account.
Source coverage
This event is listed by 2 of the 4 monitored sources.
Promotion3 of 4 sources
Why this reset?
The reset was announced as a bonus, celebration, or limited-time promotion.
Source coverage
This event is listed by 3 of the 4 monitored sources.
No reason stated3 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 3 of the 4 monitored sources.
No reason stated3 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Banked reset3 of 4 sources
Why this reset?
This was a banked reset that could be redeemed separately from the account.
Source coverage
This event is listed by 3 of the 4 monitored sources.
No reason stated3 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Incident3 of 4 sources
Why this reset?
The public record links this reset to a technical incident, recovery, or an ongoing investigation.
Source coverage
This event is listed by 3 of the 4 monitored sources.
No reason stated3 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Incident3 of 4 sources
Why this reset?
The public record links this reset to a technical incident, recovery, or an ongoing investigation.
Source coverage
This event is listed by 3 of the 4 monitored sources.
No reason stated3 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Incident3 of 4 sources
Why this reset?
The public record links this reset to a technical incident, recovery, or an ongoing investigation.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Promotion3 of 4 sources
Why this reset?
The reset was announced as a bonus, celebration, or limited-time promotion.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Launch3 of 4 sources
Why this reset?
The reset accompanied a model, product, or feature launch.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Incident3 of 4 sources
Why this reset?
The public record links this reset to a technical incident, recovery, or an ongoing investigation.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Milestone3 of 4 sources
Why this reset?
The reset was granted for a publicly stated user or growth milestone.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Launch3 of 4 sources
Why this reset?
The reset accompanied a model, product, or feature launch.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Milestone3 of 4 sources
Why this reset?
The reset was granted for a publicly stated user or growth milestone.
Source coverage
This event is listed by 3 of the 4 monitored sources.
No reason stated3 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Launch3 of 4 sources
Why this reset?
The reset accompanied a model, product, or feature launch.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Incident3 of 4 sources
Why this reset?
The public record links this reset to a technical incident, recovery, or an ongoing investigation.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Incident3 of 4 sources
Why this reset?
The public record links this reset to a technical incident, recovery, or an ongoing investigation.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Incident3 of 4 sources
Why this reset?
The public record links this reset to a technical incident, recovery, or an ongoing investigation.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Incident3 of 4 sources
Why this reset?
The public record links this reset to a technical incident, recovery, or an ongoing investigation.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Incident3 of 4 sources
Why this reset?
The public record links this reset to a technical incident, recovery, or an ongoing investigation.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Promotion3 of 4 sources
Why this reset?
The reset was announced as a bonus, celebration, or limited-time promotion.
Source coverage
This event is listed by 3 of the 4 monitored sources.
No reason stated3 of 4 sources
Why this reset?
The evaluated public data does not state a clear reason for this event, so no reason is inferred.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Compensation3 of 4 sources
Why this reset?
The reset was announced as compensation for disrupted or unusually fast-consumed usage.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Incident3 of 4 sources
Why this reset?
The public record links this reset to a technical incident, recovery, or an ongoing investigation.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Compensation3 of 4 sources
Why this reset?
The reset was announced as compensation for disrupted or unusually fast-consumed usage.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Incident3 of 4 sources
Why this reset?
The public record links this reset to a technical incident, recovery, or an ongoing investigation.
Source coverage
This event is listed by 3 of the 4 monitored sources.
Incident3 of 4 sources
Why this reset?
The public record links this reset to a technical incident, recovery, or an ongoing investigation.
Source coverage
This event is listed by 3 of the 4 monitored sources.