- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Mapbox. 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 0m it lasted.
Anything that failed between 2025-06-03 02:07 UTC and 2025-06-02 19:00 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 1
- resolved
On June 2, 2025, between approximately 19:05 and 22:30 UTC, an issue occurred preventing live speed and incident data from being served to Traffic Maps v1 and some customers using the Matrix API. This impacted services reliant on real-time traffic updates. Customers using Traffic Maps v1, experienced delayed live traffic updates. ETAs from the Matrix API provided during the incident period were based on traffic data from around 20:00 UTC, and did not reflect changes in traffic conditions until service restoration. This issue is now resolved and all services are restored.
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-b6eadb7279
Is Mapbox still down?
No, this incident was resolved 2025-06-02 19:00 UTC. For Mapbox's live state, see https://down.guide/mapbox.
How long did it last?
0m, from 2025-06-03 02:07 UTC to 2025-06-02 19:00 UTC, by the times Mapbox posted.
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.