Claude 3.5 Haiku Deprecation, Shutdown Dates & Migration Guide

Runs locally in your browser — 0 bytes uploaded Synced 2026-11-12 UTC · 2 variants · 2 ecosystems

Track confirmed UTC deprecation and shutdown dates for Claude 3.5 Haiku (Anthropic) across Anthropic, Google Vertex AI. Preview claude-3-5-haiku-20241022 → claude-haiku-4-5-20251001 upgrades locally below, audit full configs in the Model Config Auditor, or benchmark token pricing in DevToken.

Tracked Variants 2
Earliest Upcoming EOL 2026-07-05
Recommended Upgrade claude-haiku-4-5-20251001
Ecosystems Covered Anthropic, Google Vertex AI

1. Quick .env & SDK Snippet Replacement Matcher

Edit or paste your .env assignment, LiteLLM route, or SDK model identifier below to check live 3-state EOL status and copy a ready-to-apply replacement diff locally in your browser.

2 of 2 configured models need migration

Replacement Diff Preview (claude-3-5-haiku-20241022 → claude-haiku-4-5-20251001)

# ANTHROPIC_MODEL: claude-3-5-haiku-20241022 -> claude-haiku-4-5-20251001 [RETIRED · EOL 2026-02-19]
- ANTHROPIC_MODEL="claude-3-5-haiku-20241022"
+ ANTHROPIC_MODEL="claude-haiku-4-5-20251001"

# VERTEX_MODEL: claude-3-5-haiku -> claude-haiku-4-5-20251001 [RETIRED · EOL 2026-07-05]
- VERTEX_MODEL="claude-3-5-haiku"
+ VERTEX_MODEL="claude-haiku-4-5-20251001"

2. Cross-Ecosystem Claude 3.5 Haiku Lifecycle Matrix (2)

Direct vendor APIs and cloud platforms retire dated snapshots on independent schedules. Verify the exact model ID, vendor lifecycle stage, and UTC shutdown date matching your deployment.

Claude 3.5 Haiku lifecycle status, UTC shutdown dates, and replacement models across Anthropic, Google Vertex AI
Model ID Provider Calculated Status Confirmed Shutdown (UTC) Vendor Lifecycle Replacement & Migration Source
claude-3-5-haiku Google Vertex AIPartner Models RETIRED 2026-07-05130d ago RetiredDep: 2026-01-05
claude-haiku-4-5-20251001 Cost → Audit →
Docs ↗
claude-3-5-haiku-20241022 Anthropic RETIRED 2026-02-19266d ago RetiredDep: 2025-12-19
claude-haiku-4-5-20251001 Cost → Audit →
Docs ↗

3. Production Migration Checklist (claude-3-5-haiku-20241022 → claude-haiku-4-5-20251001)

Follow this deterministic engineering sequence before retiring pinned snapshots in production services and SDK clients:

  1. Inventory pinned model IDs: Search repositories and deployment manifests for ANTHROPIC_MODEL, anthropic/ LiteLLM routes, and dated snapshot strings in the Claude 3.5 Haiku family (0 deprecated, 2 retired, 0 active variants tracked).
  2. Benchmark successor quality & token pricing: Validate structured output schemas, tool-calling payloads, and latency against claude-haiku-4-5-20251001, then compare input, output, and cached token rates in DevToken.
  3. Enforce keyless CI guardrails: Wire RSS, Atom, iCal feeds & CI Guard into pull-request checks so retired or deprecated Claude 3.5 Haiku identifiers cannot re-enter production.

Compare sibling model families or inspect full provider-level schedules across every ecosystem hosting this family:

Claude 3 Haiku

DEPRECATED (1d)
Anthropic · 3 tracked IDs · 3 ecosystems Anthropic, Google Vertex AI, AWS Bedrock Upgrade: claude-haiku-4-5-20251001 Earliest EOL: 2026-11-13

5. Claude 3.5 Haiku Deprecation & Upgrade FAQ

Is Claude 3.5 Haiku deprecated or retired across Anthropic, Google Vertex AI?

LLMEOL tracks 2 Claude 3.5 Haiku variants across Anthropic, Google Vertex AI: 0 deprecated with scheduled shutdowns, 2 retired past their UTC EOL date, and 0 active with no announced shutdown date. Check the cross-ecosystem matrix above for exact snapshot dates.

What is the recommended replacement model when migrating off claude-3-5-haiku-20241022?

The primary recommended upgrade target for claude-3-5-haiku-20241022 is claude-haiku-4-5-20251001. Always test prompt formatting, max output tokens, and tool schemas on claude-haiku-4-5-20251001, and compare token pricing in DevToken before switching production traffic.

How can I replace claude-3-5-haiku-20241022 in .env and LiteLLM configs safely?

Paste your ANTHROPIC_MODEL assignment or LiteLLM model block into the Quick Replacement Matcher on this page to generate an exact diff, or open the full Local Model Config Auditor to scan multi-service manifests with zero network upload.