Skip to content
Back to ClaudeIncident Postmortem
Claude logo

Claude

Tracked by PulseWatch

Auto-drafted postmortem

Claude outage on April 30 — 105d 17h disruption

Apr 30, 01:10 PM → Aug 14, 07:00 AM · 105d 17h · high

On April 30, 2026, the Claude service experienced an outage. This incident was detected due to an elevated volume of user reports. The service was fully resolved on August 14, 2026.

Peak reports
8
in 15 min
Total reports
571
during the incident
Duration
105d 17h
tracked by PulseWatch

Impact

Users reported a range of issues affecting the Claude service. The incident was characterized by a total of 571 user reports, with a peak of 8 reports within a 15-minute period. The most frequently reported issues included slow or unresponsive service, website down reports, and various API-related problems, including specific AI API issues. No specific regional impact was recorded during this period.

Top reported issues

  • Slow / unresponsive280
  • Website down226
  • API issues53
  • AI API issues9

Incident timeline

  1. Apr 30, 01:10 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 1, 01:45 PM

    Peak of 18 reports in 15 minutes (baseline 1.3)

  3. Aug 14, 07:00 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. Apr 30, 01:10 PM

    Claude status page acknowledged the incident.

    View official source
  2. Aug 14, 07:00 AM

    AI API issues clustered from 2 sources across 8 signals. Suppressed 7 redundant alerts and flagged flapping behavior.

Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals and the sources listed above.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash