esm.sh failed requests on 18 October 2026
esm.sh from Singapore: some requests failed; 2026-10-18 14:30 UTC to 2026-10-18 16:30 UTC: peak response time 52 ms vs a usual 30 ms.
- What our checks saw
- Some requests failed
- Cities affected
- Singapore
- When
- to
- How long
- 2 hours
- Slowest check
- 52 ms, usually 30 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, San Francisco, Montreal, Tokyo, Mumbai.
Singapore
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 11:30 | 141 ms | Normal |
| 12:00 | 33 ms | Normal |
| 12:30 | 35 ms | Normal |
| 13:00 | 172 ms | Some requests failed |
| 13:30 | 783 ms | Much slower, or failing |
| 14:00 | 33 ms | Normal |
| 14:30 | 31 ms | Some requests failed |
| 15:00 | 67 ms | Normal |
| 15:30 | 36 ms | Normal |
| 16:00 | 29 ms | Normal |
| 16:30 | 30 ms | Normal |
| 17:00 | 28 ms | Normal |
| 17:30 | 29 ms | Normal |
| 18:00 | 23 ms | Normal |
| 18:30 | 27 ms | Normal |
| 19:00 | 22 ms | Normal |
| 19:30 | 36 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.