Mapbox

Affected: API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-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...

2. investigating 2026-10-21 07:21 UTC

   This issue has been resolved.

3. resolved 2026-10-21 07:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-19 21:38 UTC

   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...

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: Search

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-29 08:53 UTC

   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. identified 2026-06-29 09:03 UTC

   A mitigation was deployed at 01:35 UTC, which has reduced the impact, and we are actively working to fully resolve the issue.

3. resolved 2026-06-29 15:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: Mapbox Traffic Data, Traffic Congestion Visual Layer

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-02-10 17:23 UTC

   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. monitoring 2026-02-10 19:56 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-02-11 10:31 UTC

   The incident is resolved as of 05:13 UTC. Affected services are now fully operational.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: Mapbox Traffic Data

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-12-06 00:46 UTC

   We are experiencing delays in delivering typical Mapbox Traffic Data. We have implemented a fix and are working to resolve.

2. resolved 2025-12-08 23:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-29 03:09 UTC

   Customers are experiencing high failure rates for live traffic tile requests. We are currently investigating the issue.

2. monitoring 2025-11-29 03:36 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-11-29 03:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API, API, Telemetry, Mapbox Traffic Data

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2025-10-20 10:59 UTC

   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...

2. monitoring 2025-10-20 23:55 UTC

   We are monitoring the recovery of Mapbox services and data pipelines after the cloud provider outage.

3. monitoring 2025-10-21 00:12 UTC

   We are continuing to monitor for any further issues.

4. resolved 2025-10-21 00:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: Search

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-10-14 09:48 UTC

   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.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: Mapbox Traffic Data

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-21 22:42 UTC

   We are currently investigating this issue.

2. resolved 2025-09-22 01:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-21 22:41 UTC

   We are currently investigating this issue.

2. resolved 2025-09-22 01:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-06 22:37 UTC

   We are currently investigating this issue.

2. identified 2025-09-06 22:55 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-09-06 23:17 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-09-06 23:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API, Mapbox Traffic Data, Traffic Congestion Visual Layer

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-14 19:30 UTC

   Mapbox navigation products are experiencing degraded ETAs and Traffic visualization. We are investigating the issue.

2. monitoring 2025-07-15 04:54 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-07-15 06:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-07-08 11:30 UTC

   Navigation services experienced an outage affecting our live traffic data. As a result, users might experience issues with navigation, including inaccuracies in ETA, routing recommendations, and the display of real-time traffic conditions such as congestion and incidents for...

Excerpts are shortened. Read the full incident on Mapbox's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-06-02 19:00 UTC

   On June 2, 2025, between approximately 19:05 and 22:30 UTC, an issue occurred preventing live speed and incident data from being served to Traffic Maps v1 and some customers using the Matrix API. This impacted services reliant on real-time traffic updates. Customers using...

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: Search

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-13 23:59 UTC

   We are currently investigating this issue.

2. identified 2025-05-14 00:54 UTC

   Bottleneck has been identified. We are increasing the capacity of the Search Box system

3. monitoring 2025-05-14 02:28 UTC

   Latency Anomaly mitigation is in-place. Latency is back to normal.

4. monitoring 2025-05-14 05:51 UTC

   Another correction/Hot fix was applied to reduce the load.

5. resolved 2025-05-14 08:39 UTC

   After last correction latency is back to normal. Incident report will be shared soon.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-13 12:40 UTC

   We are investigating increased error rates and latency on our vector tile endpoints.

2. investigating 2025-03-13 12:43 UTC

   We are continuing to investigate this issue.

3. investigating 2025-03-13 16:21 UTC

   We are continuing to investigate and remediate this issue

4. monitoring 2025-03-13 21:06 UTC

   The issue has been successfully mitigated. Our team is actively monitoring the service to ensure optimal performance.

5. monitoring 2025-03-13 23:24 UTC

   Service remains stable, we'll continue to monitor overnight.

6. resolved 2025-03-14 12:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-01-31 16:44 UTC

   In rare cases, the sporadic false road closures might potentially degrade the navigation experience causing unnecessary detours. The fix was delivered on Jan 30th.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: Traffic Congestion Visual Layer

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-01-09 18:37 UTC

   We are investigating an issue with the mapbox.mapbox-traffic-v1 tileset. We have identified the root cause and are working on resolving.

2. monitoring 2025-01-09 23:25 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-01-10 02:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: Mapbox Traffic Data

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-12-10 17:37 UTC

   We are experiencing delays in delivering typical Mapbox Traffic Data. We have implemented a fix and are working to resolve.

2. identified 2024-12-10 17:37 UTC

   We are continuing to work on a fix for this issue.

3. resolved 2024-12-17 22:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-09-19 12:00 UTC

   Navigation services experienced an outage affecting our live traffic data. As a result, users might experience issues with navigation, including inaccuracies in ETA, routing recommendations, and the display of real-time traffic conditions such as congestion and incidents for...

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2024-07-30 23:07 UTC

   We have received reports from AWS that several core services are experiencing instability. This will impact Mapbox's ability to provide live traffic, live incidents and ETA's to its customers.

2. investigating 2024-07-31 00:17 UTC

   We are continuing to investigate this issue.

3. investigating 2024-07-31 02:20 UTC

   We are continuing to investigate this issue.

4. investigating 2024-07-31 12:16 UTC

   Our traffic services are fully operational.

5. resolved 2024-07-31 12:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-07-30 23:02 UTC

   We are currently investigating an increase in error responses from the live traffic vector tile service.

2. identified 2024-07-30 23:59 UTC

   We have taken measures to reduce the impact and continue to monitor the incident.

3. identified 2024-07-31 01:28 UTC

   We are continuing to work on a fix for the issue.

4. identified 2024-07-31 02:30 UTC

   We are continuing to work towards a fix for the issue.

5. identified 2024-07-31 03:35 UTC

   We are working to address service disruptions caused by the ongoing issue.

6. monitoring 2024-07-31 05:49 UTC

   We have implemented several fixes and are starting to see recovery in the Vector Tiles API. We will continue to monitor the service as it returns to full health.

7. resolved 2024-07-31 06:41 UTC

   The Vector Tiles API error rates have subsided and the service is fully operational.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-07-28 23:15 UTC

   Navigation api requests (Directions, Map-matching) in hitting our `ap-southeast-1` datacenter experienced stale or missing live-data and congestion for 90 minutes. Incident has been resolved

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-09 19:00 UTC

   We are currently investigating this issue.

2. monitoring 2024-06-09 20:39 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-06-09 21:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-05-17 00:04 UTC

   We are investigating image quality degradation on the Static Images API

2. investigating 2024-05-17 01:14 UTC

   This issue impacts Static API requests for styles using the mapbox.mapbox-terrain-dem-v1 tileset. Not all requests are impacted and the issue is sporadic. We are continuing to investigate the cause of the issue.

3. investigating 2024-05-17 15:17 UTC

   We are still investigating image quality degradation on the Static Images API

4. identified 2024-05-17 15:33 UTC

   We have identified the cause of the image degradation. However, given the nature of the issue, we do not anticipate a fix to be rolled out imminently. We will provide more updates on timeline as we have them.

5. resolved 2024-05-17 19:58 UTC

   We have identified the root cause of this issue and have a clear path forward, but expect the rollout to take some time. We are closing this status but will post updates as fixes are available.

6. postmortem 2024-05-22 15:02 UTC

   The issue with 3D Terrain distortion has been mitigated and fixes have been shipped to all Static Image and Tile endpoints.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-04-29 17:59 UTC

   We are investigating an issue causing degraded performance across maps api services.

2. identified 2024-04-29 18:12 UTC

   We have identified the issue and are working on reducing impact.

3. monitoring 2024-04-29 18:39 UTC

   We are monitoring the impacted services as we start to see recovery.

4. resolved 2024-04-29 19:04 UTC

   This incident has been resolved and system status is nominal.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2024-04-17 19:41 UTC

   We are investigating an issue with the Static API.

2. resolved 2024-04-17 20:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-03-17 19:56 UTC

   We are currently investigating an on-going issue with live traffic requests.

2. identified 2024-03-17 20:27 UTC

   We have mitigated the issue with live-traffic requests and are continuing to investigate.

3. resolved 2024-03-17 21:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-01-25 12:30 UTC

   Between approximately 12:15UTC and 13:50UTC on 2023-01-025, some users of the Matrix, Optimization, and Directions API in some regions may have received HTTP 401 authentication errors while using the services. The issue has been identified and resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-01-12 08:00 UTC

   From 2024-01-12 00:10 UTC to 2024-01-12 01:10 UTC, a period of one hour, we experienced failures when delivering live traffic updates for Mapbox Traffic Data. The issue has been resolved. During this outage, Mapbox Traffic Data customers subscribed to live traffic did not...

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-01-05 17:45 UTC

   We are currently investigating an on-going issue with live traffic requests.

2. identified 2024-01-05 18:18 UTC

   The issue causing the performance degradation to live traffic requests was identified and a fix is being implemented.

3. monitoring 2024-01-05 18:43 UTC

   The service is stabilizing and we are continuing to monitor the fix.

4. resolved 2024-01-07 00:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2023-11-15 23:35 UTC

   This affects live-data such as congestion, closures and incidents for Navigation apis as well as live-traffic maps. We are currently investigating the issue and have re-directed traffic to regions with complete coverage in the meantime.

2. monitoring 2023-11-16 00:12 UTC

   The partial live-data coverage in us-east-1 region has been mitigated, and the region is now processing client requests again. Investigation of root-cause is continuing and we're tracking key metrics.

3. resolved 2023-11-16 23:31 UTC

   The original issue is identified and resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-11-10 00:23 UTC

   We are investigating reports of processing issues with the Uploads API.

2. identified 2023-11-10 00:41 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2023-11-10 01:02 UTC

   We have resolved the issue for newly created uploads. We continue to work through the backlog of uploads that are still processing.

4. monitoring 2023-11-10 01:43 UTC

   We are seeing recovery and continue to process the backlog of jobs affected.

5. monitoring 2023-11-10 02:18 UTC

   We are continuing to monitor for any further issues.

6. resolved 2023-11-10 02:18 UTC

   All operations have returned to normal, and the backlog of jobs has been cleared.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2023-09-26 15:30 UTC

   Customers using the NavSDK, Directions, and Map Matching APIs in the AP-southeast-2 region may have received stale traffic information in ETA and Visual Map, including live incidents. This issue began around 14:45 UTC and ended around 18:30 UTC. The root cause is under...

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-09-18 19:25 UTC

   We are currently investigating an increase in HTTP error rates and latency for Maps APIs

2. identified 2023-09-18 19:29 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2023-09-18 19:33 UTC

   We are continuing to work on a fix for this issue.

4. monitoring 2023-09-18 19:47 UTC

   A fix has been implemented and we are monitoring the results.

5. monitoring 2023-09-18 21:39 UTC

   All APIs are currently operational. We are continuing to monitor performance.

6. resolved 2023-09-19 16:30 UTC

   This incident has been resolved. All systems operational.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: Search

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2023-09-12 20:14 UTC

   We've identified an issue where users searching for select POI brands in the US and Germany will either not get results or the returned POI names will just be numbers. The fix is identified and a rollback operation is underway.

2. resolved 2023-09-12 21:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API, Traffic Congestion Visual Layer

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2023-09-05 21:00 UTC

   We are investigating degraded performance for the Matrix API and Traffic Maps v1. Customers of these services may experience missing or incorrect road closure data. We have identified the root cause and are working towards a solution.

2. resolved 2023-09-05 23:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API, Studio, Search

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2023-08-24 08:23 UTC

   Multiple Mapbox services experienced errors due to an internal change. This issue lasted from 07:42 to 07:51 UTC. The issue was resolved and all services returned to normal operation.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API, Mapbox Traffic Data, Traffic Congestion Visual Layer

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-08-11 00:51 UTC

   Customers using the mapbox/driving-traffic profiles on the Directions, Map Matching, and Matrix APIs may receive ETAs that do not reflect live traffic conditions in the affected regions. Customers using traffic-maps may view tiles that do not reflect live traffic conditions in...

2. monitoring 2023-08-11 02:30 UTC

   We have identified an issue with metrics reporting from our cloud service provider. We have confirmed through the course of this incident, all live traffic systems and products making use of live traffic data were working as expected. We will continue to monitor the situation...

3. resolved 2023-08-11 02:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: Mapbox Traffic Data

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-07-25 22:12 UTC

   Mapbox Speeds is currently experiencing degraded performance. Customers of Live Traffic Data may experience stale data. We are investigating the root cause of the issue.

2. identified 2023-07-25 22:58 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2023-07-26 02:22 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2023-07-26 02:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: Traffic Congestion Visual Layer

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-07-25 22:07 UTC

   Traffic Maps V1 is experiencing degradation in quality. Users of Traffic Maps V1 may experience stale traffic tiles that do not reflect the current conditions on the road. We are investigating the cause of this issue.

2. identified 2023-07-25 22:58 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2023-07-26 02:22 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2023-07-26 02:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2023-07-18 16:30 UTC

   Due to an incident with our cloud service provider, multiple Mapbox services had elevated HTTP 421 errors. This issue lasted from 4:30 PM to 5:15 PM UTC. The issue was resolved and all services returned to normal operation afterwards.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2023-07-17 11:00 UTC

   We have identified an issue impacting traffic visualization and ETA's in the following countries: China, Korea, Southwest Japan (locations west of Tokushima), and much of South East Asia. There were three major impact areas, as described below. All have been resolved as of the...

Excerpts are shortened. Read the full incident on Mapbox's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2023-07-13 20:30 UTC

   On Thursday, 07/13/2023 between 19:20 UTC and 20:14 UTC (a period of 54 minutes) a subset of forward geocoding requests were impacted by high latency and some timeouts. The service is now operating normally.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: Telemetry

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-07-13 00:55 UTC

   We are currently investigating this issue. All customers using a Navigation API powered by Mapbox traffic may experience ETAs in the impacted regions that do not accurately reflect real time road conditions. Additionally, customers of Mapbox traffic data may receive intermittent...

2. monitoring 2023-07-13 01:53 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2023-07-13 03:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2023-07-11 16:00 UTC

   Between 13:53 UTC and 14:06 UTC users would have experienced elevated API errors for our Directions, Isochrone, and Map Matching APIs.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API, Mapbox Traffic Data, Traffic Congestion Visual Layer

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-06-13 19:20 UTC

   Offline map downloads and Mapbox Tiling Service are showing high error rates

2. investigating 2023-06-13 19:37 UTC

   We are investigating degraded generation of Live Mapbox Traffic predications and delivery to customers.

3. investigating 2023-06-13 19:56 UTC

   We are continuing to investigate this issue.

4. investigating 2023-06-13 20:07 UTC

   We are investigating degraded refreshing of Traffic Maps V1 in some regions. Users of Traffic Maps V1 may experience stale traffic that does not reflect the current conditions on the road.

5. investigating 2023-06-13 20:24 UTC

   We are continuing to investigate the issues with Mapbox Tiling Service, Mapbox Traffic, and Offline Map downloads.

6. monitoring 2023-06-13 20:40 UTC

   We are seeing decreased error rates for the Mapbox Tiling Service and Offline Map downloads. We will continue to monitor the services.

7. monitoring 2023-06-13 21:33 UTC

   Live traffic prediction has recovered but delivery of live traffic to Mapbox Speeds customers is still degraded.

8. monitoring 2023-06-13 22:24 UTC

   Delivery of Mapbox Traffic Data to customers and Traffic Maps V1 have recovered. We continue to monitor both services.

9. resolved 2023-06-13 23:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API, Mapbox Traffic Data, Traffic Congestion Visual Layer

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2023-05-31 01:05 UTC

   Customers using the mapbox/driving-traffic profiles on the Directions, Map Matching, and Matrix APIs may receive ETAs informed by stale live traffic data in the affected regions. Customers using traffic-maps may view tiles informed by stale live traffic data in the affected...

2. monitoring 2023-05-31 01:33 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2023-05-31 02:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-05-09 15:57 UTC

   We are currently investigating errors from the service providing offline map downloads

2. monitoring 2023-05-09 16:48 UTC

   A fix has been implemented and we're continuing the monitor the service

3. resolved 2023-05-09 18:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2023-05-09 08:00 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Mapbox's status page.