- Level
- confirmed
- Worst impact
- Degraded
- Components
- Track API
- Down Index
- 19of 100
What to do
Check whether you use Radar Track API. 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 43m it lasted.
Anything that failed between 2025-08-21 19:12 UTC and 2025-08-21 19: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 4
- investigating
We're experiencing an elevated level of API latencies and are currently looking into the issue.
provider
- investigating
We see that Cloudflare is having degraded network performance in the Ashburn, VA area and we suspect that it is contributing to this issue, though we are still investigating the cause of degraded performance.
provider
- monitoring
Cloudflare has implemented a fix and we are seeing performance return to normal.
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-62ce44996e
Is Radar still down?
No, this incident was resolved 2025-08-21 19:55 UTC. For Radar's live state, see https://down.guide/radar.
How long did it last?
43m, from 2025-08-21 19:12 UTC to 2025-08-21 19:55 UTC, by the times Radar posted.
What was affected?
Radar named Track API.
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.