Skip to content
Back to ClaudeIncident Postmortem
Claude logo

Claude

Reported by the vendor · tracked by PulseWatch

Auto-drafted postmortem

Claude: vendor-reported major incident on September 22 (tracked 2h 6m)

Sep 22, 01:40 AM → Sep 22, 03:46 AM · 2h 6m · high

Claude reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 2h 6m, from Tue, 22 Sep 2026 01:40:40 GMT to Tue, 22 Sep 2026 03:46:49 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration
2h 6m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

  1. Sep 22, 01:40 AM

    The vendor reported a major-impact incident on its own status page; PulseWatch began tracking it

  2. Sep 22, 01:40 AM

    Status updated: possible issue

  3. Sep 22, 03:46 AM

    PulseWatch closed the incident

Official updates

  1. Sep 22, 01:40 AM

    Claude reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: fallback