Outage in usage reporting
Summary
This incident has been resolved. Impact: Feb 26 ~02:00 to Feb 27 06:20 UTC. Usage report API endpoints and analytics dashboards experienced errors and missing data due to an internal data service issue. All endpoints have been restored and historical data is now displaying correctly. We apologize for any inconvenience caused.
Impact
none
Timeline
[identified] We are responding to an outage in usage reporting via the Console and the admin API's /v1/organizations/usage_report endpoints. The issue has been identified and the team is working on a fix
via statuspage[identified] We are responding to an outage in usage reporting across products and APIs. The issue has been identified and the team is working on a fix
via statuspage[identified] A fix has been deployed for the /v1/organizations/usage_report/messages admin API endpoint. The team is still working on fixes for other endpoints and services
via statuspage[identified] We are responding to an outage in usage reporting across products and APIs. The issue has been identified and the team is working on a fix
via statuspage[monitoring] Usage reporting has been restored across products, but is not returning data for usage that occurred after 2026-02-25 at around 18:40 UTC. The team is able restore this data and is currently working on a fix
via statuspage[resolved] This incident has been resolved. Impact: Feb 26 ~02:00 to Feb 27 06:20 UTC. Usage report API endpoints and analytics dashboards experienced errors and missing data due to an internal data service issue. All endpoints have been restored and historical data is now displaying correctly. We apologize for any inconvenience caused.
via statuspageLessons Learned
⚠Anthropic has experienced 168 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.
📊Incidents related to network, database, api have occurred 867 times across all providers in the past year. This is one of the most common failure categories in cloud infrastructure.
💡This incident is categorized as: Database Overload, Network / Routing, API Issue. Consider implementing preventive measures specific to this failure category.
Similar Incidents
Elevated errors affecting ChatGPT
OpenAI · Jul 19, 2026
Block Storage Volume NYC1 and NYC3
DigitalOcean · Jul 19, 2026
Networking in BLR1
DigitalOcean · Jul 19, 2026
Service is operating normally: [RESOLVED] Inaccurate Estimated Billing Data
AWS · Jul 18, 2026
Some users are unable to access Codex
OpenAI · Jul 18, 2026