Skip to main content
Radar

Elevated API Latencies

Degraded Lasted 2h 23m · started · Radar's page

Level
confirmed
Worst impact
Degraded
Components
Track API
Down Index
21of 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 2h 23m it lasted.

    Anything that failed between 2026-01-06 21:36 UTC and 2026-01-07 00:00 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

  1. investigating

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

    provider

  2. monitoring

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

    provider

  3. monitoring

    We are continuing to monitor for any further issues.

    provider

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

Is Radar still down?

No, this incident was resolved 2026-01-07 00:00 UTC. For Radar's live state, see https://down.guide/radar.

How long did it last?

2h 23m, from 2026-01-06 21:36 UTC to 2026-01-07 00:00 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.