LLMSwaps

Which model each app runs today, and when it last changed

The preview lines that have already gone

Two preview identifiers in this family carry a shutdown date that has already passed, and no entry in the register names them today. This is the only completed retirement here besides the one consumer product closure, and it shows what a finished one looks like from outside. As of 2026-09-22.

What remains readable about a line that has already been switched off. Recorded 2026-09-22.
EntryHow it appears thereAnnounced end for this line
Gemini APITwo preview identifiers, listed with a past shutdown date12 November 2025, already passed
Every application trackedNot named on any public pageNo date announced

Inclusion rule. An entry appears when it names this line on a page a reader can reach without an account, or when it publishes a lifecycle date for it. Absence is recorded as a row. Order. The entry publishing the date first, then the applications as one row.

1A finished retirement leaves a dated row and nothing else

The identifiers are gone and the row is still there, which is the useful half. A reader can confirm that the line existed, that it had a date, and that the date has passed, all from one page.

Nothing else survives. No application names these strings, no successor is recorded beside them, and nothing says what happened to callers who had not moved. That is the ordinary aftermath rather than a failure of this maker's documentation.

What a finished retirement leaves behindThe identifiers are gone and the dated row remains, so a reader can confirm the line existed, that it had a date and that the date has passed. No successor is recorded beside it and no application names it now.A retirement that has already completedA dated rowappearsListedTwo previewidentifiers,with a dateahead of them.Shutdown12 November2025The earlierdate in thisfamily,matching thepreview stage.Row remains,line goneNowNo applicationnames it. Nosuccessorrecorded.The stage was encoded in the identifier string, not published as a state
Fig. 1 One completed case is not a pattern; it is the only evidence available about how these endings actually finish.

2Preview lines carried the earlier date

These identifiers were retired before the released ones in the same generation, which matches the platform policies elsewhere in this register: a preview stage buys less notice. Here the stage is encoded in the identifier string rather than published as a state.

So a team that built during a preview period was on the shorter runway without any page grouping the two as one decision. The register records that as a naming convention doing a state system's work.

3Why a completed retirement belongs in a register of announcements

Most of this site records dates that have not arrived. Keeping one that has is what lets a reader calibrate the others: it shows the wording, the interval and the absence of a successor as they actually resolved.

One completed case is not a pattern. It is the only evidence available about how these endings finish, alongside the consumer closure the calendar also records.

  • veo-3.0-generate-preview and veo-3.0-fast-generate-preview
    12 November 2025shutdown dateGoogle, Gemini deprecations / recorded 2026-09-22
  • What a date in that table commits to
    The shutdown dates listed indicate the earliest possible dates on which a model might be retiredGoogle, Gemini deprecations / recorded 2026-09-22
  • How many days of advance notice
    No date announced (as of 2026-09-12)promised but never countedGoogle, Gemini deprecations / recorded 2026-09-22

4Sources

Each row is read from the page that entry publishes itself, 2026-09-22, and any date comes from whoever makes the model. Every announced date is on the calendar. Other models read this way: Kling 3.0, Kling 2.5 Turbo.