Claude (Anthropic) End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Claude (Anthropic) versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| Claude 1.0 | — | Mar 14, 2023 | Nov 6, 2024 | 641 days past EOL | EOL |
| Claude Instant 1.0 | — | Mar 14, 2023 | Nov 6, 2024 | 641 days past EOL | EOL |
| Claude 1.1 | — | Mar 14, 2023 | Nov 6, 2024 | 641 days past EOL | EOL |
| Claude 1.2 | — | Mar 14, 2023 | Nov 6, 2024 | 641 days past EOL | EOL |
| Claude Instant 1.1 | — | Mar 31, 2023 | Nov 6, 2024 | 641 days past EOL | EOL |
| Claude 1.3 | — | Apr 18, 2023 | Nov 6, 2024 | 641 days past EOL | EOL |
| Claude 2.0 | — | Jul 11, 2023 | Jul 21, 2025 | 384 days past EOL | EOL |
| Claude Instant 1.2 | — | Aug 9, 2023 | Nov 6, 2024 | 641 days past EOL | EOL |
| Claude 2.1 | — | Nov 21, 2023 | Jul 21, 2025 | 384 days past EOL | EOL |
| Claude Sonnet 3 | — | Mar 4, 2024 | Jul 21, 2025 | 384 days past EOL | EOL |
| Claude Opus 3 | — | Mar 4, 2024 | Jan 5, 2026 | 216 days past EOL | EOL |
| Claude Haiku 3 | — | Mar 13, 2024 | Apr 20, 2026 | 111 days past EOL | EOL |
| Claude Sonnet 3.5 (20240620) | — | Jun 21, 2024 | Oct 28, 2025 | 285 days past EOL | EOL |
| Claude Sonnet 3.5 (20241022) | — | Oct 22, 2024 | Oct 28, 2025 | 285 days past EOL | EOL |
| Claude Haiku 3.5 | — | Oct 22, 2024 | Feb 19, 2026 | 171 days past EOL | EOL |
| Claude Sonnet 3.7 | — | Feb 24, 2025 | Feb 19, 2026 | 171 days past EOL | EOL |
| Claude Opus 4 | — | May 22, 2025 | Jun 15, 2026 | 55 days past EOL | EOL |
| Claude Sonnet 4 | — | May 22, 2025 | Jun 15, 2026 | 55 days past EOL | EOL |
| Claude Opus 4.1 | — | Aug 5, 2025 | Aug 5, 2026 | 4 days past EOL | EOL |
| Claude Sonnet 4.5 | — | Sep 29, 2025 | Sep 29, 2026 | 51 days remaining | Warning |
| Claude Haiku 4.5 | — | Oct 15, 2025 | Oct 15, 2026 | 67 days remaining | Warning |
| Claude Opus 4.5 | — | Nov 24, 2025 | Nov 24, 2026 | 107 days remaining | Warning |
| Claude Opus 4.6 | — | Feb 5, 2026 | Feb 5, 2027 | 180 days remaining | Active |
| Claude Sonnet 4.6 | — | Feb 17, 2026 | Feb 17, 2027 | 192 days remaining | Active |
| Claude Opus 4.7 | — | Apr 16, 2026 | Apr 16, 2027 | 250 days remaining | Active |
| Claude Opus 4.8 | — | May 28, 2026 | May 28, 2027 | 292 days remaining | Active |
| Claude Fable 5 | — | Jun 9, 2026 | Jun 9, 2027 | 304 days remaining | Active |
| Claude Mythos 5 | — | Jun 9, 2026 | TBD | Supported | Active |
| Claude Sonnet 5 | — | Jun 30, 2026 | Jun 30, 2027 | 325 days remaining | Active |
| Claude Opus 5 | — | Jul 24, 2026 | Jul 24, 2027 | 349 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/claude)
What does Claude (Anthropic) end of life mean for your organization?
When a version of Claude (Anthropic) reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Claude (Anthropic) should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Claude (Anthropic) reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Commercial extended support | Not available for Claude (Anthropic) from the original maintainer | Third-party vendors patch some end-of-life software on a custom basis; availability depends on the specific version and source access |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →