A date that can only get later
Here the published dates are described as the earliest on which a model might be retired. That makes each one a floor: access will not end before it and may end well after, with nothing published when the day passes uneventfully. The register keeps the wording verbatim for that reason. As of 2026-09-22.
| What the page is asked | What Gemini API publishes | What that leaves open |
|---|---|---|
| Can the date be pushed back | Yes, it is stated as the earliest possible | Moving later requires no correction |
| Can access end before it | Nothing published suggests it can | The date is the floor, not the ceiling |
| Is the notice quantified | Advance notice promised, no figure given | So the real runway is not calculable |
| What a passed date means | Possibly nothing at all | A model may simply keep answering |
Inclusion rule. A cell is filled from a published sentence about access ending other than on a stated date. A reader's estimate of how fast a menu could change does not fill one. Order. Which direction the date can move first, then what that leaves unknown.
1A floor and a deadline produce different plans
Read as a deadline, the date says finish the migration by then. Read as published, it says have the migration ready by then and expect to hold it. The second plan wastes less and requires admitting the date is soft.
Teams that treat a floor as a deadline spend urgency they did not need. Teams that ignore the date because it is soft discover it was real. Neither reading is safe on its own, which is why the wording matters more than the number.
2Nothing marks the day a floor turns out to be soft
If a model keeps answering past its listed date, no correction is published and the row may simply remain. So a reader cannot tell whether a date has slipped or whether their own check was wrong.
That is the cost of the phrasing. It makes every row honest and makes the table unusable as a record of what actually happened, which is a gap the calendar here can only partly close.
3An unquantified notice removes the other way in
If the period were stated in days, a production could ignore the floor and plan from the warning instead. The promise here is made in words, so neither the date nor the notice yields a runway.
Both halves are recorded in the notice reading for this entry. The combination is the reason it publishes more dates than anybody else and commits to less.
- What a date in that table commits toThe shutdown dates listed indicate the earliest possible dates on which a model might be retired
- How many days of advance noticeNo date announced (as of 2026-09-12)promised but never counted
4Sources
Read from the deprecations page on ai.google.dev, 2026-09-22. The whole entry is on Gemini API, and the column it sits in is on Ending early. Same column, other entries: LTX Studio, Runway.