- Level
- confirmed
- Worst impact
- Degraded
- Components
- API
- Regions
- us, us-east-1
What to do
Check whether you use Mapbox API in us, us-east-1. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 23h 56m it lasted.
Anything that failed between 2023-11-15 23:35 UTC and 2023-11-16 23:31 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
This affects live-data such as congestion, closures and incidents for Navigation apis as well as live-traffic maps. We are currently investigating the issue and have re-directed traffic to regions with complete coverage in the meantime.
provider
- monitoring
The partial live-data coverage in us-east-1 region has been mitigated, and the region is now processing client requests again. Investigation of root-cause is continuing and we're tracking key metrics.
provider
- resolved
The original issue is identified and 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-020f6e9a41
Is Mapbox still down?
No, this incident was resolved 2023-11-16 23:31 UTC. For Mapbox's live state, see https://down.guide/providers/mapbox.
How long did it last?
23h 56m, from 2023-11-15 23:35 UTC to 2023-11-16 23:31 UTC, by the times Mapbox posted.
What was affected?
Mapbox named API in us, us-east-1.
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.