Claude API disruption on 20 October 2026

Claude API from Amsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal: degraded checks; 2026-10-20 14:30 UTC to 2026-10-20 16:30 UTC: peak first visible token 14.53 s vs a usual 1.01 s.

What our checks saw: Degraded
Cities affected: Amsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal
When: 20 Oct, 14:30 UTC to 20 Oct, 16:30 UTC
How long: 2 hours
Slowest check: 14.53 s, usually 1.01 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 60 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

Each check (UTC)Usual (1.01 s)Slow check outside the incidentIncident

Every check as a table

Time (UTC)	Check	Reading
11:30	1.09 s	No check
12:30	1.16 s	No check
13:30	1.21 s	Normal
14:30	1.14 s	No check
15:30	14.70 s	No check
16:30	14.36 s	Much slower, or failing
17:30	1.06 s	Normal
18:30	1.33 s	Normal
19:30	1.08 s	Normal
20:30	1.08 s	Normal
21:30	1.26 s	Normal
22:30	1.31 s	Normal
23:30	950 ms	Normal
00:30	984 ms	Normal
01:30	970 ms	Normal
02:30	975 ms	Normal

San Francisco

Each check (UTC)Usual (926 ms)Slow check outside the incidentIncident

Every check as a table

Time (UTC)	Check	Reading
11:30	1.02 s	No check
12:30	1.19 s	No check
13:30	1.06 s	Normal
14:30	1.10 s	No check
15:30	14.14 s	No check
16:30	9.01 s	Much slower, or failing
17:30	974 ms	Normal
18:30	1.09 s	Normal
19:30	1.04 s	Normal
20:30	1.06 s	Normal
21:30	1.06 s	Normal
22:30	1.02 s	Normal
23:30	883 ms	Normal
00:30	916 ms	Normal
01:30	916 ms	Normal
02:30	883 ms	Normal

Montreal

Each check (UTC)Usual (903 ms)Slow check outside the incidentIncident

Every check as a table

Time (UTC)	Check	Reading
11:30	1.14 s	No check
12:30	1.27 s	No check
13:30	982 ms	Normal
14:30	1.19 s	No check
15:30	10.60 s	No check
16:30	4.51 s	Much slower, or failing
17:30	921 ms	Normal
18:30	1.31 s	Normal
19:30	1.09 s	Normal
20:30	971 ms	Normal
21:30	1.05 s	Normal
22:30	1.07 s	Normal
23:30	859 ms	Normal
00:30	881 ms	Normal
01:30	912 ms	Normal
02:30	913 ms	Normal

Singapore

Each check (UTC)Usual (1.08 s)Slow check outside the incidentIncident

Every check as a table

Time (UTC)	Check	Reading
11:30	1.19 s	No check
12:30	1.32 s	No check
13:30	1.22 s	Normal
14:30	1.39 s	No check
15:30	11.00 s	No check
16:30	8.98 s	Much slower, or failing
17:30	1.15 s	Normal
18:30	1.37 s	Normal
19:30	1.22 s	Normal
20:30	1.21 s	Normal
21:30	1.20 s	Normal
22:30	1.16 s	Normal
23:30	1.05 s	Normal
00:30	1.08 s	Normal
01:30	1.04 s	Normal
02:30	1.12 s	Normal

Tokyo

Each check (UTC)Usual (1.01 s)Slow check outside the incidentIncident

Every check as a table

Time (UTC)	Check	Reading
11:30	1.12 s	No check
12:30	1.23 s	No check
13:30	1.19 s	Normal
14:30	1.19 s	No check
15:30	14.49 s	No check
16:30	14.35 s	Much slower, or failing
17:30	994 ms	Normal
18:30	1.38 s	Normal
19:30	1.19 s	Normal
20:30	1.10 s	Normal
21:30	1.12 s	Normal
22:30	1.06 s	Normal
23:30	980 ms	Normal
00:30	951 ms	Normal
01:30	949 ms	Normal
02:30	1.07 s	Normal

Mumbai

Each check (UTC)Usual (1.11 s)Slow check outside the incidentIncident

Every check as a table

Time (UTC)	Check	Reading
11:30	1.25 s	No check
12:30	1.35 s	No check
13:30	1.30 s	Normal
14:30	1.46 s	No check
15:30	14.52 s	No check
16:30	14.21 s	Much slower, or failing
17:30	1.13 s	Normal
18:30	1.39 s	Normal
19:30	1.29 s	Normal
20:30	1.24 s	Normal
21:30	1.20 s	Normal
22:30	1.21 s	Normal
23:30	1.10 s	Normal
00:30	1.10 s	Normal
01:30	1.12 s	Normal
02:30	1.10 s	Normal

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.