- Level
- confirmed
- Worst impact
- Degraded
- Components
- API
- Regions
- us
What to do
Check whether you use Mapbox API in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 12h 38m it lasted.
Anything that failed between 2026-10-20 18:43 UTC and 2026-10-21 07:22 UTC may need a replay.Subscribe to Mapbox's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=mapbox works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Mapbox 3
- investigating
On October 20, 2026, between 14:45 and 15:47 UTC, temporary regional capacity constraints caused intermittent disruptions to navigation services in the US-East region. This resulted in brief, recurring periods of elevated latency and missing route results during this window. Our services have returned to normal operation, and our engineering team is continuing to investigate.
provider
- investigating
This issue has been resolved.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-40e46dc56e
Is Mapbox still down?
No, this incident was resolved 2026-10-21 07:22 UTC. For Mapbox's live state, see https://down.guide/mapbox.
How long did it last?
12h 38m, from 2026-10-20 18:43 UTC to 2026-10-21 07:22 UTC, by the times Mapbox posted.
What was affected?
Mapbox named API in us.
What caused it?
Mapbox hasn't published a root cause. If it does, it shows here.
Where does this come from?
Mapbox's official status page, https://status.mapbox.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.