Mapbox: Elevated latency and error rates on Maps API
Timeline of updates
- resolved
Between 23:30 UTC 13 February 2017 and 5:00 UTC 14 February 2017, an upstream service provider experienced a networking device failure that resulted in increased packet loss in their Eastern U.S. region. To mitigate the impact for Mapbox users, we redirected portions of our traffic away from the affected region to our secondary data store in a different region. The impact on our Maps API was elevated p90 latency for some requests; our global error rate remained normal for the duration of the event.
From Mapbox’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.mapbox.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Mapbox, started 2017-02-14 04:06 UTC, resolved after 1.4 h, 1 update(s).
- Title
- Elevated latency and error rates on Maps API
- Vendor
- Mapbox
- Date
- URL
- https://rewindex.com/company/mapbox/incidents/1l32w2tr4h5b
Mapbox profileRecent Mapbox incidentsAll outages on February 14, 2017Mapbox in February 2017MarkdownJSON