Mapbox Outage History
6 incidents recorded over the last 365 days, 6 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Mapbox Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jun 29, 2026 | Elevated Rate of Partial Response (206) and Not Found (404) Errors in the Search Box APIThis incident has been resolved. | 6h 22m | Resolved |
| Feb 10, 2026 | Degraded live traffic in EuropeThe incident is resolved as of 05:13 UTC. Affected services are now fully operational. | 17h 7m | Resolved |
| Dec 6, 2025 | Delayed delivery of Mapbox Traffic DataThis incident has been resolved. | 70h 22m | Resolved |
| Nov 29, 2025 | High failure rate for live traffic tile requestsThis incident has been resolved. | 44 min | Resolved |
| Oct 20, 2025 | AWS outage impacting Mapbox core servicesThis incident has been resolved. | 13h 41m | Resolved |
| Oct 14, 2025 | Elevated level of partial response in Search Box APIFrom 2025/10/14 05:37 UTC to 2025/10/14 06:29 UTC, we experienced elevated levels of 206 Partial Content responses on the Search Box APIs due to a lack of POI results in the search. | 0 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Mapbox incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Mapbox Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Mapbox acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Mapbox outage in this window ran 2d 22h, against a mean recovery of 18h 3m. If you depend on Mapbox in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.