Day 15/ Nevermind, we're still cooking... and reset. Enjoy.
Tibo@thsottiaux
Day 15/ We're cookedView this post on X ↗
Here’s what we’re cooking with Codex: https://t.co/EHSalmUTN0View this post on X ↗
Tibo reset monitor
Codex quota resets and reset cards: timing, eligibility and Tibo’s original posts.
No new pending announcement in collected records
Codex Usage reset · Source confirmed
- Eligibility：Not specified in the source
No announcement does not mean no future reset. Passing a scheduled window never confirms an event.
Latest from Tibo · @theo I demand a reset
Tibo@thsottiaux
@theo I demand a reset
T3 Connect has not been reliable today. Super sorry about that. Should be recovered now 🤞 Nerdy deets below for those who care: T3 Connect is our built-in alternative to Tailscale for remote connections on T3 Code. Turns out there's so many T3 Connect users that we are hitting some rate limits on Cloudflare's side! They have confirmed the issues on their end and are working on fixes. We were unaware of these limits (seems like they were too). We're well under the limits we knew about, specifically the # of tunnels we can deploy to our users. The alerting on these failures was also pretty rough. CF has confirmed all of this and is working on fixes on their end 🙏 Crazy to have a product so popular that it's taking down CloudFlare lol. We are working hard to prevent these types of regressions going forward. This work is full of fun challenges. Once a thundering herd starts, we're a bit screwed since we can't control the code you're running on your end! We have to plan way in advance for changes because we can't guarantee that users are on the latest version at any given time. Thanks for sticking through with us in the interim. If you want to maximize your uptime and minimize chances of connection loss like today, I will not be disappointed if you set up Tailscale as a fallback (I do this personally)View this post on X ↗
- Reset events · 90 days
- 11 events
- Banked events · 90 days
- 3 events
- Median confirmation gap
- 10.1 days
- Latest reset confirmation
Counts recognized events. Announcements and confirmations are grouped; discussion is excluded. Counts do not establish individual account resets.
Event calendar
Choose a date for resets, banked resets and original posts.
2006 / 02
This month 0 collected eventsThis month ↗
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 |
- Source confirmed
- Estimate passed; unconfirmed
- Announced
History months
2/13
2006Entire monthSelected 2006-02-13: 0 records.
No records for this day
No reset or reset-card records have been collected for this date. Choose a labelled day to view its records.
Recent record · 2026-10-20 →How is timing estimated?Sources and rules
Start with the original words.“Next hour” starts at publication. Explicit clock times use their stated time zone; PST and PDT use their corresponding offsets. Missing zones use an explicitly labelled Pacific-local assumption. Estimates add a separate 1–2 hour allowance.
Missing times get a reference window.The reference is 16:30–21:30 Pacific, adjusted for daylight saving time. We count confirmation-post timestamps; these do not establish when a reset button was pressed.
Of 9 collected confirmation timestamps in 90 days, 5 fall in that window.
Source facts and estimates stay separate.Only explicit confirmation posts are source-confirmed. Six hours after an estimated window, a record may say “likely completed (estimate)”; it remains unconfirmed. Banked resets do not restore usage by themselves. Posting time is not delivery time.
Public posts are checked continuously.New posts every 1.0 hours; relevant older sources every 6.0 hours. Messages publish automatically and may be withdrawn by an operator. Check your own quota and banked balance in Codex.
Earliest collected record ·
Coverage is limited to accessible sources successfully read by this monitor, not a complete historical archive. Manual evidence is labelled separately.