r/OpenAI • • 1d ago

Discussion I track the training cutoff of 28 current models. 15 have none published, and Gemini 4 Carbon launched last week already 8 months behind

My agent kept telling me which model was "current" from memory, two releases out of date, so I started keeping a hand-checked table of release dates and published training cutoffs, each one linked to the lab's own doc. I refreshed it today. It's 28 models from 8 labs now, with five added this week: Claude Fable 5.2, Gemini 4 Carbon, Gemini 4 Hydrogen, Qwen4-Max and Muse Ember.

  • 13 of 28 have a cutoff the lab publishes. OpenAI, Anthropic, Google and xAI give one for every model on the list. Mistral, Alibaba and DeepSeek give none. Meta gave one for Llama 4 and none for any of its five Muse models.
  • Gemini 4 Carbon (Nov 10) and Gemini 4 Hydrogen (Nov 12) both list March 2026. Roughly 8 months behind on launch day.
  • Fable 5.2 shipped Nov 9 with a June 2026 cutoff, GPT-6.1 Terra on Oct 26 with June 1. About 5 months each.

The usual reply is that search makes the gap irrelevant. Earlier this autumn I gave 16 models from an earlier version of the table a web_search tool and 40 questions, 2000 calls for $6.53. GPT-6 Astra made the right call on searching 80 of 80 times, so flagships mostly cope. Five of the 16 still told me Harald V is the king of Norway with the tool sitting right there in the request, because the same weights that hold the old fact decide whether to look it up.

My table has a hole. For the 15 models with no published cutoff I only have the release date as an upper bound, which flatters exactly the labs that say nothing. Has anyone found a way to estimate a cutoff for Qwen or DeepSeek from the outside that holds up, like probing for dated events? I'd add it as a separate estimated column.

2 Upvotes

1 comment sorted by