By rssfeeds-admin 
Reports began surfacing in community forums, including a thread on DesignTaxi, where users flagged inability to complete chat sessions, failed API requests, and broken response cycles. The pattern closely mirrors a string of instability incidents that have plagued Anthropic’s infrastructure throughout March and early April 2026.
What Users Are Experiencing
Affected users report requests being silently dropped where the system appears to accept a prompt but fails to return any output — alongside classic 500 Internal Server Errors that indicate backend processing failures.
Some developers using Claude Code and the API have reported that requests time out mid-session or return blank responses without any error acknowledgment.
On Downdetector during a similar April 8 incident, Claude Chat accounted for the majority of complaints, followed by the mobile app and Claude Code. The current disruption appears to follow a near-identical symptom profile, affecting both consumer-facing and developer-facing surfaces simultaneously.
This is not an isolated event. Anthropic’s own status history reveals a troubling pattern of recurring elevated error events throughout April 2026 alone. On April 10, Anthropic confirmed “elevated errors on requests to non-Opus models,” which were resolved after approximately 21 minutes of active investigation.
On April 8, Sonnet 4.6 experienced elevated error rates between 23:00 PT and 01:50 PT, while a separate authentication outage affected Claude.ai, Claude Code, and the developer console between 17:25–17:44 UTC the same day.
Earlier in April, incidents struck on April 6 and April 7, both involving elevated login and chat errors across desktop, mobile, and web surfaces. In March, a major multi-hour outage on March 2 triggered over 500/529 errors across all product surfaces, lasting nearly 10 hours before Anthropic rolled out fixes.
Anthropic’s Response
As of the time of writing, Anthropic has not posted a public incident update on status.claude.com for April 13, despite community-reported disruptions. This discrepancy between official status signals and real-world user experience has become a recurring concern among developers and enterprise teams relying on Claude’s API for production workflows.
Users experiencing issues are advised to monitor status.claude.com for real-time updates, implement exponential backoff strategies when hitting 500 or 529 error codes, and consider failover routing to alternate model endpoints during elevated error windows.
Follow us on Google News, LinkedIn, and X for daily cybersecurity updates. Contact us to feature your stories.
The post Claude AI Reportedly Down for Hundreds of Users With Intermittent 500 Errors appeared first on Cyber Security News.
Discover more from RSS Feeds Cloud
Subscribe to get the latest posts sent to your email.