Skip to main content
Radar

Elevated API Errors

Degraded Lasted 32m · started · Radar's page

Level
confirmed
Worst impact
Degraded
Components
Track verified API, Track API, Geocoding APIs, Routing APIs, Maps APIs
Down Index
25of 100

What to do

  • Check whether you use Radar Track verified API, Track API, Geocoding APIs, Routing APIs and 1 more. 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 32m it lasted.

    Anything that failed between 2025-12-05 09:23 UTC and 2025-12-05 09:55 UTC may need a replay.
  • Subscribe to Radar's feed to hear about the next one first. RSS feed

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

Updates from Radar 3

  1. investigating

    We're experiencing an elevated level of API errors and are currently looking into the issue.

    provider

  2. monitoring

    The issue is related to a Cloudflare incident (https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q).

    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-53d8d76dea

Is Radar still down?

No, this incident was resolved 2025-12-05 09:55 UTC. For Radar's live state, see https://down.guide/radar.

How long did it last?

32m, from 2025-12-05 09:23 UTC to 2025-12-05 09:55 UTC, by the times Radar posted.

What was affected?

Radar named Track verified API, Track API, Geocoding APIs, Routing APIs and 1 more.

What caused it?

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

Where does this come from?

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