Anthropic: Elevated errors on platform.claude.com
Affected scope is described in the vendor notice; service-wide impact is not established.
official status feed · checked 3m ago · vendor posted 2d ago
This vendor notice needs independent evidence matching its issue and affected scope to clear the two-source gate.
These services share one vendor status page, and each shows this same notice, so it is listed once.
Anthropic
Source: vendor:status.anthropic.com
- Independent origins
- 1
- Corroborating signals
- 1 evidence row
- Vendor claim
- a major-impact incident
- Our evidence-based assessment
- minorgraded from this incident’s evidence · Oct 7, 2026 13:28 UTC
The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.
Observed health
Unknown
No samples qualify for a combined success and latency score.
Evidence strength
Vendor-reported
An official notice is available; independent agreement is unproven.
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.
Claude
Source: status.anthropic.com
- Independent origins
- 0
- Corroborating signals
- None in current evidence
- Vendor claim
- a major-impact incident
- Our evidence-based assessment
- minorgraded from this incident’s evidence · Oct 7, 2026 13:40 UTC
The assessment is a measurement of this incident’s evidence. It does not change PulseWatch’s detection decision, the recorded severity, or who is alerted.
Observed health
Unknown
No samples qualify for a combined success and latency score.
Evidence strength
Vendor-reported
An official notice is available; independent agreement is unproven.
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.
