What is the difference between deprecation and retirement?

Deprecation (or, on Amazon Bedrock, the Legacy state) means a model is still callable but is scheduled to go away: the vendor has flagged it, usually named a recommended replacement, and set a date. Retirement - called shutdown by OpenAI and the Gemini API, retired by Anthropic and Vertex AI, and EOL by Amazon Bedrock - is the date the model stops working. Before that date, existing code keeps running; after it, calls fail.

How do vendors announce model deprecations?

The notice periods differ. Anthropic provides at least 60 days notice before retirement for publicly released models. OpenAI gives at least 6 months for generally available models, at least 3 months for specialized variants, and as little as about 2 weeks for preview models. The Gemini API gives at least 2 weeks for preview and latest aliases and treats its table dates as the earliest possible shutdown. Amazon Bedrock keeps a model at least 12 months on the platform and at least 6 months in the Legacy state before EOL. Vendors notify affected customers by email and update their documentation; larger changes are also announced on blogs.

What happens to API calls to a retired model?

They fail. Anthropic states that requests to retired models will fail. Amazon Bedrock states that after EOL requests made to this version will fail. The Gemini API states that a shut-down model is completely turned off, and the endpoint is no longer available. OpenAI states that a shut-down model or endpoint will no longer be accessible. Migration does not happen automatically - you must update your application code to a supported model before the date.

How should I plan a model migration?

Find your model's row for the specific platform you call, because the same model can have different dates on different platforms. Note the retirement, shutdown, or EOL date and the vendor's recommended replacement, test the replacement, and switch before the date. Step-by-step migration mechanics for Claude models are covered in the Anthropic Claude Model Migration Guide, and the LLM Token Counter and Context Budget Planner can help estimate context and token budgets for a candidate replacement.

AI Model Deprecation and Lifecycle Calendar - Anthropic, OpenAI, Google, and Amazon Bedrock

First Published: 2026-07-05
Last Updated: 2026-07-05

This page is a single, cross-vendor calendar of announced deprecation, retirement, shutdown, and end-of-life (EOL) dates for AI models on the four platforms most teams run in production: the Anthropic API, OpenAI, Google (the Gemini API and Vertex AI), and Amazon Bedrock. Model end-of-life is a recurring operational event for every AI team, yet each vendor publishes its schedule on a different page and defines the terms differently. The goal here is to keep those official facts in one place and to translate each vendor's vocabulary into a common frame.

The First Published and Last Updated dates shown above indicate the currency of this page. Companion references on hidekazu-konishi.com:

Overview

This page collects, in one view, the model lifecycle information that each vendor publishes on its own official documentation:

Anthropic — the Model deprecations page and the Models overview for the Anthropic API (also offered as Claude Platform on AWS and Microsoft Foundry).
OpenAI — the Deprecations page and the Models page.
Google — the Gemini API deprecations page (Google AI for Developers) and the Vertex AI model-versioning and deprecations pages (Google Cloud).
Amazon Bedrock — the Model lifecycle page in the Amazon Bedrock User Guide.

This page is reviewed and updated quarterly, and whenever major deprecations are announced. Because model lifecycle dates change — vendors add rows, adjust dates, and retire models — always confirm the current dates on the official pages linked in each section before you act.

The scope of this first edition is limited to the four platforms above and to dates that are officially published. I do not include unannounced or speculated dates, pricing, or performance comparisons. Migration mechanics (how to move code from one model to another) are covered in the dedicated Anthropic Claude Model Migration Guide; this page is about when a model changes state and what the vendor lists as its replacement.

How to Read This Page

Lifecycle terminology differs by vendor

Every vendor uses slightly different words for the same two ideas: "still usable but scheduled to go away" and "no longer usable." The table below maps each vendor's official terms onto that common frame. The definitions are quoted from each vendor's official documentation.

Concept	Anthropic	OpenAI	Google Gemini API	Google Vertex AI	Amazon Bedrock
Still callable, scheduled to end	Deprecated ("still functional but no longer recommended"; a recommended replacement and retirement date are assigned). Also Legacy ("will no longer receive updates and may be deprecated in the future").	Deprecation ("the process of retiring a model or endpoint"; becomes deprecated immediately when announced). Legacy models "no longer receive updates."	No separate "deprecated" state; a model is scheduled with a shutdown date. Stability labels: stable, preview, experimental, latest.	Latest stable vs legacy stable (an older, still-supported stable version).	Legacy ("in the Legacy state for at least 6 months before the EOL date"; new customers cannot use it).
No longer callable	Retired ("no longer available for use. Requests to retired models will fail").	Shutdown / Sunset ("completely turned off"; "will no longer be accessible").	Shutdown ("completely turned off, and the endpoint is no longer available").	Retired ("past its retirement date and has been permanently deactivated").	EOL (End-of-Life) ("no longer available for use in all AWS Regions and requests made to this version will fail").

The meaning of the dates

An announcement / deprecation date is when the vendor first flags a model. The model is usually still fully callable at this point.
A retirement / shutdown / EOL date is when calls to the model stop working.
An intermediate date can matter too. On Amazon Bedrock the Legacy date is when new customers can no longer start using the model (and inactive existing customers may lose access), while the public extended access start date (for models with EOL dates after February 1, 2026) is when a Legacy model may move to higher provider-set pricing until EOL.

The same model can have different dates on different platforms

This is the single most important thing to know. A model offered through more than one platform is governed by each platform's own schedule, and those schedules diverge. Both Anthropic and Amazon Bedrock state this explicitly:

Anthropic: "The dates on this page apply to Anthropic-operated platforms ... Partner-operated platforms (Amazon Bedrock and Google Cloud) set their own retirement schedules, so a model's lifecycle status and dates can differ."

Amazon Bedrock: "Model lifecycle dates on this page are specific to Amazon Bedrock and may differ from dates published by model providers (such as Anthropic or Cohere). For Amazon Bedrock usage, only the dates on this page apply."

For example, Claude Sonnet 4 (claude-sonnet-4-20250514) is listed as Retired on the Anthropic API on June 15, 2026, while on Amazon Bedrock the same model (anthropic.claude-sonnet-4-20250514-v1:0) has an EOL date of October 14, 2026. Always check the row for the platform you actually call.

Sourcing

Every date and model ID below is transcribed from the vendor's official documentation at the time of writing, with the source page linked at the end of each vendor section. This page does not use second-hand reporting. Where an official page is dynamically rendered and its per-model table could not be transcribed verbatim, that is stated plainly and the reader is pointed to the official page.

Deprecation Calendar

Upcoming deadlines across all vendors

The consolidated table lists officially scheduled deadlines on or after this page's First Published date, in ascending order. Each platform's official lifecycle page is linked in the per-vendor sections below. Dates that have already passed are retained in the per-vendor tables for historical reference.

* You can sort the table by clicking on the column name.

Date	Platform	Model(s)	What happens	Replacement (as listed)
2026-07-07	Amazon Bedrock	Meta Llama 3.1 405B Instruct; Llama 3.2 1B / 3B / 11B / 90B Instruct	EOL	(not listed)
2026-07-14	Google Gemini API	`gemini-embedding-001`	Shutdown	`gemini-embedding-2`
2026-07-30	Amazon Bedrock	Claude 3 Sonnet; Claude 3.5 Sonnet; Claude 3.5 Sonnet v2; Claude 3.7 Sonnet (GovCloud)	EOL	(not listed)
2026-08-05	Anthropic API	`claude-opus-4-1-20250805`	Retired	`claude-opus-4-8`
2026-08-17	Google Gemini API	`imagen-4.0-generate-001`; `imagen-4.0-ultra-generate-001`; `imagen-4.0-fast-generate-001`	Shutdown	`gemini-3.1-flash-image`
2026-08-19	Amazon Bedrock	Cohere Command R; Command R+	EOL	(not listed)
2026-08-26	OpenAI	Assistants API (`/v1/assistants`, `/v1/threads`, and related endpoints)	Shutdown	Responses API and Conversations API
2026-09-10	Amazon Bedrock	Claude 3 Haiku	EOL	(not listed)
2026-09-14	Amazon Bedrock	Amazon Nova Premier; Amazon Nova Sonic	EOL	(not listed)
2026-09-30	Amazon Bedrock	Amazon Nova Canvas; Amazon Nova Reel (`v1:0`, `v1:1`)	EOL	(not listed)
2026-10-14	Amazon Bedrock	Claude Sonnet 4	EOL	(not listed)
2026-10-16	Google Gemini API	`gemini-2.5-pro`; `gemini-2.5-flash`	Shutdown	`gemini-3.1-pro-preview`; `gemini-3.5-flash`
2026-11-26	Amazon Bedrock	AI21 Jamba 1.5 Large; Jamba 1.5 Mini	EOL	(not listed)
2026-11-30	Amazon Bedrock	TwelveLabs Marengo Embed v2.7	EOL	(not listed)
2027-05-07	Google Gemini API	`gemini-3.1-flash-lite`	Shutdown	(not listed)

The per-vendor tables below give the full detail, including already-passed dates and the announcement or Legacy dates that precede each retirement.

Anthropic (Anthropic API / Claude Platform on AWS / Microsoft Foundry)

Anthropic assigns each model a lifecycle state (Active, Legacy, Deprecated, Retired) and, for deprecated models, a retirement date and a recommended replacement. For currently Active models, Anthropic lists a "Not sooner than" floor date rather than a scheduled retirement.

Currently Active models (earliest possible retirement):

Model ID	Retirement not sooner than
`claude-opus-4-8`	2027-05-28
`claude-opus-4-7`	2027-04-16
`claude-opus-4-6`	2027-02-05
`claude-opus-4-5-20251101`	2026-11-24
`claude-sonnet-4-6`	2027-02-17
`claude-sonnet-4-5-20250929`	2026-09-29
`claude-haiku-4-5-20251001`	2026-10-15

claude-fable-5 and claude-sonnet-5 are current flagship models on the Anthropic API and are not listed with a retirement floor.

Deprecated and retired models (with retirement dates):

* You can sort the table by clicking on the column name.

Model ID	Deprecation announced	Retirement date	Recommended replacement	State
`claude-opus-4-1-20250805`	2026-06-05	2026-08-05	`claude-opus-4-8`	Deprecated
`claude-mythos-preview`	(not listed)	2026-06-30	`claude-mythos-5`	Retired
`claude-opus-4-20250514`	2026-04-14	2026-06-15	`claude-opus-4-8`	Retired
`claude-sonnet-4-20250514`	2026-04-14	2026-06-15	`claude-sonnet-4-6`	Retired
`claude-3-7-sonnet-20250219`	2025-10-28	2026-02-19	`claude-sonnet-4-6`	Retired
`claude-3-5-sonnet-20241022`	2025-08-13	2025-10-28	`claude-sonnet-4-6`	Retired
`claude-3-5-sonnet-20240620`	2025-08-13	2025-10-28	`claude-sonnet-4-6`	Retired
`claude-3-5-haiku-20241022`	2025-12-19	2026-02-19	`claude-haiku-4-5-20251001`	Retired
`claude-3-haiku-20240307`	2026-02-19	2026-04-20	`claude-haiku-4-5-20251001`	Retired
`claude-3-opus-20240229`	2025-06-30	2026-01-05	`claude-opus-4-8`	Retired
`claude-3-sonnet-20240229`	2025-01-21	2025-07-21	`claude-sonnet-4-6`	Retired
`claude-2.1`	2025-01-21	2025-07-21	`claude-opus-4-8`	Retired
`claude-2.0`	2025-01-21	2025-07-21	`claude-opus-4-8`	Retired
`claude-1.3`, `claude-1.2`, `claude-1.1`, `claude-1.0`	2024-09-04	2024-11-06	`claude-haiku-4-5-20251001`	Retired
`claude-instant-1.2`, `claude-instant-1.1`, `claude-instant-1.0`	2024-09-04	2024-11-06	`claude-haiku-4-5-20251001`	Retired

The claude-mythos-preview row is sourced from a notice on the official deprecations page rather than its model-status table; the notice states the model will be retired on June 30, 2026, with claude-mythos-5 as the migration target, and does not list a separate deprecation announcement date.

Anthropic also lists an API-parameter deprecation: temperature, top_p, and top_k are deprecated on Claude Opus 4.7 and later (including Claude Opus 4.8) and on Claude Sonnet 5, returning a 400 error when set to a non-default value.

Official sources: Model deprecations - Claude Docs, Models overview - Claude Docs, Commitments on Model Deprecation and Preservation.

OpenAI

OpenAI's Deprecations page is a dynamically rendered application, so its full per-model shutdown table could not be transcribed verbatim for this edition. OpenAI's confirmed lifecycle terminology and notification practice are in the Vendor Lifecycle Policies section below. The individual deprecation that could be confirmed from official documentation is:

Announced	Shutdown date	Deprecated system	Recommended replacement
2025-08-26	2026-08-26	Assistants API (`/v1/assistants`, `/v1/threads`, and related endpoints)	Responses API and Conversations API

For the authoritative, current list of per-model shutdown dates, see OpenAI's official Deprecations page (linked below). Note the documentation host migration: the older platform.openai.com/docs/deprecations URL now redirects to developers.openai.com.

Official sources: OpenAI Deprecations, OpenAI Models.

Google — Gemini API (Google AI for Developers)

The Gemini API deprecations page publishes shutdown dates per model. Google states that "the shutdown dates listed in the table indicate the earliest possible dates on which a model might be retired," and that the exact date is communicated to users with advance notice. The table below lists models with a published shutdown date, in ascending order.

* You can sort the table by clicking on the column name.

Model ID	Shutdown date	Recommended replacement
`imagen-3.0-generate-002`	2025-11-10	`imagen-4.0-generate-001`
`gemini-2.0-flash-live-001`	2025-12-09	`gemini-3.1-flash-live-preview`
`gemini-live-2.5-flash-preview`	2025-12-09	`gemini-3.1-flash-live-preview`
`text-embedding-004`	2026-01-14	`gemini-embedding-2`
`gemini-3-pro-preview`	2026-03-09	`gemini-3.1-pro-preview`
`gemini-robotics-er-1.5-preview`	2026-04-30	`gemini-robotics-er-1.6-preview`
`gemini-3.1-flash-lite-preview`	2026-05-25	`gemini-3.1-flash-lite`
`gemini-2.0-flash`	2026-06-01	`gemini-3.5-flash`
`gemini-2.0-flash-001`	2026-06-01	`gemini-3.5-flash`
`gemini-2.0-flash-lite`	2026-06-01	`gemini-3.1-flash-lite`
`gemini-2.0-flash-lite-001`	2026-06-01	`gemini-3.1-flash-lite`
`gemini-3.1-flash-image-preview`	2026-06-25	`gemini-3.1-flash-image`
`gemini-3-pro-image-preview`	2026-06-25	`gemini-3-pro-image`
`veo-3.0-generate-001`	2026-06-30	`veo-3.1-generate-preview`
`veo-3.0-fast-generate-001`	2026-06-30	`veo-3.1-fast-generate-preview`
`veo-2.0-generate-001`	2026-06-30	`veo-3.1-generate-preview`
`gemini-embedding-001`	2026-07-14	`gemini-embedding-2`
`imagen-4.0-generate-001`	2026-08-17	`gemini-3.1-flash-image`
`imagen-4.0-ultra-generate-001`	2026-08-17	`gemini-3.1-flash-image`
`imagen-4.0-fast-generate-001`	2026-08-17	`gemini-3.1-flash-image`
`gemini-2.5-pro`	2026-10-16	`gemini-3.1-pro-preview`
`gemini-2.5-flash`	2026-10-16	`gemini-3.5-flash`
`gemini-3.1-flash-lite`	2027-05-07	(not listed)

Google's changelog separately records the earlier Gemini 1.5 models (gemini-1.5-pro, gemini-1.5-flash, gemini-1.5-flash-8b) as shut down effective 2025-09-29; they no longer appear in the current deprecations table.

Official sources: Gemini API deprecations, Gemini API models.

Google — Vertex AI (Google Cloud)

Vertex AI (currently branded within the Gemini Enterprise Agent Platform documentation) maintains its own model-versioning and deprecations pages, separate from the Gemini API. Its core "Model versions and lifecycle" page is dynamically rendered and its full per-model table could not be transcribed verbatim for this edition. The individual events that could be confirmed from official Vertex AI documentation are:

Item	Event	Date	Replacement / migration
`gemini-2.0-flash-001`, `gemini-2.0-flash-lite-001`	Discontinued	2026-06-01	Gemini 3.1 Flash-Lite, Gemma 4, or a more recent Gemini release
Vertex AI SDK "Generative AI module"	Deprecated 2025-06-24, shutdown 2026-06-24	2026-06-24	Google Gen AI SDK

Vertex AI publishes stable model versions with retirement dates and auto-updated aliases that always point to the latest stable version. For the authoritative per-model retirement dates — including partner "Models as a Service" offerings such as Anthropic Claude and Mistral on Vertex AI — see the official pages linked below.

Official sources: Vertex AI generative AI deprecations, Model versions and lifecycle.

Amazon Bedrock

A model on Amazon Bedrock is in one of three states: Active, Legacy, or End-of-Life (EOL). The table below is the set of models currently in the Legacy state or pending EOL on Amazon Bedrock. Per AWS, this table "does not include Active models or models that have already passed their EOL date," and it does not list recommended replacements. The public extended access date (for EOL dates after February 1, 2026) marks when a Legacy model may move to higher, provider-set pricing until EOL.

* You can sort the table by clicking on the column name.

Provider	Model	Model ID	Legacy date	EOL date	Public extended access
Meta	Llama 3.1 405B Instruct	`meta.llama3-1-405b-instruct-v1:0`	2026-01-07	2026-07-07	2026-04-07
Meta	Llama 3.2 1B Instruct	`meta.llama3-2-1b-instruct-v1:0`	2026-01-07	2026-07-07	2026-04-07
Meta	Llama 3.2 3B Instruct	`meta.llama3-2-3b-instruct-v1:0`	2026-01-07	2026-07-07	2026-04-07
Meta	Llama 3.2 11B Instruct	`meta.llama3-2-11b-instruct-v1:0`	2026-01-07	2026-07-07	2026-04-07
Meta	Llama 3.2 90B Instruct	`meta.llama3-2-90b-instruct-v1:0`	2026-01-07	2026-07-07	2026-04-07
Anthropic	Claude 3 Sonnet	`anthropic.claude-3-sonnet-20240229-v1:0`	2026-01-30	2026-07-30	2026-04-30 (varies by Region)
Anthropic	Claude 3.5 Sonnet	`anthropic.claude-3-5-sonnet-20240620-v1:0`	2026-01-30	2026-07-30	2026-04-30
Anthropic	Claude 3.5 Sonnet v2	`anthropic.claude-3-5-sonnet-20241022-v2:0`	2026-01-30	2026-07-30	2026-04-30
Anthropic	Claude 3.7 Sonnet (GovCloud)	`anthropic.claude-3-7-sonnet-20250219-v1:0`	2026-01-30	2026-07-30	2026-04-30
Cohere	Command R	`cohere.command-r-v1:0`	2026-02-19	2026-08-19	2026-05-19
Cohere	Command R+	`cohere.command-r-plus-v1:0`	2026-02-19	2026-08-19	2026-05-19
Anthropic	Claude 3 Haiku	`anthropic.claude-3-haiku-20240307-v1:0`	2026-03-10	2026-09-10	2026-06-10
Amazon	Nova Premier	`amazon.nova-premier-v1:0`	2026-03-13	2026-09-14	(none)
Amazon	Nova Sonic	`amazon.nova-sonic-v1:0`	2026-03-13	2026-09-14	(none)
Amazon	Nova Canvas	`amazon.nova-canvas-v1:0`	2026-03-30	2026-09-30	(none)
Amazon	Nova Reel	`amazon.nova-reel-v1:0`	2026-03-30	2026-09-30	(none)
Amazon	Nova Reel	`amazon.nova-reel-v1:1`	2026-03-30	2026-09-30	(none)
Anthropic	Claude Sonnet 4	`anthropic.claude-sonnet-4-20250514-v1:0`	2026-04-14	2026-10-14	2026-07-14
AI21 Labs	Jamba 1.5 Large	`ai21.jamba-1-5-large-v1:0`	2026-05-26	2026-11-26	2026-08-26
AI21 Labs	Jamba 1.5 Mini	`ai21.jamba-1-5-mini-v1:0`	2026-05-26	2026-11-26	2026-08-26
TwelveLabs	Marengo Embed v2.7	`twelvelabs.marengo-embed-2-7-v1:0`	2026-05-29	2026-11-30	2026-08-29
Amazon	Titan Image Generator G1 v2	`amazon.titan-image-generator-v2:0`	2025-12-30	2026-06-30	(none)

Official source: Model lifecycle - Amazon Bedrock User Guide.

Vendor Lifecycle Policies

This section summarizes each vendor's stated notification practice and model-ID conventions — the rules that govern how the dates above are set and communicated.

Anthropic

Notice: Anthropic "notifies customers with active deployments for models with upcoming retirements, providing at least 60 days notice before model retirement for publicly released models."
After retirement: "Requests to models past the retirement date will fail."
Model IDs carry a dated snapshot suffix (for example, claude-opus-4-5-20251101), and aliases (for example, claude-opus-4-5) point to the latest snapshot.
Scope: dates apply to Anthropic-operated platforms (the Claude API, Claude Platform on AWS, and Microsoft Foundry); Amazon Bedrock and Google Cloud set their own schedules.
Anthropic has published "Commitments on Model Deprecation and Preservation," including long-term preservation of model weights.

OpenAI

Notice: at least 6 months for generally available (GA) models; at least 3 months for specialized variants of GA models; preview models (whose names contain "preview") may be retired with much shorter notice, such as 2 weeks. Safety- or compliance-driven timelines can be shorter.
Notification method: impacted customers actively using a model are notified by email, with documentation updates and blog posts for larger changes.
Terminology: a model or endpoint becomes "deprecated" immediately when announced; at its "shutdown" (used interchangeably with "sunset") date it is "completely turned off" and "will no longer be accessible."

Google — Gemini API

Stability labels: stable ("usually don't change"; recommended for production), preview ("will be deprecated with at least 2 weeks notice"), experimental ("not ... suitable for production"), and latest (an alias that is "hot-swapped with every new release," with "a 2-week notice ... through email before the version behind latest is changed").
Shutdown dates in the table are "the earliest possible dates on which a model might be retired"; the exact date is communicated with advance notice.
At shutdown, a model is "completely turned off, and the endpoint is no longer available."

Google — Vertex AI

Vertex AI distinguishes latest stable models (recommended for new and active projects) from legacy stable models (older, still-supported versions), and marks a version retired once "past its retirement date and ... permanently deactivated."
Auto-updated aliases always point to the latest stable model; Google recommends pinning an explicit stable version for production.
Vertex AI's exact per-model retirement dates and notice windows are published on its official model-versions and deprecations pages (linked in the Vertex AI section above). The documentation host has migrated from cloud.google.com to docs.cloud.google.com, and the generative-AI docs are now branded under the "Gemini Enterprise Agent Platform."

Amazon Bedrock

Minimum availability: "Once a model launches on Amazon Bedrock, it will remain on Amazon Bedrock for at least 12 months before the EOL date."
Legacy period: "A model will be in the Legacy state for at least 6 months before the EOL date." New customers cannot use Legacy models, and existing customers may lose access after 15 days of inactivity. You cannot create new Provisioned Throughput or new fine-tuning jobs on a Legacy model.
Customization: if you fine-tuned or customized a model before it entered Legacy, you can still create a new custom model deployment for on-demand inference and continue using existing on-demand deployments or Provisioned Throughput endpoints created before Legacy — but you cannot start new fine-tuning jobs or create new Provisioned Throughput endpoints once the model is Legacy.
Public extended access: for models with EOL dates after February 1, 2026, after at least 3 months in Legacy the model enters a public extended access period (a minimum of 3 more months to EOL) during which pricing may increase as set by the provider.
After EOL: "requests made to this version will fail, unless there is a private arrangement between you and the provider for continued access."
How it's surfaced: the state appears in the console and in the modelLifecycle field returned by the GetFoundationModel and ListFoundationModels API calls.

Frequently Asked Questions about AI Model Deprecations

What is the difference between deprecation and retirement?: Deprecation (or, on Amazon Bedrock, the Legacy state) means a model is still callable but is scheduled to go away: the vendor has flagged it, usually named a recommended replacement, and set a date. Retirement — called "shutdown" by OpenAI and the Gemini API, "retired" by Anthropic and Vertex AI, and "EOL" by Amazon Bedrock — is the date the model stops working. Before that date, existing code keeps running; after it, calls fail.
How do vendors announce model deprecations?: The notice periods differ. Anthropic provides at least 60 days notice before retirement for publicly released models. OpenAI gives at least 6 months for generally available models, at least 3 months for specialized variants, and as little as about 2 weeks for preview models. The Gemini API gives at least 2 weeks for preview and "latest" aliases and treats its table dates as the earliest possible shutdown. Amazon Bedrock keeps a model at least 12 months on the platform and at least 6 months in the Legacy state before EOL. Vendors notify affected customers by email and update their documentation; larger changes are also announced on blogs.
What happens to API calls to a retired model?: They fail. Anthropic states that "requests to retired models will fail." Amazon Bedrock states that after EOL "requests made to this version will fail." The Gemini API states that a shut-down model is "completely turned off, and the endpoint is no longer available." OpenAI states that a shut-down model or endpoint "will no longer be accessible." Migration does not happen automatically — you must update your application code to a supported model before the date.
How should I plan a model migration?: Find your model's row for the specific platform you call (the same model can have different dates on different platforms), note the retirement, shutdown, or EOL date and the vendor's recommended replacement, test the replacement, and switch before the date. Step-by-step migration mechanics for Claude models are covered in the Anthropic Claude Model Migration Guide. To estimate context and token budgets for a candidate replacement, the LLM Token Counter and Context Budget Planner may help.

Summary

Model end-of-life is a recurring operational event across every AI platform, but each vendor publishes its schedule separately and uses different words — deprecated, legacy, retired, shutdown, sunset, EOL — for the same two underlying states. This page consolidates the officially published dates for the Anthropic API, OpenAI, Google (Gemini API and Vertex AI), and Amazon Bedrock, maps each vendor's vocabulary onto a common frame, and records that the same model can carry different dates on different platforms.

This first edition lists every dated model on the Anthropic API, Amazon Bedrock, and Google Gemini API pages, and publishes the confirmed lifecycle policies plus individually verified events for OpenAI and Google Vertex AI. Future updates will expand the OpenAI and Vertex AI per-model schedules and, as warranted, add further platforms. The page is reviewed and updated quarterly and whenever major deprecations are announced; always confirm the current dates on the official pages linked in each section before acting.

Related references on hidekazu-konishi.com:

References:
Model deprecations - Claude Docs
OpenAI Deprecations
Gemini API deprecations
Vertex AI generative AI deprecations
Model lifecycle - Amazon Bedrock User Guide

References:
Tech Blog with curated related content

Written by Hidekazu Konishi