Dev APIs / Maps API / Mapbox

Mapbox

OPERATIONAL

Since May 2023 · 50 incidents · status.mapbox.com · checked just now

User reportsVisitors who said it's down for them, per hour over 24 hours. Not from the status page. Never counted in grades.
…
GradeCLast 90 days
CPRODA+SHIP

Overview

Admitted uptimeCustomer time not hit, by the provider's own account. Regional and partial incidents count in part.
99.912%Grade C
IncidentsEverything posted on the status page except scheduled maintenance.
20 Sev 1
Fully downMost customers down, by the provider's own account.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
12h 38m
LongestLongest Sev 1–2 incident, start to resolved.
12h 38m
Since lastTime since the last counted incident was resolved.
3d 8h

By area

CProduction
2INCIDENTS
12h 38mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 2Oct 20, 2026 · 12h 38m · regionalIntermittent Routing Disruptions in US-East
SEV 2Oct 19, 2026 · 0m · regionalDisruption in Routing Availability in US-East
Most hit
Navigation - API2
Worse. 3 in the last 6 months, 2 in the 6 before.
A+Shipping
0INCIDENTS
0mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90dNothing.
0 in the last 6 months, 0 in the 6 before.
CleanSev 3–4Sev 1–2No data

Trend, last 12 months

3 in the last 6 months, 3 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down2
Sev 3 · Can't shipCan't deploy, build or manage it0
Sev 4 · PapercutDocs, status page, slow dashboard0

When it breaks

Start times, last 12 months, UTC.

What breaks

Navigation - API2 incidents
Data Services - Mapbox Traffic Data2 incidents
Search1 incident
Data Services - Traffic Congestion Visual Layer1 incident
Maps - API1 incident

Communication

Updates eachStatus page updates per incident, on average.
4.0Last 12 months
Update gapMedian time between status page updates during an incident.
2h 33mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 5Sev 1–2

Incident history

Oct 20, 202612h 38mSEV 2
Intermittent Routing Disruptions in US-EastNavigation API requests in US-East had elevated latency and missing route results for about an hour; other regions were not reported affected.AI-graded · regional · Navigation - API
Why this grade
  1. RULES · SEV 2
    Sev 2 because Navigation - API had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · HIGH CONFIDENCE
    Navigation API requests in US-East had elevated latency and missing route results for about an hour; other regions were not reported affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 18:43 UTC · investigating
    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.
  2. 07:21 UTC · investigating
    This issue has been resolved.
  3. 07:22 UTC · resolved
    This incident has been resolved.
Oct 19, 20260mSEV 2
Disruption in Routing Availability in US-EastDirections and Map Matching APIs had elevated latency and missing route data in US-East for about 23 minutes; other regions were unaffected.AI-graded · regional · Navigation - API
Why this grade
  1. RULES · SEV 2
    Sev 2 because Navigation - API had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · HIGH CONFIDENCE · BACK AFTER 0M
    Directions and Map Matching APIs had elevated latency and missing route data in US-East for about 23 minutes; other regions were unaffected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
1 update
  1. 21:38 UTC · resolved
    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.
Jun 29, 20266h 22mSEV 2
Elevated Rate of Partial Response (206) and Not Found (404) Errors in the Search Box APISearch Box API returned elevated partial (206) and not-found (404) responses for about six hours; other Mapbox APIs were not reported affected.AI-graded · one model or feature · Search
Why this grade
  1. RULES · SEV 1
    Sev 1 because Search had a partial outage
  2. CLAUDE · SEV 2 · SINGLE · MEDIUM CONFIDENCE
    Search Box API returned elevated partial (206) and not-found (404) responses for about six hours; other Mapbox APIs were not reported affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 08:53 UTC · investigating
    Starting at 2026-06-29 00:00 UTC, the Search Box API began returning elevated rates of 206 (Partial Content) and 404 (Not Found) responses.
  2. 09:03 UTC · identified
    A mitigation was deployed at 01:35 UTC, which has reduced the impact, and we are actively working to fully resolve the issue.
  3. 15:15 UTC · resolved
    This incident has been resolved.
Feb 10, 202617h 08mSEV 2
Degraded live traffic in EuropeLive traffic speeds, routing and ETA calculations degraded across Europe for about 25 hours due to a third-party data provider outage.AI-graded · regional · Data Services - Mapbox Traffic Data +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because Data Services - Mapbox Traffic Data had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Live traffic speeds, routing and ETA calculations degraded across Europe for about 25 hours due to a third-party data provider outage.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 17:23 UTC · identified
    Since 04:40 UTC, a data provider outage has caused degraded performance for traffic-related services in the Europe. This impacts live speeds, routing, and ETA calculations. We are working closely with the data provider and will provide updates as the services stabilize.
  2. 19:56 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 10:31 UTC · resolved
    The incident is resolved as of 05:13 UTC. Affected services are now fully operational.
Dec 6, 20252d 22hSEV 4
Delayed delivery of Mapbox Traffic DataMapbox Traffic Data delivery was delayed for an unstated period and scope; the text gives no detail on who was hit.AI-graded · Data Services - Mapbox Traffic Data
Why this grade
  1. RULES · SEV 2
    Sev 2 because Data Services - Mapbox Traffic Data had degraded performance
  2. CLAUDE · SEV 4 · UNCLEAR · LOW CONFIDENCE
    Mapbox Traffic Data delivery was delayed for an unstated period and scope; the text gives no detail on who was hit.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 00:46 UTC · identified
    We are experiencing delays in delivering typical Mapbox Traffic Data. We have implemented a fix and are working to resolve.
  2. 23:08 UTC · resolved
    This incident has been resolved.
Nov 29, 202545mSEV 2
High failure rate for live traffic tile requestsLive traffic tile requests in the Maps API had a high failure rate for about 45 minutes; other Maps products were not named as affected.AI-graded · one model or feature · Maps - API
Why this grade
  1. RULES · SEV 1
    Sev 1 because Maps - API had a partial outage
  2. CLAUDE · SEV 2 · SINGLE · MEDIUM CONFIDENCE
    Live traffic tile requests in the Maps API had a high failure rate for about 45 minutes; other Maps products were not named as affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
3 updates
  1. 03:09 UTC · investigating
    Customers are experiencing high failure rates for live traffic tile requests. We are currently investigating the issue.
  2. 03:36 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 03:54 UTC · resolved
    This incident has been resolved.
Oct 20, 202513h 41mSEV 2
AWS outage impacting Mapbox core servicesAn AWS outage degraded Mapbox Maps API, Navigation API, Telemetry and Traffic Data services from about 10:59 to 00:40 UTC on 20-21 October 2025. Mapbox reported errors and degraded performance, monitored data pipeline recovery after AWS recovered, and resolved the incident at 00:40 UTC.AI-graded · Maps - API +3
Why this grade
  1. RULES · SEV 2
    Sev 2 because Maps - API had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Maps and Navigation API requests and Traffic Data services hit errors and degraded performance for about 14 hours during an AWS outage.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
4 updates
  1. 10:59 UTC · identified
    We have received reports from AWS that multiple core services are experiencing instability. This is currently impacting multiple Mapbox services with degraded performance and errors. While AWS systems are currently recovering, we are working on restoring health of impacted Mapbox services.
  2. 23:55 UTC · monitoring
    We are monitoring the recovery of Mapbox services and data pipelines after the cloud provider outage.
  3. 00:12 UTC · monitoring
    We are continuing to monitor for any further issues.
  4. 00:40 UTC · resolved
    This incident has been resolved.
Oct 14, 20250mSEV 2
Elevated level of partial response in Search Box APISearch Box API returned partial results for about 52 minutes due to missing POI data; the text does not say how widely.AI-graded · Search
Why this grade
  1. RULES · SEV 2
    Sev 2 because Search had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Search Box API returned partial results for about 52 minutes due to missing POI data; the text does not say how widely.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
1 update
  1. 09:48 UTC · resolved
    From 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.
Sep 21, 20253h 10mSEV 4
Missing Closures Icons in Traffic Maps v1Closure icons were missing from Mapbox Traffic Data v1 maps for an unspecified period; the text gives no scope or detail.AI-graded · Data Services - Mapbox Traffic Data
Why this grade
  1. RULES · SEV 2
    Sev 2 because Data Services - Mapbox Traffic Data had degraded performance
  2. CLAUDE · SEV 4 · UNCLEAR · LOW CONFIDENCE
    Closure icons were missing from Mapbox Traffic Data v1 maps for an unspecified period; the text gives no scope or detail.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 22:42 UTC · investigating
    We are currently investigating this issue.
  2. 01:53 UTC · resolved
    This incident has been resolved.
Sep 21, 20253h 11mSEV 2
Matrix API Planned Closures (remove icons)Matrix API under Navigation was marked degraded for about three hours; the update gives no detail on scope or impact.AI-graded · Navigation - API
Why this grade
  1. RULES · SEV 2
    Sev 2 because Navigation - API had degraded performance
  2. CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
    Matrix API under Navigation was marked degraded for about three hours; the update gives no detail on scope or impact.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record
2 updates
  1. 22:41 UTC · investigating
    We are currently investigating this issue.
  2. 01:52 UTC · resolved
    This incident has been resolved.

Peers, 90 days

Compare

README badge

Mapbox's live grade, for your README.

Mapbox grade badge
[![mapbox on downagain.dev](https://downagain.dev/badge/mapbox.svg)](https://downagain.dev/p/mapbox)