Anthropic logo

Claude API disruption on 4 October 2026

Claude API from Amsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal: degraded checks; 2026-10-04 13:30 UTC to 2026-10-04 15:30 UTC: peak first visible token 8.32 s vs a usual 1.34 s.

What our checks saw
Degraded
Cities affected
Amsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal
When
to
How long
2 hours
Slowest check
8.32 s, usually 1.34 s
Anthropic's status page
Open it

Where our checks saw it

Each glowing city had slow or failing checks during the incident, shown at its worst. We test from 6 cities, so other places may have been hit too.

Our checks, city by city

Each point is one check every 30 minutes, from three hours before the incident to three hours after. Coloured points are the checks we counted as slower or failing. The shaded area shows how far above the usual time they were.

Amsterdam

Incident0 ms10.00 s20.00 s10:3013:3016:30
Each check (UTC)Usual (1.31 s)Much slower, or failingIncident
Every check as a table
Time (UTC)CheckReading
10:301.37 sNormal
11:001.19 sNormal
11:301.10 sNormal
12:001.23 sNormal
12:301.42 sNormal
13:001.40 sNormal
13:3014.17 sMuch slower, or failing
14:001.46 sNormal
14:301.39 sNormal
15:001.44 sNormal
15:301.23 sNormal
16:001.34 sNormal
16:301.17 sNormal
17:001.17 sNormal
17:301.20 sNormal
18:001.28 sNormal
18:301.32 sNormal

San Francisco

Incident0 ms7.50 s15.00 s10:3013:3016:30
Each check (UTC)Usual (1.16 s)Much slower, or failingIncident
Every check as a table
Time (UTC)CheckReading
10:301.02 sNormal
11:001.09 sNormal
11:301.04 sNormal
12:001.08 sNormal
12:301.06 sNormal
13:001.14 sNormal
13:309.35 sMuch slower, or failing
14:001.47 sNormal
14:301.23 sNormal
15:001.29 sNormal
15:301.16 sNormal
16:001.47 sNormal
16:301.08 sNormal
17:001.09 sNormal
17:301.20 sNormal
18:001.09 sNormal
18:301.07 sNormal

Montreal

Incident0 ms10.00 s20.00 s10:3013:3016:30
Each check (UTC)Usual (1.16 s)Much slower, or failingIncident
Every check as a table
Time (UTC)CheckReading
10:30993 msNormal
11:001.10 sNormal
11:301.04 sNormal
12:001.22 sNormal
12:301.08 sNormal
13:001.04 sNormal
13:3014.49 sMuch slower, or failing
14:001.39 sNormal
14:301.19 sNormal
15:001.18 sNormal
15:301.12 sNormal
16:001.34 sNormal
16:301.05 sNormal
17:001.13 sNormal
17:301.08 sNormal
18:001.07 sNormal
18:301.22 sNormal

Singapore

Incident0 ms10.00 s20.00 s10:3013:3016:30
Each check (UTC)Usual (1.33 s)Much slower, or failingIncident
Every check as a table
Time (UTC)CheckReading
10:301.23 sNormal
11:001.26 sNormal
11:301.19 sNormal
12:001.23 sOur check could not be verified
12:301.27 sNormal
13:001.39 sNormal
13:3014.30 sMuch slower, or failing
14:001.52 sNormal
14:301.43 sNormal
15:001.45 sNormal
15:301.29 sNormal
16:001.56 sNormal
16:301.32 sNormal
17:001.23 sNormal
17:301.27 sNormal
18:001.27 sNormal
18:301.25 sNormal

Tokyo

Incident0 ms7.50 s15.00 s10:3013:3016:30
Each check (UTC)Usual (1.21 s)Much slower, or failingIncident
Every check as a table
Time (UTC)CheckReading
10:301.14 sNormal
11:001.15 sNormal
11:301.17 sNormal
12:001.17 sNormal
12:301.17 sNormal
13:001.27 sNormal
13:309.31 sMuch slower, or failing
14:001.73 sNormal
14:301.39 sNormal
15:001.24 sNormal
15:301.31 sNormal
16:001.36 sNormal
16:301.14 sNormal
17:001.12 sNormal
17:301.17 sNormal
18:001.17 sNormal
18:301.32 sNormal

Mumbai

Incident0 ms10.00 s20.00 s10:3013:3016:30
Each check (UTC)Usual (1.34 s)Slower than usualMuch slower, or failingIncident
Every check as a table
Time (UTC)CheckReading
10:301.16 sNormal
11:001.35 sNormal
11:301.24 sNormal
12:001.26 sNormal
12:301.39 sNormal
13:001.82 sNormal
13:3014.35 sMuch slower, or failing
14:002.29 sSlower than usual
14:301.54 sNormal
15:001.31 sNormal
15:301.36 sNormal
16:001.47 sNormal
16:301.26 sNormal
17:001.24 sNormal
17:301.28 sNormal
18:001.34 sNormal
18:301.42 sNormal

How fast is your API around the world?

Run a free speed test from multiple cities and find out where your users are waiting. No setup, no account required.

Test my API

No account required · Takes about 30 seconds.