Claude Status · History · Incident #4869

RESOLVED

Elevated error rate across multiple models

Critical · Started Jun 23, 2026 · 2:19 PM

⚡ Pulsetic detected this 400 minutes before Claude acknowledged it

Duration

2h 25m
Severity

Critical
Detection lead

400 min
User reports

Peak 263/hr

Summary

Elevated error rate across multiple models

This incident has been resolved.

Started

Jun 23, 2026 · 2:19 PM
Resolved

Jun 23, 2026 · 4:44 PM
Duration

2h 25m
Severity

Critical

Detection lead

Pulsetic caught this 400 minutes early

Pulsetic detected

~400 min before acknowledgement

User reports and synthetic probes crossed the detection threshold
Claude acknowledged

Jun 23, 2026 · 2:19 PM

Via official status page

Event timeline

How this incident unfolded

●

Detected by Pulsetic
Jun 23 · 7:39 AM Pulsetic

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

Investigating
Jun 23 · 2:19 PM Claude

We are currently investigating this issue.
◆

Identified
Jun 23 · 2:25 PM Claude

The issue has been identified and a fix is being implemented.
◉

Monitoring
Jun 23 · 2:53 PM Claude

A fix has been implemented and we are monitoring the results.
◉

Monitoring
Jun 23 · 3:28 PM Claude

We are continuing to monitor for any further issues.
◉

Monitoring
Jun 23 · 4:05 PM Claude

We have seen error rates broadly return to normal success levels across all models. We saw elevated error rates on requests to multiple models from 7:08am PT / 14:08 UTC through 8:33am PT / 15:33 UTC.
✓

Resolved
Jun 23 · 4:44 PM Claude

This incident has been resolved.

User reports · incident window

Report volume over time

Hourly report count. Red bars mark the incident window.

Peak: 263 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: 400 minutes early.

Start monitoring free