Skip to main content
Mapbox

Elevated Rate of Partial Response (206) and Not Found (404) Errors in the Search Box API

Partial outage Lasted 6h 22m · started · Mapbox's page

Level
confirmed
Worst impact
Partial outage
Components
Search
Down Index
33of 100

What to do

  • Check whether you use Mapbox Search. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 6h 22m it lasted.

    Anything that failed between 2026-06-29 08:53 UTC and 2026-06-29 15:15 UTC may need a replay.
  • Subscribe to Mapbox's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=mapbox works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Mapbox 3

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

    provider

  2. identified

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

    provider

  3. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-2ac3835550

Is Mapbox still down?

No, this incident was resolved 2026-06-29 15:15 UTC. For Mapbox's live state, see https://down.guide/mapbox.

How long did it last?

6h 22m, from 2026-06-29 08:53 UTC to 2026-06-29 15:15 UTC, by the times Mapbox posted.

What was affected?

Mapbox named Search.

What caused it?

Mapbox hasn't published a root cause. If it does, it shows here.

Where does this come from?

Mapbox's official status page, https://status.mapbox.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.