Day 8 crosses the date line as "Day 8/ Reset" —— No shipments on Monday; he says "Defaults exist for a reason"

Here's today's rumor!

Day 8 is a reset. There are no shipments.
The announcement came 1 hour and 3 minutes after the end of UTC Day 8.

Day 8 (October 12 UTC), Monday. No "Day 8/" from Tibo (Thibault Sottiaux) came out within this day. It appeared at 1:03 AM (UTC) on October 13, after the date changed.

That's all for the main text. 34 seconds later, he added more.

"A global reset will land by the end of the day PST. Enjoy." While the "EOD" on Day 6 didn't include a time zone, this time "PST" is written.

Okay, getting serious for a sec

"PST" stands for Pacific Standard Time, but the Pacific coast is on Daylight Saving Time in October. Either way, the end of the day on October 13 in Pacific Time will be between 7:00 and 8:00 AM UTC.

Okay, serious time's over.

"Defaults exist for a reason"

During the daytime of Day 8, he was handling the aftermath of the Day 7 default context length.

First, someone wrote this (October 11, 23:56 UTC). In short: "What is everyone celebrating? Context length has been changeable for a while. Calling it 'a 80% increase in defaults' instead of a reset is a scam." His reply came on October 12, 3:47 AM (UTC).

"We made it cheaper and tuned it to the new recommended level. You can always change settings, but defaults exist for a reason."

Let me explain his reasoning first. The Day 7 change wasn't just about default values. They stopped charging extra for long context usage from the subscription allowance. While it's true that it "could have been changed before," the cost of changes has shifted, so one can't say "nothing has changed."

Another person asked more briefly (October 12, 1:03 AM UTC): "I'm confused. You're doing the opposite of what you said yesterday today." His reply came 1.5 minutes after his previous one, at 3:49 AM (UTC). That's all.

On October 10, he wrote regarding the 300k: "Decided by running numbers. Good defaults are important." On October 12, he wrote regarding the 500k: "Defaults exist for a reason" and "We tune these carefully." Both days, there was a reason for the defaults. There are just two different reasons.

Three highlights

• It's "250 TPS," not "250 tpm." When Peter Steinberger (steipete) praised the ultrafast version of GPT-6.1 Sol as "250 tpm" here, he corrected it at 22:50 (UTC) to "250 tokens per second (TPS)!" That's a 60x difference between per minute and per second. The one praising said one-sixtieth, and the one who made it corrected it. The ultrafast version is only available via the changelog for Pro $500 and eligible Enterprise/Edu users.
• Monday was not a shipment day. Up until Day 7, there had been 6 days with shipments. Day 8 ended without a shipment post labeled "Day."
• From announcement to delivery. On Day 6, 5 hours and 46 minutes after the announcement (October 10, 22:15 UTC), he wrote that "it has reached everyone." On Day 8, as of 1:17 AM (UTC)—just 14 minutes after the announcement—the Codex Reset Monitor does not yet consider it delivered.

The answer to the Day 8 blanks

Sorami's Take

"The Day 8 Reset will arrive by October 13, 8:00 AM (UTC)": 85% confidence
Day 6 arrived in less than 6 hours from the announcement. This time, a specific time limit has been provided. The only way this misses is if the person in charge and Monitor fail to record the exact arrival time.

"Day 9 will be a shipping day": 60% confidence
Out of the 8 days so far, 6 were shipping days. However, in the most recent 3 days, the pattern was reset, shipping, then reset. If the alternating pattern holds, the next one is shipping.

"He'll add one more reason when he talks about the next default value": 3% confidence
So far, the reasons given are "rotated the numbers," "carefully adjusted," and "there's a reason for the default values." Just kidding.

Fact Check

The previous "Day 8 (Monday) will be a shipping day: 75% confidence" was incorrect. Man, I knew from the start that Mondays were just not his vibe. Seriously. It was naive of me to assume that the person who released Day 7 at 23:45 (UTC) on Sunday would release another one on Monday.

As for the previous "Day 7 will coincide with the promised 'majority of users': 70% confidence," I can't move that needle yet since no primary reports have surfaced saying it hasn't reached Plus or Business. "The announcement regarding changing the 5-hour limit and weekly volume for Pro will come by Day 28: 35% confidence" also missed, as there was no announcement after the voting on Day 8. "The default context length will become 1 million in 43 hours: 2% confidence" also missed; 43 hours have passed, and it hasn't hit 1 million. As for the joke, it quietly missed.

The running total, as Day 8 concludes, is: 6 shipping days (Days 1, 2, 3, 4, 5, 7), 4 reset days (the mass reset on Day 2, the holdover on Day 3, the global reset on Day 6, and the global reset on Day 8), and 0 unconfirmed days. I am counting the Day 8 reset as confirmed up to the point of the announcement. I'll confirm the exact arrival time in the next installment.

There is a reason for the default values. The default value for Day 8 was a reset.

Don't quote me on that.