Radar incident

Elevated API Latencies

Minor Resolved View vendor source →

Radar experienced a minor incident on June 18, 2025 affecting Track API, lasting 9h 41m. The incident has been resolved; the full update timeline is below.

Started
Jun 18, 2025, 01:43 PM UTC
Resolved
Jun 18, 2025, 11:24 PM UTC
Duration
9h 41m
Detected by Pingoru
Jun 18, 2025, 01:43 PM UTC

Affected components

Track API

Update timeline

  1. investigating Jun 18, 2025, 01:43 PM UTC

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

  2. identified Jun 18, 2025, 01:59 PM UTC

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

  3. identified Jun 18, 2025, 02: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.

  4. identified Jun 18, 2025, 03: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.

  5. identified Jun 18, 2025, 03:46 PM UTC

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

  6. resolved Jun 18, 2025, 11:24 PM UTC

    This incident has been resolved.