Evidence Boundary
- Anthropic's status incident is a company acknowledgment.
- Anthropic-owned GitHub issues are public customer reports hosted by Anthropic, not company findings.
- Reddit posts and comments are third-party public claims.
- A thread may contain several reports, and the same person may have participated in more than one thread.
- The rows are not a unique-user count and the dollar figures must not be added into a single loss total.
- Community reports do not prove the separate customer's private $704.71 ledger.
Source Matrix
| Source | Publicly stated plan/usage context | Publicly claimed paid-credit impact | Evidence value |
|---|---|---|---|
| Anthropic official incident Company acknowledgment |
Users across Claude.ai, Claude Code, and other surfaces were erroneously required to use usage credits for an included model. | Anthropic later corrected an incident window; the status page does not publish account-level refund totals. | Establishes the cross-surface routing incident. |
| Anthropic-owned GitHub issue cluster Customer reports on Anthropic tracker |
Nine closely related issues were opened in 67 minutes; reports include roughly 12%, 24% session / 28% weekly, 45%, and 50% included-usage positions. |
The issues generally establish credit-gate and entitlement symptoms, not verified payment totals. | Anthropic-hosted, cross-platform chronology with duplicate clustering around the official incident. |
| r/ClaudeCode: “It's happened” Third-party claims |
Reports include unexpected card notifications and usage credits reaching 105%. |
Separate commenters claimed $50 overages, a $100 monthly usage-credit limit consumed, and another $50 limit affected. | Contemporaneous reports of automatic payment activity and substantial credit use. |
| r/ClaudeCode: credits required Third-party claims |
Multiple users said an included model suddenly required credits; one said roughly half of included usage remained. | No reliable aggregate dollar amount stated. | Direct plan-headroom contradiction. |
| r/claude: July 17/19 Third-party claims |
Paid-credit charging was reported during the outage. | One commenter claimed $287 was consumed before detection. | High-dollar incident claim requiring private verification. |
| r/ClaudeCode: “Fable gone?” Third-party claims |
Users reported remaining plan usage, a disappearing usage meter, and a switch to paid credits. | Separate comments claimed $500 consumed, a full Extra Usage budget consumed without notice, and a $6.32 charge. | Strongest public thread for scale, no-warning switching, and stated plan headroom. |
| r/claudexplorers: subscription access lost Third-party claims |
Original poster said plenty of capacity remained; another user reported no Claude Code warning before the switch. | Original poster claimed $6.32; another user reported spending several dollars. | Direct no-warning and remaining-capacity reports. |
| r/claude: removed from Max plans? Third-party claims |
Multiple mid-session reports; one user said 30% remained and another described substantial weekly capacity. |
No single reliable dollar amount. | Large contemporaneous cluster of plan-headroom reports. |
| r/Anthropic: Fable 5 issue Third-party claims |
Max 20x and Max 5x users reported credits suddenly required; one commenter said only about 6% of included usage had been consumed. |
No single reliable dollar amount. | Cross-plan corroboration of the included-usage contradiction. |
| r/ClaudeAI: pricing confusion Third-party claims |
The original post showed 75% session usage, 11% weekly usage, and usage credits off; commenters said the included model disappeared and accounts started using credits. |
Commenters said credits remained consumed after service returned; one claimed it cost about $8 to finish a task after enabling credits. | Timestamped plan-headroom, credit-state, and paid-impact detail from the incident window. |
| r/ClaudeAI: Extra Usage before quota exhaustion Third-party claims |
A Max 20x user reported 8% five-hour usage and 3% weekly usage while the app said quota was exhausted. |
The user said the app was burning usage credits; no reliable dollar total stated. | Particularly sharp included-quota contradiction with both usage windows quantified. |
| r/Anthropic: $200 credit-loss report Third-party claims |
The original poster said usage switched without warning; after model access returned, the poster said the credits had not returned. | The poster claimed to be down $200 in credits and said Fin redirected the complaint to Apple/iOS despite the credit purchase being made by debit card. | High-dollar, no-warning, unresolved-credit, and support-routing claims requiring private verification. |
What the Matrix Establishes
- Paid-credit routing was publicly reported while included-plan capacity reportedly remained.
- Users reported automatic card or auto-reload activity during the incident.
- Some users reported transitions to paid credits without a clear warning.
- Publicly claimed account impacts range from several dollars to hundreds of dollars.
- A full investigation must determine whether Anthropic reconciled complete July 17 ledgers or only a narrow incident window.
The matrix does not establish a total number of affected users or a combined loss amount. Those facts require Anthropic's internal entitlement, usage-credit, payment, and correction records.
Questions Anthropic Can Resolve
- How many accounts were routed to usage credits during the July 17 incident?
- How many auto-reloads or payment-method charges were triggered?
- How many accounts received only an account credit rather than a payment-method refund?
- Did Anthropic audit every July 17 debit or only the selected incident window?
- How many accounts showed remaining included-plan entitlement when paid-credit routing began?
- Were all affected users notified and reconciled, including users who did not open support cases?
Related Resources
Verification and Privacy
Reporters and regulators should contact individual sources privately for invoices, account state, and payment evidence. Public participants should share only aggregate amounts, plan context, correction type, and outcome. Do not publish invoice IDs, support IDs, account emails, card details, private screenshots, or complete support transcripts.