Anthropic reports Claude Fable 5 sightings were a UI bug; traffic stayed at zero

• According to the zero-traffic reply, Anthropic was serving exactly 0 traffic to Claude Fable 5, and the correction post reframed the apparent return as a UI bug.
• The confusion had real smoke behind it: the AWS Bedrock listing post surfaced active model cards and IDs, while the Bedrock catalog screenshot showed Fable 5 back in Amazon's interface.
• Client-side strings moved too. the Claude Code string report and the string summary both showed v2.1.190 preparing Fable-specific limits, weekly included usage, and a /usage-credits recovery path.
• User screenshots were genuine interface evidence, not proof of serving traffic. the model-picker screenshot showed Fable 5 as selectable but unavailable, while the chat screenshot showed a chat claiming to be Fable 5 before the bug explanation landed.
• By the end of the cycle, multiple early posters had corrected or deleted rollout claims, including the deleted-AWS-post follow-up and the Anthropic-confirmed debunk.

You can read the original Anthropic suspension notice, inspect the AWS Bedrock resurfacing post, compare the Claude Code string changes, and watch how model-self-identification screenshots briefly outran the actual backend state.

The core fact arrived in one line. According to the zero-traffic reply, Anthropic was serving "exactly 0 traffic" to Fable 5 and suspected a UI bug.

That statement quickly collapsed the comeback narrative. Kimmonismus's correction, TestingCatalog's summary, WesRoth's follow-up, and AI Builder Club's recap all converged on the same point: visible model surfaces did not mean a production route was live.

The strongest false-positive signal came from AWS. The Bedrock listing post said Fable 5 had reappeared in AWS docs, model cards, and data-retention docs, with IDs including anthropic.claude-fable-5 and global.anthropic.claude-fable-5.

A separate Bedrock screenshot in the access-denied test mattered more than the card itself. It showed anthropic.claude-fable-5 in the interface, but the actual invocation path returned AccessDeniedException, which fits the broader pattern: catalog visibility, no confirmed serving.

The second signal came from client strings, not traffic. The Claude Code string report showed v2.1.190 adding or rewording Fable 5 copy, and the follow-up summary extracted the concrete changes.

The new strings pointed to a more specific billing and quota model than earlier builds:

• "Fable 5 requires usage credits" string diff
• "You've reached your Fable 5 limit" new limit copy
• "You've used your included Fable 5 usage for this week" weekly allotment copy
• "Run /usage-credits to keep using Fable 5" recovery-path copy

Those strings are still evidence of preparation, not rollout. They tell you the client had logic for limits and weekly included usage, but the zero-traffic reply says there was no live traffic behind it.

The user reports were not invented. The model-picker screenshot showed Fable 5 inside Claude's selector with a "Currently unavailable" label, and the iOS recording post claimed the model worked only in selected chats.

The more confusing evidence was the self-identification screenshot, where a chat answered, "I'm running as Claude Fable 5." After Anthropic's reply, posters like the red-herring follow-up and the later recap treated those outputs as symptoms of the same UI-state bug, not proof that requests were actually routed to Fable 5.

This story moved in the usual bad order: first the sightings, then the caveats, then the debunk. An early rollout claim cited video proof, a later correction added Anthropic's message back into the thread, and a cleanup reply said the earlier AWS post had been deleted after direct confirmation.

That left one durable engineering takeaway: several surfaces could mention Fable 5 at once, including AWS cards, Claude Code strings, and app pickers, while the backend still served nothing. The official suspension notice at Anthropic's access page stayed relevant the whole time because the visible IDs and UI hooks never turned into confirmed invocations.