PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Claude is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Claude. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Claude issues today?

As of Sep 28, 2026 08:03 UTC, 0 users had reported issues with Claude in the previous 24 hours.

How can I report a Claude outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Productivity

Is Claude down right now?

NormalOfficial status last polled Sep 28, 2026 07:43 UTCclaude.ai Official status page

Claude AI assistant and Anthropic API platform availability.

Are you on the Claude team and see something inaccurate? Report it to us. We respond within one business day.

Is Claude down right now?

No. Claude has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Sep 28, 2026 08:03 UTC

Normal

Claude is operating normally

As of Sep 28, 2026 08:03 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

Sep 22, 2026 03:46 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Claude.

Incident days

No recorded incident

63h 21m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Claude. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

1 incident

Busiest day

63h 21m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Claude outage on September 22 2h 6m disruption

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

A high-severity disruption was detected for the Claude service. This incident was identified through automated monitoring signals, including the vendor's status page. The disruption lasted for 2 hours and 6 minutes, resolving on September 22, 2026, at 03:46 UTC.

Peak reports

in 15 min

Total reports

during outage

Duration

2h 6m

until recovery

Impact

The Claude service experienced a high-severity disruption for a duration of 2 hours and 6 minutes. This incident was detected by automated monitoring systems. No user-reported data was collected for this incident, and therefore no information regarding specific affected regions or issue types is available from user reports. The impact was assessed based on the service's operational status during the outage window.

Outage timeline

Sep 22, 01:40 AM
PulseWatch detected the incident from automated vendor and probe signals (high severity)
Sep 22, 01:40 AM
Status updated: possible issue
Sep 22, 03:46 AM
Signals cleared — incident resolved

Official updates

Sep 22, 01:40 AM
Claude status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

91.2%

90-day uptime

0.0%

Calculated from Claude's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other productivity services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedHigh

Claude: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Claude or have an alert rule on it can be alerted, labelled vendor-reported.

9/22/2026, 1:40:40 AM · 2h 6m

01:40 AM03:46 AM

Detection9/22/2026, 1:40:40 AM · 6d ago

Detected — high severity

ResolvedHigh

Claude: the vendor reports a major disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

9/12/2026, 8:56:48 AM · 2d 10h

08:56 AM07:02 PM

Detection9/12/2026, 8:56:48 AM · 15d ago

Detected — high severity

Claude: the vendor reports a major disruption on its own status page. Single origin, not independently confirmed; no customer alert is sent until a second independent source agrees.

ResolvedMedium

Claude incident correlated across 2 signal groups: official/vendor, social chatter.

9/3/2026, 1:43:03 PM · 3h 9m

01:43 PM04:52 PM

Detection9/3/2026, 1:43:03 PM · 24d ago

Detected — medium severity

Claude incident correlated across 2 signal groups: official/vendor, social chatter.

ResolvedMedium

Claude incident correlated across 1 signal group: official/vendor.

8/14/2026, 6:29:42 PM · 2h 13m

06:29 PM08:42 PM

Detection8/14/2026, 6:29:42 PM · 1mo ago

Detected — medium severity

Claude incident correlated across 1 signal group: official/vendor.

ResolvedMedium

Claude incident correlated across 1 signal group: official/vendor.

8/14/2026, 12:38:26 AM · 40 min

12:38 AM01:18 AM

Detection8/14/2026, 12:38:26 AM · 1mo ago

Detected — medium severity

Claude incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Claude enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

0 reports aggregated in last 24h
Crowdsourced baseline detection
Official status page

Live signal

Status: Normal
Monitoring: Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage: Verified against the vendor's own incident history
Reports (24h): 0
Baseline / hour: 5
Open threshold: 3x

Official site

claude.ai

Related services

15Five

Productivity

Unknown

ADP

Productivity

Unknown

ADP Workforce Now

Productivity

Unknown