TiDB Cloud Outage History

This incident has been resolved.

The issue has been resolved, and TiDB Cloud Web Console and API performance has returned to normal. Database services were not affected during the incident. We apologize for the inconvenience and appreciate your patience.

The issue has been fully resolved, and services have remained stable since recovery.

The slower-than-usual response times on tidbcloud.com have been resolved. Our team has confirmed that the service is operating normally.

We experienced a temporary service degradation affecting Starter and Essential plan clusters in AWS us-east-1. During this period, some users may have encountered connection issues or query errors. Impact Duration: 06:09 – 06:19 (UTC) The issue has been fully resolved, and services have remained stable since recovery. We sincerely apologize for any inconvenience this may have caused and appreciate your patience and understanding.

The issue affecting Starter and Essential TiDB Cloud instances in AWS ap-southeast-1 has been resolved as of 13:00 UTC Time. All services have recovered, and query performance has returned to normal. We will continue to monitor the system to ensure stability. Thank you for your patience.

Between 22:08 and 22:15 UTC on Feb 9, 2026, a portion of Starter and Essential clusters in the US-East-1 region were unavailable. The issue has been identified and resolved, and all services are now fully operational.

The issue has been resolved. All services are now operating normally. We will continue to monitor the system to ensure stability. Thank you for your patience and understanding.

After 24 hours of observation, the issue has been completely resolved.

The incident has been recovered.

The issue has been resolved.

Between 03:38 - 04:21 UTC. The issue in AP-NORTHEAST-1 has been resolved。

Between 08:25 and 10:52 UTC, some queries to TiFlash in the us-east-1 region experienced partial failures. The issue affected a subset of requests, resulting in degraded query performance or incomplete results for certain workloads. The problem has since been resolved, and TiFlash service is operating normally.

The issue was resolved on 2025-09-24 at 13:50 UTC.

The issue affecting Starter and Essential (Private Preview) clusters in US-EAST-1 has been identified and resolved. Service has been fully restored. We apologize for any inconvenience caused.

The issue causing the inaccessibility of the web console has been resolved.

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

Some TiDB Cloud Serverless clusters located in the us-west-2 region experienced errors for 22 minutes 34 seconds. Root Cause: The issue was due to forward version incompatibility, which resulted in two TiKV servers with older versions than the others panicking. Start Time: 10:58:10 UTC Recovery Time: 11:20:44 UTC

Some TiDB Cloud Serverless clusters located in the ap-southeast-1 region experienced intermittent errors for 26 minutes. Root Cause: The issue was due to an unexpected server outage, resulting in multiple restarts of TiKV server. Start Time: 14:25 UTC Recovery Time: 14:51 UTC (automatically recovered)

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)

We apologize for the inconvenience. A partial accessibility issue with TiDBCloud Serverless was detected in the ap-northeast-1 region at 02:46 UTC on 2024/12/17. The issue was resolved at 02:58 UTC the same day.

We experienced a TiDBCloud Webconsole and API failure from approximately 8:50 AM and to 11:45 AM UTC, and we have confirmed that the issue has been fully resolved.

From 01:43 to 02:57 UTC, some customers were unable to create new TiDBCloud Dedicated clusters on our website. Currently, the service has been restored to normal, and we are continuously monitoring the situation while conducting a thorough analysis of the root cause of the issue.

The accessibility issue in the us-west-2 region has been resolved at 2024/10/29 20:50 UTC.