Elevated API Latencies

What to do

• Check whether you use Radar Track API in us, us-east-1, us-east-2. 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 9h 41m it lasted.

  Anything that failed between 2025-06-18 13:43 UTC and 2025-06-18 23:24 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 6

1. investigatingJun 18, 2025, 1:43 PM UTC

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

   provider

2. identifiedJun 18, 2025, 1:59 PM UTC

   The issue has been identified and a fix is being implemented.

   provider

3. identifiedJun 18, 2025, 2:07 PM UTC

   The cause of this issue is a reoccurrence of the same AWS incident from last week: https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-2::event/INTERNETCONNECTIVITY/AWS_INTERNETCONNECTIVITY_OPERATIONAL_ISSUE/AWS_INTERNETCONNECTIVITY_OPERATIONAL_ISSUE_D8A2C_D55BF2D0F04 We are immediately taking steps to prevent this ongoing AWS issue from affecting our infrastructure.

   provider

4. identifiedJun 18, 2025, 3:43 PM UTC

   We have not seen any impact outside of two brief periods within 13:29 - 13:42 UTC today. On-call Radar engineers are continuing to work on isolating our infrastructure from these ongoing AWS network connectivity incidents between the us-east-1 and us-east-2 regions.

   provider

5. identifiedJun 18, 2025, 3:46 PM UTC

   We are continuing to work on a fix for this issue.

   provider

6. resolvedJun 18, 2025, 11:24 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

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