TiDB Cloud incident

TiDB Cloud Serverless Partial Downtime in us-east-1 Region

Minor Resolved View vendor source →

TiDB Cloud experienced a minor incident on June 17, 2025 affecting aws / us-east-1, lasting 32m. The incident has been resolved; the full update timeline is below.

Started
Jun 17, 2025, 10:01 AM UTC
Resolved
Jun 17, 2025, 10:33 AM UTC
Duration
32m
Detected by Pingoru
Jun 17, 2025, 10:01 AM UTC

Affected components

aws / us-east-1

Update timeline

  1. resolved Jun 17, 2025, 04:59 PM UTC

    Some TiDB Cloud Serverless clusters located in the us-east-1 region experienced connectivity errors when establishing the first connection after being idle for 10 minutes. Root Cause: The issue was due to inappropriate error handling in the TiDB resource arbitration service, which resulted in the service panicking and being unable to allocate resources for TiDB cluster awakening from hibernation. Start Time: 10:01 UTC Recovery Time: 10:33 UTC