DEPENDENCIES & RESILIENCE

Anthropic shut down two models on a US order — what it means for your business

13 June 2026 · 5 min read

On 12 June 2026, Anthropic announced something few had treated as a realistic scenario: following a US government export-control directive, it had to disable two of its models (Fable 5 and Mythos 5) for all customers — not gradually, but immediately, to ensure compliance. Its other models stayed available.

You don't have to use that specific model for the lesson to apply to you. If your business runs on a third-party AI — a chatbot, a voice agent, a text tool — you've just watched a risk most people ignore play out live.

What actually happened

Per Anthropic's official statement, the US government issued a directive suspending access to the two models for any foreign national, inside or outside the US. The net effect was that, to comply, the company shut the models down for everyone. The directive arrived that same afternoon and took effect almost immediately.

A decision neither the provider nor you made — but one that stopped the service from one moment to the next.

Why it matters

When you build a function on top of an AI model, you inherit the provider's risks: pricing changes, version retirements, outages — and, as we just saw, regulatory or geopolitical decisions entirely outside your control. If your support chatbot or voice agent "speaks" through one specific model and it goes dark, your service goes down — and the customer blames you, not the provider.

This is exactly why serious contracts carry a "third-party dependencies" clause: outages or changes at the model provider sit outside your control and liability — but that doesn't relieve you of the duty to have a plan.

What to do — practically

  • Map it. Which business function runs on which model/provider? If you don't know, that's the first gap.
  • Have a fallback. A second provider/model you can switch to fast — ideally without rebuilding everything.
  • Fix the contract. Ask for terms on model discontinuation/replacement, change notice and service continuity.
  • Plan the failure. What the bot tells customers if the service drops; how it escalates to a human.

The EU AI Act already pushes you toward this mindset: human oversight, documentation, risk management. Resilience against third-party dependencies is part of the same puzzle — not a luxury.

Do you know which model each of your AI functions runs on?

The Shielding Audit maps your AI systems, their third-party dependencies and resilience gaps — in priority order. It starts with a free 45-minute mapping session.

Book a free session
← All articles