← all posts
migration·Lukas Babaliauskas·Nov 20, 2026·12 min read

Anthropic model deprecation schedule: every Claude retirement date

Every Claude model retirement date since 2024, the active models' earliest dates, Bedrock and Google Cloud dates, and what changes off Claude Sonnet 4.5.

The next Claude model to retire is Claude Sonnet 4.5. Anthropic deprecated claude-sonnet-4-5-20250929 on September 30, 2026, and requests to it fail on the Claude API from November 30, 2026. The listed replacement is claude-sonnet-5-5. After that, no Claude model on Anthropic's API has a retirement date: every other model is either already retired or active with a "not sooner than" date, and the only other deprecated model, claude-mythos-preview, has no date yet.

Three things about Anthropic's schedule catch teams out:

  • +Notice is now about 60 days. Until October 2025 Anthropic gave 76 to 189 days. The five retirements announced since December 2025 each came 60 to 62 days ahead, the minimum Anthropic promises.
  • +"Not sooner than" is a floor, not a date. Claude Haiku 4.5's floor, October 15, 2026, has passed and the model is still active. A model retires only after a deprecation notice.
  • +Bedrock and Google Cloud keep their own calendars. Claude Sonnet 4.5 runs on AWS Bedrock until April 8, 2027, and Claude Opus 4.1, retired on Anthropic's API in August, runs on Bedrock until January 8, 2027.

This post lists every Claude retirement since 2024, the active models' floors, the Bedrock and Google Cloud dates, what changes in the request when you move off Claude Sonnet 4.5, and how to find and test every Claude call before its date. The facts come from Anthropic's model deprecations page ↗, its models overview ↗, the Claude Sonnet 5.5 migration guide ↗, AWS's Bedrock model lifecycle page ↗ and Google Cloud's partner model deprecations page ↗, all read on November 17, 2026. Check the page again before you act on a date.

Every Claude retirement date

Anthropic's deprecation history, oldest at the bottom, on the Claude API:

Model IDAnnouncedRetiredNoticeListed replacement
claude-sonnet-4-5-20250929September 30, 2026November 30, 202661 daysclaude-sonnet-5-5
claude-opus-4-1-20250805June 5, 2026August 5, 202661 daysclaude-opus-4-8
claude-sonnet-4-20250514April 14, 2026June 15, 202662 daysclaude-sonnet-5-5
claude-opus-4-20250514April 14, 2026June 15, 202662 daysclaude-opus-4-8
claude-3-haiku-20240307February 19, 2026April 20, 202660 daysclaude-haiku-4-5-20251001
claude-3-5-haiku-20241022December 19, 2025February 19, 202662 daysclaude-haiku-4-5-20251001
claude-3-7-sonnet-20250219October 28, 2025February 19, 2026114 daysclaude-sonnet-5-5
claude-3-opus-20240229June 30, 2025January 5, 2026189 daysclaude-opus-4-8
claude-3-5-sonnet-20240620, claude-3-5-sonnet-20241022August 13, 2025October 28, 202576 daysclaude-sonnet-5-5
claude-2.0, claude-2.1, claude-3-sonnet-20240229January 21, 2025July 21, 2025181 daysclaude-opus-4-8 for Claude 2, claude-sonnet-5-5 for Sonnet 3
claude-1.0 to claude-1.3, claude-instant-1.0 to claude-instant-1.2September 4, 2024November 6, 202463 daysclaude-haiku-4-5-20251001

The replacement column is what Anthropic's page says today, not what it said at the time. Anthropic updates the listed replacement as newer models ship, which is why Claude 1 points to a model released in 2025.

claude-mythos-preview is the one other deprecated model. Anthropic deprecated it on June 9, 2026, and its retirement date is "to be announced."

What the history says about the next retirement

Two patterns hold across the table.

The notice period shrank to the minimum. Anthropic's policy is at least 60 days' notice before retiring a publicly released model, by email to customers with active deployments and on the deprecations page. Through October 2025 it gave well over that: 181 days for Claude 2, 189 for Claude Opus 3, 76 for Claude Sonnet 3.5 and 114 for Claude Sonnet 3.7. Starting with Claude Haiku 3.5 in December 2025, all five announcements since came 60 to 62 days ahead. Plan for the next one to arrive with two months' warning, which is not much time to test a replacement on a large suite.

Recent models lasted about a year. Measured from the date in the model ID to the retirement date, Claude Sonnet 3.7 and Claude Opus 4.1 both lasted exactly 365 days, Claude Sonnet 4 and Opus 4 lasted 397, and Claude Sonnet 4.5 lasts 427. The Claude 3 models lasted longer: 676 days for Claude 3 Opus and 774 for Claude 3 Haiku. A model you pin today should be expected to need a migration within about 12 to 15 months.

Active Claude models and their "not sooner than" dates

Every active model on the deprecations page has a tentative retirement date written as "not sooner than":

Model IDNot sooner than
claude-haiku-4-5-20251001October 15, 2026 (passed; still active)
claude-opus-4-5-20251101November 24, 2026
claude-opus-4-6February 5, 2027
claude-sonnet-4-6February 17, 2027
claude-opus-4-7April 16, 2027
claude-opus-4-8May 28, 2027
claude-fable-5, claude-mythos-5June 9, 2027
claude-sonnet-5June 30, 2027
claude-opus-5July 24, 2027
claude-fable-5-1, claude-mythos-5-1September 1, 2027
claude-opus-5-5September 22, 2027
claude-sonnet-5-5September 28, 2027
claude-haiku-5-5October 7, 2027
claude-fable-5-2, claude-mythos-5-2November 9, 2027

Read these as the earliest a model could retire, not as a schedule. A model retires only after Anthropic deprecates it and gives notice. Claude Haiku 4.5 passed its floor in October without a notice, so it keeps running. Claude Opus 4.5 reaches its floor on November 24, 2026, but with no notice as of November 17 and a 60-day minimum, it can't retire before mid-January 2027.

The floors still matter when you pick a replacement. Anthropic still lists claude-haiku-4-5-20251001 as the replacement for Claude Haiku 3 and Claude Haiku 3.5, but its floor has passed, so it could be deprecated on any day with 60 days' notice. A migration off an old Haiku that lands on Haiku 4.5 may have to be repeated soon. claude-haiku-5-5, with a floor of October 7, 2027, is the longer-lived target, at a different price and with the request changes covered below.

Anthropic's model lifecycle: Active, Legacy, Deprecated, Retired

Anthropic uses four states:

  • +Active: fully supported and recommended.
  • +Legacy: no longer updated, and might be deprecated in the future.
  • +Deprecated: still works, but has a recommended replacement and an assigned retirement date. Anthropic warns that deprecated models "are likely to be less reliable than active models."
  • +Retired: requests fail.

Two other things change what "retired" means.

Model IDs and aliases. From the Claude 4.6 generation on, the dateless ID is the model: claude-sonnet-4-6 and claude-opus-4-8 are fixed snapshots, and Anthropic says it doesn't change the weights or configuration behind an existing ID. An update ships under a new ID, and every ID has its own retirement date. Before 4.6, IDs carry a date, as in claude-sonnet-4-5-20250929, and the Claude API also accepts short aliases such as claude-sonnet-4-5 that point to the latest dated snapshot of that minor version. Code that calls the alias claude-sonnet-4-5 is calling claude-sonnet-4-5-20250929, and it fails on November 30 the same way.

Retired models keep their weights. In November 2025 Anthropic committed ↗ to preserving the weights of every publicly released model for at least the lifetime of the company, and to interviewing each model before retirement for a post-deployment report. That doesn't keep a retired model callable on the API. Anthropic says it hopes to make past models available again, without a date.

Claude on AWS Bedrock and Google Cloud: different dates

Anthropic's dates apply to the platforms it operates: the Claude API, Claude Platform on AWS, Microsoft Foundry and the Anthropic-managed Claude models on Google Cloud. AWS Bedrock and Google's own Claude offering set their own schedules, and each says only its own page applies:

ModelClaude APIAWS BedrockGoogle Cloud (Google-managed)
Claude Sonnet 4.5November 30, 2026April 8, 2027 (Legacy since October 8, 2026)November 30, 2026
Claude Opus 4.1Retired August 5, 2026January 8, 2027, in three US regionsAvailable, no date on Google's deprecations page
Claude Sonnet 4Retired June 15, 2026Retired October 14, 2026Available, no date on Google's deprecations page
Claude Opus 4Retired June 15, 2026Not listedAvailable, no date on Google's deprecations page
Claude 3.7 SonnetRetired February 19, 2026Last regions retired November 13, 2026Retired May 11, 2026
Claude 3.5 Sonnet and 3.5 Sonnet v2Retired October 28, 2025Last regions retired November 13, 2026Retired February 19, 2026
Claude 3 HaikuRetired April 20, 2026Retired September 10, 2026 in most regions, November 13 in the last threeRetired August 23, 2026
Claude 3.5 HaikuRetired February 19, 2026Not listedRetired July 5, 2026

So the same model can be retired on one platform and still answer on another. Anthropic's own models page marks Claude Opus 4.1 and Claude Sonnet 4 as "retired, except on Claude Models on Google Cloud (Google managed) and Bedrock." If you run Claude through Bedrock, take the Bedrock date from AWS's lifecycle page, not from Anthropic's. Bedrock also lists a "public extended access" start for each Legacy model, January 8, 2027 for Claude Sonnet 4.5, and its lifecycle page explains what changes on that date for your account.

The model IDs differ as well. Bedrock uses anthropic.claude-sonnet-4-5-20250929-v1:0, often behind an inference profile prefix such as us. or global., and Google's managed offering uses claude-sonnet-4-5@20250929. A grep for the Claude API ID alone misses both.

Claude Sonnet 4.5 retires November 30, 2026: what changes

claude-sonnet-5-5 is cheaper per token than Claude Sonnet 4.5, at $2 per million input tokens and $10 per million output tokens against $3 and $15, with a 1M-token context window instead of 200K. But it isn't a model-string swap. The Sonnet 5.5 migration guide lists these changes for a Claude Sonnet 4.5 request:

In your Claude Sonnet 4.5 requestOn claude-sonnet-5-5What to do
No thinking field, so no thinkingAdaptive thinking runs by defaultRead content blocks by type, not content[0], and pass thinking blocks back unchanged in tool loops. To run without up-front thinking, send thinking: {"type": "between_tools"}; "disabled" returns a 400
thinking: {"type": "enabled", "budget_tokens": N}400 errorUse adaptive thinking and set output_config.effort
No effort settingEffort defaults to highSet output_config.effort explicitly, and test two or three levels
temperature, top_p, top_k400 errorRemove them
A prefilled last assistant turn400: "The conversation must end with a user message."Use structured outputs for format, the system prompt for preambles, the user turn for continuations
tool_choice of type any or tool400 errorSend tool_choice: {"type": "auto"}, mark the tool strict: true, and say in the prompt when to call it
output_formatDeprecated, 400 without a beta headerMove it to output_config.format
interleaved-thinking-2025-05-14, fine-grained-tool-streaming-2025-05-14 beta headersNot needed or replacedRemove the first; replace the second with eager_input_streaming: true on each tool
max_tokens sized for the visible answerCovers thinking too, and the same text is about 30% more tokensRecount with token counting, and raise max_tokens

Three of these change behavior without an error, which makes them the dangerous ones:

  • +Thinking on by default. The response can start with thinking blocks, so code that reads the first block as text breaks, and thinking tokens are billed as output.
  • +About 30% more tokens for the same text. Claude Sonnet 5.5 uses a newer tokenizer, so the per-token price cut is partly offset, and a max_tokens that fit before can now truncate.
  • +No forced tool choice. With auto, the model can answer without calling the tool your code expected. That shows up as a missing tool call, not a 400, once you've changed the request to stop the error.

The temperature change reaches beyond Sonnet 5.5. In API version 2026-10-21 Anthropic removed temperature, top_p and top_k for every model, and on earlier API versions Claude 4.7 and later models return a 400 for a non-default value. A test harness that pins temperature=0 for reproducibility needs another way to tell noise from regressions: sample each case several times and compare pass rates.

How to find every Claude model call

  1. +

    Grep for every ID form. The Claude API IDs, the pre-4.6 aliases, the Bedrock IDs and the Google-managed IDs:

    bash
    grep -rhoE "(anthropic\.)?claude-[a-z0-9.-]+(@[0-9]{8}|-v[0-9]:[0-9])?" \
      --exclude-dir={node_modules,.git,.venv,dist} . | sort | uniq -c | sort -rn

    Check config, environment files, infrastructure code, prompt registries, batch jobs and the eval harness, where a judge model is easy to forget.

  2. +

    Export the usage report. In the Claude Console, open the Usage ↗ page and click Export. The CSV breaks usage down by API key and model, which catches the calls a grep can't see, such as a service in another repo.

  3. +

    Check what answered. Every Messages API response names the model that served it:

    python
    import anthropic
    
    client = anthropic.Anthropic()
    msg = client.messages.create(
        model="claude-sonnet-4-5",
        max_tokens=16,
        messages=[{"role": "user", "content": "ping"}],
    )
    print(msg.model)  # the model that served the request
  4. +

    Write down what each route does with the model. Tool calls, structured output, free text or classification. That decides how much testing the replacement needs.

How to test the replacement before the date

Changing the model string makes the new model answer. It doesn't tell you whether it does the same job. In a model swap the regressions that matter mostly read fine: an argument changes format, an enum value moves one notch, a request the old model refused becomes a tool call.

  1. +Record a baseline while the old model still answers. Once it retires, nobody can record what it did. Capture 100 to 300 real production inputs per route, with the tools called, their arguments, the structured fields and the refusals. The method is in Build a golden eval suite from production traffic.
  2. +Replay the same inputs on the replacement and diff per route. Assert tool calls, arguments and structured fields deterministically, and use an LLM judge only for free text. Without temperature, sample each case several times. Compare per route, because a drop on one route disappears in an average.
  3. +Measure cost per request, not per token. Thinking tokens and the newer tokenizer both move the bill, so the paired cost per case is the number to check against the cheaper list price.
  4. +Cut over one route at a time, before the date. Keep the old model as a fallback only while it answers, and remove it from every fallback list before it retires: a fallback to a retired model fails exactly when you need it.

The full walkthrough, with code and the regressions it caught on a real upgrade, is in How to catch LLM regressions before a model upgrade ships.

Doing this with EvalShift

Disclosure: I'm the founder of EvalShift, and recording the baseline and replaying it on the replacement is the part it automates. The capture SDK wraps the Anthropic client and records real runs, including tool calls, and compare replays them against the replacement:

python
import anthropic
from evalshift import capture
from evalshift.adapters.anthropic import wrap_anthropic

client = wrap_anthropic(anthropic.Anthropic())  # each create() inside a capture records one call

TOOLS = [...]  # the tools the agent is offered, or [] for none

@capture.agent(suite="support", redact=True, tools=TOOLS)  # no-op unless EVALSHIFT_CAPTURE=1
def handle_ticket(message): ...
bash
pip install evalshift
EVALSHIFT_CAPTURE=1 python my_agent.py   # record production-shaped runs
evalshift capture sync                   # recorded runs -> golden suite
evalshift compare --suite-name support --to claude-sonnet-5-5

Both arms are live calls, so run it before November 30 while Claude Sonnet 4.5 still answers. Pass the full model ID to --to. EvalShift's config has no effort setting, so compare measures Claude Sonnet 5.5 at Anthropic's default effort, high: the change you get by editing only the model string. EvalShift sends temperature=0 on every call. If a model rejects it, EvalShift resends without it and marks the run as non-deterministic in the report, so set defaults.samples_per_example above 1. The max_cost_increase threshold in the migration_policy fails the verdict if the paired cost rises by more than you allow, which is where thinking tokens and the newer tokenizer would show up. Docs: /docs/sdk-adapters, /docs/captures, /docs/baselines.

FAQ

When is Claude Sonnet 4.5 being retired? On the Claude API, claude-sonnet-4-5-20250929 retires on November 30, 2026. Anthropic deprecated it on September 30, 2026 and lists claude-sonnet-5-5 as the replacement. Google Cloud's managed Claude offering shuts it down the same day, and AWS Bedrock runs it until April 8, 2027.

Which Claude models are deprecated right now? Two: claude-sonnet-4-5-20250929, retiring November 30, 2026, and claude-mythos-preview, deprecated June 9, 2026 with its retirement date still to be announced. Every other model on Anthropic's list is either active or already retired.

When was Claude 3 Opus retired? claude-3-opus-20240229 retired on the Claude API on January 5, 2026, after a deprecation notice on June 30, 2025. Anthropic's listed replacement is claude-opus-4-8. On Google Cloud it shut down on August 1, 2025.

When was Claude Sonnet 4 deprecated? Anthropic deprecated claude-sonnet-4-20250514 and claude-opus-4-20250514 on April 14, 2026, and both retired on the Claude API on June 15, 2026. Claude Sonnet 4 stayed on AWS Bedrock until October 14, 2026.

When was Claude 3.7 Sonnet retired? claude-3-7-sonnet-20250219 retired on the Claude API on February 19, 2026, after a notice on October 28, 2025. On Google Cloud it shut down on May 11, 2026, and its last AWS Bedrock regions reached end of life on November 13, 2026.

How much notice does Anthropic give before retiring a model? At least 60 days for publicly released models, by email to customers with active deployments and on the deprecations page. The five retirements announced since December 2025 each came 60 to 62 days ahead. Before that, notices ranged from 76 to 189 days.

Does the claude-sonnet-4-5 alias keep working after the retirement? No. Before the 4.6 generation, aliases such as claude-sonnet-4-5 point to the latest dated snapshot of that minor version, which is claude-sonnet-4-5-20250929. When that snapshot retires, calls to the alias fail too.

What does "not sooner than" mean on Anthropic's deprecations page? It is the earliest date an active model could retire, not a scheduled date. A model retires only after Anthropic deprecates it and gives notice. Claude Haiku 4.5's floor, October 15, 2026, passed without a notice, and the model is still active.

Keep reading