On June 9, Anthropic launched Fable 5. On June 12, it was gone. The US Commerce Department pulled it and Mythos 5 under export controls, three days after release, citing national security. The models returned July 1 after Anthropic agreed to new safeguards. If you shipped on Fable 5 in that window, you spent nineteen days without your model. That is the part builders need to sit with.
What actually happened
Commerce lifted the controls on June 30. Anthropic redeployed Fable 5 across Claude.ai, the platform, and Claude Code, capped at 50 percent of weekly limits through July 7, and shipped a new safety classifier that blocks the jailbreak that triggered the pause in over 99 percent of cases. The deal also has Anthropic reporting malicious activity and helping write future model standards. Access is back, but on new terms.
Why this is your problem
A frontier model can disappear for reasons that have nothing to do with your code. Regulation, a safety pause, a deprecation. If your product hard-depends on one model behind one API, you inherit every one of those risks. My advice: keep a second model wired up and tested, even if you never route to it, and abstract the model call behind your own interface so switching is a config change, not a rewrite. The teams who treated Fable 5’s outage as a fire drill already knew what their fallback does.