Claude Outage Hits Consumers First: Web and Mobile Users Face Elevated Errors While Business API Stays Online
Why this matters now: Consumers trying to access claude on web and mobile are experiencing elevated errors and timeouts, disrupting everyday workflows and apps, while businesses relying on the Claude API continue operating. That split—consumer surfaces down, business API working—shifts the immediate impact from enterprise continuity to consumer trust, customer support load, and short-term product perception.
Immediate impact for users and companies: who feels it first
Claude's consumer-facing services, including claude. ai and its apps, are experiencing partial outages that are producing failed requests, timeouts, and inconsistent responses for people using web and mobile interfaces. Businesses that depend on the Claude API remain able to make API calls, meaning commercial integrations should continue functioning even as individual users encounter interruptions.
Event details and current status
The incident was flagged on March 2, 2026. Elevated errors are appearing across platforms and the outage is affecting users broadly rather than being limited to a single app or region. The team is investigating the problem; the first "Investigating" notice went out at 11: 49 UTC, with a follow-up update at 12: 06 UTC indicating the investigation was ongoing. There is no ETA mentioned yet, though the status indicates the issue is actively being worked on.
What users are encountering right now
People trying to use Claude on web, mobile, or sometimes API may see failed requests, timeouts, or inconsistent responses. In some cases, site-level access gates are prompting interaction checks: "To continue, please click the box below to let us know you're not a robot. " Users are reminded to make sure their browser supports JavaScript and cookies and that those elements are not being blocked from loading. For inquiries related to that message, users are asked to contact support and provide the reference ID displayed.
Company response, commercial implications and uncertainty
The statement on the outage clarifies that consumer-facing surfaces are currently unavailable while the Claude API that powers business integrations is working. That dichotomy reduces immediate enterprise risk for firms using the API but raises separate issues: customer-facing products are impaired, and support teams should expect elevated volume and troubleshooting requests. There is no stated ETA for full restoration; the team is actively investigating and providing status updates at the noted timestamps.
- March 2, 2026 — incident flagged.
- 11: 49 UTC — initial "Investigating" notice issued.
- 12: 06 UTC — follow-up update confirming ongoing investigation; no ETA.
Here’s the part that matters for teams: if your service integrates with the Claude API, immediate user-facing downtime may be limited; if your product routes customers to claude. ai or consumer apps, you should prepare for intermittent failures and increased support contacts.
Quick Q&A to cut through the noise
Q: Is the business API down?
A: No — the Claude API that powers business integrations is reported to be working.
Q: Which surfaces are affected?
A: Consumer-facing surfaces such as claude. ai and mobile apps are seeing partial outages and elevated errors across platforms.
