Case · 2026-10-07

The usage page could not load the usage

The meter broke. The work did not. You just could not see the bill accruing.

Summary: From 00:00 to 01:40 UTC on 7 Oct 2026 many requests to load usage data on platform.claude.com and the Admin API usage report returned errors. Messages API requests were not affected. A later same-day incident left recent usage delayed by about 30 minutes while a full fix was still in progress.

Source: status.claude.com · 7 Oct 2026

What landed

Two console usage incidents on 7 Oct 2026.

First, elevated errors loading usage data. Investigating at 01:20 UTC: errors on the platform.claude.com Usage page and the Admin API usage report since 5pm PT. Messages API requests were not affected.

Resolved at 02:33 UTC. Window: 17:00 PT on 6 Oct / 00:00 UTC on 7 Oct to 18:40 PT on 6 Oct / 01:40 UTC on 7 Oct.

Later the same day, elevated errors on platform.claude.com covered the Usage page, Rate limits page, and Admin API usage report again. By 21:44 UTC those errors were mitigated. Status said the most recent ~30 minutes of usage may take longer to appear while a full fix was still in progress. API requests were not affected.

Affected component for both: Claude Console.

Why it matters

Spend and rate decisions depend on that page. A dark usage report is how teams guess their way into the next cap, including the false spend-limit pause filed the same evening.

Satire margin

Core functionality is fine. The part that tells you whether you can afford core functionality is not.

Primary sources

• Status: elevated errors loading usage data (resolved 02:33 UTC)
• Status: usage data errors, mitigated with a 30 minute lag

← Timeline· All cases· See a sibling failure? Submit it