DeepSeek API slowdown on 14 October 2026
DeepSeek API from Singapore: slower than usual; 2026-10-14 16:00 UTC to 2026-10-14 17:30 UTC: peak first visible token 0.81 s vs a usual 0.54 s.
- What our checks saw
- Slower than usual
- Cities affected
- Singapore
- When
- to
- How long
- 90 minutes
- Slowest check
- 810 ms, usually 539 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: Amsterdam, San Francisco, Montreal, Tokyo, Mumbai.
Singapore
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 13:00 | 809 ms | Slower than usual |
| 13:30 | 767 ms | Normal |
| 14:00 | 727 ms | Normal |
| 14:30 | 699 ms | Normal |
| 15:00 | 955 ms | Slower than usual |
| 15:30 | 784 ms | Normal |
| 16:00 | 835 ms | Slower than usual |
| 16:30 | 736 ms | Normal |
| 17:00 | 734 ms | Normal |
| 17:30 | 649 ms | Normal |
| 18:00 | 656 ms | Normal |
| 18:30 | 630 ms | Normal |
| 19:00 | 480 ms | Normal |
| 19:30 | 435 ms | Normal |
| 20:00 | 677 ms | Normal |
| 20:30 | 879 ms | Slower than usual |
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.