DeepSeek logo

DeepSeek API slowdown on 19 November 2026

DeepSeek API from Amsterdam, Mumbai, Singapore, Tokyo, Montreal: slower than usual; 2026-11-19 00:00 UTC to 2026-11-19 03:00 UTC: peak first visible token 1.45 s vs a usual 817 ms.

What our checks saw
Slower than usual
Cities affected
Amsterdam, Mumbai, Singapore, Tokyo, Montreal
When
to
How long
3 hours
Slowest check
1.45 s, usually 817 ms
DeepSeek'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. Not affected: San Francisco.

Amsterdam

Incident0 ms1.00 s2.00 s21:0000:0003:00
Each check (UTC)Usual (780 ms)Slower than usualIncident
Every check as a table
Time (UTC)CheckReading
21:00780 msNormal
21:30930 msNormal
22:00695 msNormal
22:30717 msNormal
23:00587 msNormal
23:30642 msNormal
00:001.78 sSlower than usual
00:30946 msNormal
01:001.12 sNormal
01:301.03 sNormal
02:00764 msNormal
02:30862 msNormal
03:00839 msNormal
03:30696 msNormal
04:00733 msNormal
04:30962 msNormal
05:00838 msNormal
05:30794 msNormal

Montreal

Incident0 ms1.25 s2.50 s21:0000:0003:00
Each check (UTC)Usual (817 ms)Slower than usualIncident
Every check as a table
Time (UTC)CheckReading
21:00772 msNormal
21:30717 msNormal
22:00959 msNormal
22:30892 msNormal
23:00711 msNormal
23:30775 msNormal
00:001.96 sSlower than usual
00:30936 msNormal
01:001.79 sSlower than usual
01:30812 msNormal
02:00775 msNormal
02:30804 msNormal
03:00925 msNormal
03:30819 msNormal
04:00752 msNormal
04:30916 msNormal
05:00821 msNormal
05:30807 msNormal

Singapore

Incident0 ms1.00 s2.00 s21:0000:0003:00
Each check (UTC)Usual (599 ms)Slower than usualMuch slower, or failingIncident
Every check as a table
Time (UTC)CheckReading
21:00469 msNormal
21:30356 msNormal
22:00471 msNormal
22:30506 msNormal
23:00553 msNormal
23:30646 msNormal
00:001.60 sMuch slower, or failing
00:30499 msNormal
01:00949 msSlower than usual
01:30799 msNormal
02:00578 msNormal
02:30579 msNormal
03:00402 msNormal
03:30528 msNormal
04:00595 msNormal
04:30390 msNormal
05:00406 msNormal
05:30513 msNormal

Tokyo

Incident0 ms1.00 s2.00 s21:0000:0003:00
Each check (UTC)Usual (669 ms)Slower than usualMuch slower, or failingIncident
Every check as a table
Time (UTC)CheckReading
21:00629 msNormal
21:30715 msNormal
22:00784 msNormal
22:30652 msNormal
23:00632 msNormal
23:30812 msNormal
00:001.72 sMuch slower, or failing
00:30733 msNormal
01:001.35 sSlower than usual
01:30652 msNormal
02:00888 msNormal
02:30572 msNormal
03:00624 msNormal
03:30649 msNormal
04:00822 msNormal
04:30875 msNormal
05:00617 msNormal
05:30607 msNormal

Mumbai

Incident0 ms1.00 s2.00 s21:0000:0003:00
Each check (UTC)Usual (666 ms)Slower than usualIncident
Every check as a table
Time (UTC)CheckReading
21:00647 msNormal
21:30806 msNormal
22:00346 msNormal
22:30430 msNormal
23:00608 msNormal
23:30653 msNormal
00:001.51 sSlower than usual
00:30687 msNormal
01:001.40 sSlower than usual
01:30914 msNormal
02:00873 msNormal
02:30767 msNormal
03:00611 msNormal
03:30632 msNormal
04:00619 msNormal
04:30735 msNormal
05:00659 msNormal
05:30573 msNormal

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.