outages.live
Live
MapboxIncident · 2026-10-20 18:43 UTC

Intermittent Routing Disruptions in US-East

ResolvedOfficial update

This incident has been resolved.

The latest update from Mapbox.

State

Resolved

Started

12 d ago

2026-10-20 18:43 UTC

Lasted

12 h 38 min

until 2026-10-21 07:22 UTC

Worst impact

Degraded

Timeline

3 updates
18:4321:5301:0204:1207:22
DegradedUpdate postedTimes in UTC

Investigating

12 h 38 min 100%

Updates

Times in UTC

As posted by Mapbox

Resolved2026-10-21 07:22 UTC

This incident has been resolved.

Investigating2026-10-21 07:21 UTC

This issue has been resolved.

Investigating2026-10-20 18:43 UTC

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.

Affected components

2
APINavigation - API

Mapbox in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

2

Days with an incident

3

Median duration

6 h 19 min

This incident

2.0× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

12 h 38 min
median 6 h 19 min
90 days agoToday

Other Mapbox incidents

All incidents

Mapbox·Disruption in Routing Availability in US-East

Between 19:18 and 19:41 UTC, we experienced an issue affecting the Directions API and Map Matching API in the US-East region. This caused elevated latency and missing route data for a significant portion of regional traffic. The issue has been identified and resolved, and all service metrics have fully returned to normal operation.

Resolvedresolved 13 d ago

Follow Mapbox

Your coding agent knows when Mapbox is down, and tells you when a failure is theirs, not yours. You can also get Mapbox incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "mapbox" and tell me if Mapbox has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=mapbox
Slack
/feed subscribe https://outages.cc/feed.xml?providers=mapbox

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane