esm.sh disruption on 19 October 2026
esm.sh from San Francisco: degraded checks; 2026-10-19 17:00 UTC to 2026-10-19 22:00 UTC: peak response time 514 ms vs a usual 31 ms.
- What our checks saw
- Degraded
- Cities affected
- San Francisco
- When
- to
- How long
- 5 hours
- Slowest check
- 514 ms, usually 31 ms
- esm.sh'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, Montreal, Singapore, Tokyo, Mumbai.
San Francisco
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 14:00 | 29 ms | Normal |
| 14:30 | 38 ms | Normal |
| 15:00 | 40 ms | Normal |
| 15:30 | 46 ms | Normal |
| 16:00 | 459 ms | Much slower, or failing |
| 16:30 | 193 ms | Normal |
| 17:00 | 79 ms | Normal |
| 17:30 | 159 ms | Normal |
| 18:00 | 539 ms | Much slower, or failing |
| 18:30 | 488 ms | Much slower, or failing |
| 19:00 | 529 ms | Much slower, or failing |
| 19:30 | 40 ms | Normal |
| 20:00 | 511 ms | Much slower, or failing |
| 20:30 | 164 ms | Normal |
| 21:00 | 29 ms | Normal |
| 21:30 | 25 ms | Normal |
| 22:00 | 31 ms | Normal |
| 22:30 | 33 ms | Normal |
| 23:00 | 42 ms | Normal |
| 23:30 | 35 ms | Normal |
| 00:00 | 67 ms | Normal |
| 00:30 | 42 ms | Normal |
| 01:00 | 32 ms | 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.