Anthropic logo

Claude API disruption on 29 October 2026

Claude API from Amsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal: degraded checks; 2026-10-29 06:30 UTC to 2026-10-29 13:00 UTC: peak first visible token 2.48 s vs a usual 930 ms.

What our checks saw
Degraded
Cities affected
Amsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal
When
to
How long
6.5 hours
Slowest check
2.48 s, usually 930 ms
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 s03:3006:3009:3012:3015:30
Each check (UTC)Usual (1.04 s)Much slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
03:30891 msNormal
04:00895 msNormal
04:30899 msNormal
05:001.03 sNormal
05:30992 msNormal
06:001.03 sNormal
06:30–Much slower, or failing
07:00–Much slower, or failing
07:30–Much slower, or failing
08:00–Much slower, or failing
08:30–Much slower, or failing
09:00–Much slower, or failing
09:30–Much slower, or failing
10:00–Much slower, or failing
10:30–Much slower, or failing
11:001.31 sNormal
11:301.03 sNormal
12:001.00 sNormal
12:301.34 sNormal
13:00969 msNormal
13:303.15 sMuch slower, or failing
14:00964 msNormal
14:30987 msNormal
15:0014.03 sMuch slower, or failing
15:301.12 sNormal
16:001.65 sSlower than usual

San Francisco

Incident0 ms7.50 s15.00 s03:3006:3009:3012:3015:30
Each check (UTC)Usual (951 ms)Much slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
03:30801 msNormal
04:00835 msNormal
04:30861 msNormal
05:00980 msNormal
05:30922 msNormal
06:00933 msNormal
06:30–Much slower, or failing
07:00–Much slower, or failing
07:30–Much slower, or failing
08:00–Much slower, or failing
08:30–Much slower, or failing
09:00–Much slower, or failing
09:30–Much slower, or failing
10:00–Much slower, or failing
10:30–Much slower, or failing
11:001.26 sNormal
11:30949 msNormal
12:00928 msNormal
12:301.19 sNormal
13:00858 msNormal
13:301.67 sSlower than usual
14:00914 msNormal
14:30938 msNormal
15:009.46 sMuch slower, or failing
15:301.06 sNormal
16:001.51 sSlower than usual

Montreal

Incident0 ms7.50 s15.00 s03:3006:3009:3012:3015:30
Each check (UTC)Usual (931 ms)Much slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
03:30806 msNormal
04:00820 msNormal
04:30814 msNormal
05:001.09 sNormal
05:30900 msNormal
06:00902 msNormal
06:30–Much slower, or failing
07:00–Much slower, or failing
07:30–Much slower, or failing
08:00–Much slower, or failing
08:30–Much slower, or failing
09:00–Much slower, or failing
09:30–Much slower, or failing
10:00–Much slower, or failing
10:30–Much slower, or failing
11:002.48 sMuch slower, or failing
11:30912 msNormal
12:00896 msNormal
12:301.18 sNormal
13:00852 msNormal
13:301.93 sSlower than usual
14:00958 msNormal
14:30903 msNormal
15:0013.57 sMuch slower, or failing
15:301.00 sNormal
16:001.71 sSlower than usual

Singapore

Incident0 ms10.00 s20.00 s03:3006:3009:3012:3015:30
Each check (UTC)Usual (1.08 s)Much slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
03:30977 msNormal
04:00975 msNormal
04:30991 msNormal
05:001.14 sNormal
05:301.09 sNormal
06:001.07 sNormal
06:30–Much slower, or failing
07:00–Much slower, or failing
07:30–Much slower, or failing
08:00–Much slower, or failing
08:30–Much slower, or failing
09:00–Much slower, or failing
09:30–Much slower, or failing
10:00–Much slower, or failing
10:30–Much slower, or failing
11:001.39 sNormal
11:301.19 sNormal
12:001.04 sNormal
12:301.31 sNormal
13:001.07 sNormal
13:301.62 sNormal
14:001.13 sNormal
14:301.12 sNormal
15:0013.99 sMuch slower, or failing
15:301.21 sNormal
16:001.54 sNormal

Tokyo

Incident0 ms10.00 s20.00 s03:3006:3009:3012:3015:30
Each check (UTC)Usual (1.03 s)Much slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
03:30922 msNormal
04:00912 msNormal
04:30913 msNormal
05:001.07 sNormal
05:30972 msNormal
06:001.00 sNormal
06:30–Much slower, or failing
07:00–Much slower, or failing
07:30–Much slower, or failing
08:00–Much slower, or failing
08:30–Much slower, or failing
09:00–Much slower, or failing
09:30–Much slower, or failing
10:00–Much slower, or failing
10:30–Much slower, or failing
11:001.34 sNormal
11:301.08 sNormal
12:00980 msNormal
12:301.33 sNormal
13:001.03 sNormal
13:302.04 sSlower than usual
14:001.04 sNormal
14:301.02 sNormal
15:0013.96 sMuch slower, or failing
15:301.14 sNormal
16:001.61 sSlower than usual

Mumbai

Incident0 ms10.00 s20.00 s03:3006:3009:3012:3015:30
Each check (UTC)Usual (1.14 s)Much slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
03:301.04 sNormal
04:001.05 sNormal
04:301.01 sNormal
05:001.18 sNormal
05:301.09 sNormal
06:001.10 sNormal
06:30–Much slower, or failing
07:00–Much slower, or failing
07:30–Much slower, or failing
08:00–Much slower, or failing
08:30–Much slower, or failing
09:00–Much slower, or failing
09:30–Much slower, or failing
10:00–Much slower, or failing
10:30–Much slower, or failing
11:001.43 sNormal
11:301.15 sNormal
12:001.08 sNormal
12:301.38 sNormal
13:001.16 sNormal
13:302.43 sSlower than usual
14:001.08 sNormal
14:301.17 sNormal
15:0014.14 sMuch slower, or failing
15:301.21 sNormal
16:001.54 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.