- Level
- confirmed
- Worst impact
- Degraded
- Components
- Track verified API, Track API, Webhooks, Search APIs, Geocoding APIs, Routing APIs, Trips APIs, Maps APIs
- Down Index
- 30of 100
What to do
Check whether you use Radar Track verified API, Track API, Webhooks, Search APIs and 4 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 26m it lasted.
Anything that failed between 2026-06-26 22:33 UTC and 2026-06-26 22:59 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 5
- investigating
We're experiencing an elevated level of API latencies and are currently looking into the issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
API latencies have returned to baseline, but webhooks and integration sends are delayed.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- 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-e55a363055
Is Radar still down?
No, this incident was resolved 2026-06-26 22:59 UTC. For Radar's live state, see https://down.guide/radar.
How long did it last?
26m, from 2026-06-26 22:33 UTC to 2026-06-26 22:59 UTC, by the times Radar posted.
What was affected?
Radar named Track verified API, Track API, Webhooks, Search APIs and 4 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.