outages.live
Live

Mapbox

Mapbox is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

2

Days with an incident

3

Median duration

6 h 19 min

Longest incident

12 h 38 min

Components

22

Navigation

API Operational
90 days ago3 days with an incidentToday
Mobile SDK Operational
90 days agoNo incidentsToday

Maps

API Operational
90 days agoNo incidentsToday
Studio Operational
90 days agoNo incidentsToday
GL Native Operational
90 days agoNo incidentsToday
GL JS Operational
90 days agoNo incidentsToday
Mobile SDK Operational
90 days agoNo incidentsToday
Accounts Operational
90 days agoNo incidentsToday
Search Operational
90 days agoNo incidentsToday
Atlas Operational
90 days agoNo incidentsToday
Vision Operational
90 days agoNo incidentsToday
Security Operational
90 days agoNo incidentsToday

Data Services

Geodata Operational
90 days agoNo incidentsToday
Imagery Operational
90 days agoNo incidentsToday
Telemetry Operational
90 days agoNo incidentsToday
Telemetry SDK Operational
90 days agoNo incidentsToday
Mapbox Traffic Data Operational
90 days agoNo incidentsToday
Traffic Congestion Visual Layer Operational
90 days agoNo incidentsToday
Contribute Operational
90 days agoNo incidentsToday

WWW (marketing websites)

www.mapbox.jp Operational
90 days agoNo incidentsToday
www.mapbox.com Operational
90 days agoNo incidentsToday
www.mapbox.by Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 20, 2026

Duration12 h 38 min18:43 to 07:22Intermittent Routing Disruptions in US-EastDegraded

This incident has been resolved.

Oct 19, 2026

Duration1 min21:38 to 21:38Disruption in Routing Availability in US-EastNotice

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.

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane