TiDB Cloud

Affected: TiDB Cloud Portal Backend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-13 09:30 UTC

   We are investigating an issue affecting cluster change operations through the TiDB Cloud Console and API. Existing clusters remain operational, and database workloads are not affected. We will provide updates as more information becomes available.

2. monitoring 2026-09-13 09:48 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-13 09:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: TiDB Cloud Portal Backend, TiDB Cloud Portal Frontend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-23 03:03 UTC

   We are currently investigating an issue causing slower response times for the TiDB Cloud Web Console and APIs. Database services are not affected and continue to operate normally. We are working to resolve the issue as soon as possible. We apologize for the inconvenience.

2. identified 2026-08-23 03:24 UTC

   We have identified the root cause and are currently working on optimizations to restore normal Web Console and API performance. Database services remain unaffected. We appreciate your patience while we work on the fix.

3. resolved 2026-08-23 03:31 UTC

   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.

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: aws / us-west-2, aws / us-west-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-07-15 04:00 UTC

   Some Starter and Essential services in AWS us-west-2 are currently unavailable. We are investigating the root cause.

2. resolved 2026-07-15 04:22 UTC

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

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: TiDB Cloud Portal Backend, TiDB Cloud Portal Frontend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-01 05:43 UTC

   We are currently observing slower-than-usual response times on tidbcloud.com. Our team is actively investigating the issue and will provide updates as soon as more information becomes available.

2. resolved 2026-07-01 08:49 UTC

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

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2026-04-03 06:00 UTC

   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...

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: aws / ap-southeast-1, aws / ap-southeast-1

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-02-27 11:55 UTC

   We are currently investigating an issue causing partial query failures on Starter and Essential TiDB Cloud instances in the AWS ap-southeast-1 region. Some users may experience intermittent query errors or degraded performance. Our team is actively working to identify the root...

2. resolved 2026-02-27 13:07 UTC

   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...

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: aws / us-east-1, aws / us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-02-10 08:14 UTC

   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.

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: aws / ap-southeast-1, aws / eu-central-1, aws / us-east-1, aws / us-west-2, alicloud / ap-southeast-1

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-06 05:10 UTC

   We have identified an issue where some v8.5 Starter TiDB Cloud instances may experience import failures. To prevent further impact and ensure system stability, the import function has been temporarily disabled for affected region instances while maintenance is in progress. Our...

2. resolved 2026-02-06 05:41 UTC

   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.

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: TiDB Cloud Portal Backend

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-12-10 23:52 UTC

   We’re currently investigating an intermittent DNS resolution issue that may affect connectivity to some TiDB Cloud private endpoints. While certain retries may succeed, other attempts will fail leading to inconsistent connections. Our engineering team is working with our DNS...

2. investigating 2025-12-11 00:32 UTC

   We are continuing to investigate this issue.

3. investigating 2025-12-11 01:04 UTC

   We have identified an intermittent DNS resolution issue caused by an unexpected outage in the DNS service used by our backend systems. As a result, you may experience occasional connection disruptions. Our engineering team is actively working with our DNS provider to determine...

4. monitoring 2025-12-11 02:09 UTC

   The issue has been identified and the DNS problem has been fixed. Name resolution is now recovering. You can use the following command to verify it locally: "nslookup -qt=NS tidb-cloud.com 8.8.8.8"

5. resolved 2025-12-12 06:31 UTC

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

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: aws / us-west-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-11-25 07:19 UTC

   The issue affecting Starter and Essential (Public Preview) clusters in US-WEST-2 has been identified.

2. resolved 2025-11-25 07:24 UTC

   The incident has been recovered.

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: TiDB Cloud Portal Backend, aws / us-east-1

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-20 08:40 UTC

   We are currently investigating an access issue affecting Starter and Essential (Public Preview) clusters in the US-East-1 region. Some related services, including Portal UI, OpenAPI, and Metrics, may also be impacted. Our engineering team is actively working to identify the...

2. monitoring 2025-10-20 09:48 UTC

   Most services have been restored, and we are still monitoring the services.

3. resolved 2025-10-20 09:51 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-10-15 03:30 UTC

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

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2025-10-14 08:30 UTC

   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...

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: TiDB Cloud Portal Backend

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2025-09-24 12:50 UTC

   We are currently investigating a fundamental issue affecting TiDB Cloud on GCP. This issue is causing partial impact on cluster creation and scaling, and some operations may fail. Our team is actively working with GCP to resolve the problem as quickly as possible.

2. resolved 2025-09-24 14:56 UTC

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

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: aws / us-east-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-22 14:30 UTC

   We are currently investigating an issue causing partial inaccessibility of Starter and Essential (Private Preview) clusters in the US-East-1 region. Our team is actively working on a resolution.

2. investigating 2025-09-22 17:29 UTC

   To address the ongoing issue, we have proactively paused all clusters in US-EAST-1. The team is working on a fix.

3. resolved 2025-09-22 20:45 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.

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: TiDB Cloud Portal Frontend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-21 01:05 UTC

   We are currently investigating an issue that is causing the TiDB Cloud webconsole to be inaccessible. Our team is working to resolve this as quickly as possible and will provide an update as soon as we have more information.

2. resolved 2025-08-21 01:54 UTC

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

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: aws / us-east-1

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2025-06-17 16:59 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,...

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: aws / us-west-2

Failure mode: A zone, region or data center became unavailable. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-05-13 17:07 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:...

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: aws / ap-southeast-1

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-05-08 16:11 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...

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: TiDB Cloud Portal Backend

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2025-04-15 09:34 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...

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: aws / ap-northeast-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-12-17 03:08 UTC

   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.

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: TiDB Cloud Portal Backend, TiDB Cloud Portal Frontend

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-12-05 08:55 UTC

   Our TiDB Cloud is currently experiencing unexpected failures with the Webconsole and API. We are actively investigating the issue.

2. investigating 2024-12-05 08:59 UTC

   We are continuing to investigate this issue.

3. identified 2024-12-05 09:42 UTC

   We have identified the root cause and are now proceeding with the service recovery.

4. monitoring 2024-12-05 10:39 UTC

   We are implementing the fix, and the service has partially recovered. We are continuously monitoring the recovery progress.

5. resolved 2024-12-05 11:47 UTC

   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.

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2024-11-06 01:30 UTC

   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.

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: aws / us-west-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-10-29 20:02 UTC

   We apologize for the inconvenience, but we have detected an accessibility issue in the us-west-2 region starting from 2024/10/29 at 18:08 UTC.

2. resolved 2024-10-29 21:13 UTC

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

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: aws / ap-northeast-1, aws / ap-southeast-1, aws / eu-central-1, aws / us-west-2

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-08-29 13:19 UTC

   We apologize for the inconvenience, but we have detected a partial connectivity issue in the multiple regions during the following periods (UTC Timezone): ap-northeast-1 08:34-09:03 ap-southeast-1 08:32-09:19 us-west-2 08:45-09:10 eu-central-1 09:08-09:15 The issue has been...

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: aws / us-west-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-07-22 02:53 UTC

   We apologize for the inconvenience, but we have detected a partial accessibility issue in the us-west-2 region during the following periods (UTC Timezone): 01:25 to 01:32 01:35 to 01:50 01:59 to 02:07 The issue has been solved.

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Affected: aws / us-west-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-07-02 19:08 UTC

   This incident has been resolved at 19:00 UTC time, July 2st.

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-07-01 17:00 UTC

   This incident has been resolved at 17:01 UTC time, July 1st.

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2024-04-29 12:30 UTC

   During the period from 19:30 to 20:15 (UTC+0), TiDB Cloud Serverless experienced unavailability in the us-east-1 region. 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...

Excerpts are shortened. Read the full incident on TiDB Cloud's status page.