Anthropic pulls Claude Sonnet 4.5 with no public notice
Key insights
- Anthropic removed Claude Sonnet 4.5 around May 15 with only a brief in-product pop-up and no official documentation or blog post.
- The removal is a full model deprecation, not a feature toggle, breaking any production system hardcoded to the Sonnet 4.5 model ID.
- Multiple developers on r/agi reported never seeing the pop-up warning before their workflows broke, indicating inconsistent notice delivery.
Why this matters
API-dependent production systems now face a concrete precedent: Anthropic can remove a model with no versioned deprecation timeline, no email notice, and no documentation update, meaning any hardcoded model ID is a single silent deletion away from an outage. Founders and technical leaders building on proprietary model APIs need to treat model availability as an operational risk category, not just a capability one, and architect accordingly with fallback routing or abstraction layers. The incident also signals that Anthropic's internal release and deprecation processes are not yet calibrated for the production dependency patterns of external developer teams, a gap that will matter more as enterprise adoption deepens.
Summary
Anthropic removed Claude Sonnet 4.5 from production access around May 15 without a blog post, documentation update, or formal deprecation notice — leaving developers who depended on the model scrambling after their integrations broke.
The only warning some users received was a brief in-product pop-up, which many report never seeing before the model disappeared entirely. The removal is a full deprecation, distinct from the earlier Sonnet 4.6 extended-thinking toggle change, meaning any application hardcoded to the Sonnet 4.5 model ID stopped working without warning.
Essentially: (Anthropic, affected developers) are caught in a communication breakdown over production-critical model access.
- Sonnet 4.5 was removed around May 15 with no accompanying changelog, API deprecation notice, or developer email.
- Multiple r/agi developers confirmed broken production workflows, with some reporting they never saw the pop-up warning at all.
- The deprecation is a model removal, not a feature flag change, making rollback or substitution non-trivial for teams with hardcoded model identifiers.
For an industry that increasingly runs critical infrastructure on third-party model APIs, this incident puts a sharp point on how fragile those dependencies can be when providers treat deprecations as internal housekeeping rather than public commitments.
Potential risks and opportunities
Risks
- Startups and production teams with hardcoded Sonnet 4.5 model IDs face immediate outages with no rollback path, and repeated incidents could push enterprise customers toward providers with formal SLA-backed deprecation windows (Google Vertex, Azure OpenAI).
- Anthropic faces reputational risk with developer-relations stakeholders if the pattern of silent removals continues into higher-stakes model deprecations, particularly as it courts enterprise contracts that typically require advance change-control notice.
- Third-party platforms and orchestration tools (LangChain, LlamaIndex, vendor-specific wrappers) that pinned to Sonnet 4.5 may have shipped broken releases to their own downstream users, compounding the blast radius beyond direct Anthropic API customers.
Opportunities
- Model routing and fallback infrastructure vendors (Portkey, OpenRouter, Martian) can position silent deprecation risk as a core sales argument for abstraction layers that automatically reroute to available model equivalents.
- Anthropic competitors with published, SLA-backed deprecation policies (Google Vertex AI, Azure OpenAI Service) gain a concrete differentiator to cite in enterprise procurement conversations happening right now.
- Developer tooling companies building model-ID monitoring or API health alerting (Datadog, Langfuse, Helicone) have a clear new alert category to ship: model availability change detection with automated fallback suggestions.
What we don't know yet
- Whether Anthropic has a formal deprecation policy with minimum notice windows, and if so, why it was not followed for Sonnet 4.5's May 15 removal.
- Which specific Anthropic API tiers or regions received the pop-up warning, and whether paid enterprise customers were notified separately from free-tier users.
- Whether Sonnet 4.5 will be reinstated or if a migration path to a functionally equivalent model (e.g., Sonnet 4.6) has been officially documented as of May 17.
Originally reported by reddit.com
Read the original article →Original headline: r/agi: Anthropic Removes Claude Sonnet 4.5 Silently — Developers Report No Official Announcement After Brief May 15 Pop-Up Warning