Claude Code Service Outage and Status Page Transparency Issues

Service Outage Details

Claude Code users reported multiple authentication failures including broken OAuth functionality, API keys expiring daily, and 500 errors or timeouts when attempting to reauthorize. The official status page at https://status.claude.com/ initially showed no issues despite users being unable to log in for at least an hour.

Status Page Transparency Concerns

Users expressed frustration that the status page didn't reflect actual service degradation. One comment noted: "The real issue isn't that Claude is down, it can happen. The problem is that the status page doesn't report anything, even if it has been impossible to log in during the past hour." The status page was eventually updated to show the issues.

User Reports and Workarounds

Service impact appeared inconsistent across regions. One user in Central Europe reported: "I just fixed something using Claude Code," while another experienced different behavior across virtual machines: "Claude Code is running just fine on one of my virtual machines. On another, it logged me out saying the OAuth token expired, and it won't log me back in due to internal server errors."

Some users suggested implementing provider-agnostic workflows as backup. One shared a simple script for toggling between backends when Claude tokens run out, using GLM-5 as an alternative. However, others noted challenges with provider normalization due to differing capabilities between models.

Broader Context on AI Service Reliability

The discussion highlighted broader concerns about AI service reliability monitoring. Users suggested the need for third-party performance testing that could provide metrics like time to first response, global capacity status, effective throttling rates, and actual intelligence metrics. One comment proposed: "There should be a very loud third party ruthlessly running continuous tests against all of them... like a leaderboard focused on actual live performance."