TiDB Cloud incident

Dedicated TiDBCloud Partial Downtime in ap-northeast-1 Region

Notice Resolved View vendor source →

TiDB Cloud experienced a notice incident on April 15, 2025 affecting TiDB Cloud Portal Backend, lasting 49m. The incident has been resolved; the full update timeline is below.

Started
Apr 15, 2025, 07:41 AM UTC
Resolved
Apr 15, 2025, 08:30 AM UTC
Duration
49m
Detected by Pingoru
Apr 15, 2025, 07:41 AM UTC

Affected components

TiDB Cloud Portal Backend

Update timeline

  1. resolved Apr 15, 2025, 09:34 AM UTC

    Some nodes in dedicated TiDB Cloud clusters located in the ap-northeast-1 region experienced a brief period of unavailability. Root Cause: The issue was due to an AWS incident affecting EC2 instances in apne1-az4 Availability Zone, where instance health checks failed temporarily. More details can be found on the AWS Health Dashboard.(https://health.aws.amazon.com/health/status) Start Time: 07:41 AM UTC Recovery Time: 08:30 AM UTC (automatically recovered)