Claude Status · History · Incident #6028

ACTIVE INCIDENT

Elevated errors across many models

Major · Started Jul 30, 2026 · 5:57 AM

⚡ Pulsetic detected this 580 minutes before Claude acknowledged it

Duration

Ongoing
Severity

Major
Detection lead

580 min
User reports

Peak 2/hr

Summary

Elevated errors across many models

As of 01:33 PT / 08:33 UTC we are back to errors across all models.

Started

Jul 30, 2026 · 5:57 AM
Status

Identified
Duration

Ongoing
Severity

Major

Detection lead

Pulsetic caught this 580 minutes early

Pulsetic detected

~580 min before acknowledgement

User reports and synthetic probes crossed the detection threshold
Claude acknowledged

Jul 30, 2026 · 5:57 AM

Via official status page

Event timeline

How this incident unfolded

●

Detected by Pulsetic
Jul 29 · 8:17 PM Pulsetic

User reports and synthetic probes crossed the detection threshold — 580 min before the official acknowledgement.
◐

Investigating
Jul 30 · 5:57 AM Claude

We are currently investigating this issue.
◆

Identified
Jul 30 · 6:26 AM Claude

All models except Opus 5 have recovered. We're working to recover Opus 5 as well.
◆

Identified
Jul 30 · 7:33 AM Claude

As of 7:32 UTC / 0:32 PT, Opus 5 errors are back to baseline but we're seeing again Sonnet 5's errors up.
◆

Identified
Jul 30 · 8:06 AM Claude

As of 8:05 UTC / 1:05 PT, Sonnet 5 errors are back to baseline, but we're seeing an increased error rate on Fable 5.
◆

Identified
Jul 30 · 8:33 AM Claude

As of 01:33 PT / 08:33 UTC we are back to errors across all models.

User reports · incident window

Report volume over time

Hourly report count. Red bars mark the incident window.

Peak: 2 reports/hr

← Before incident After →

Pattern

Other recent incidents

Browse full incident history →

Get alerted before the next Claude outage.

Pulsetic catches degradations minutes before vendors acknowledge them. This one: 580 minutes early.

Start monitoring free