YugabyteDB

Affected: YugabyteDB Aeon Management Services

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. 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: Google Cloud.

1. investigating 2026-08-22 12:58 UTC

   We have identified resource capacity constraints in the us-central1 (GCP) region that are causing some cluster creation and edit operations to fail in YugabyteDB Aeon. Our team is actively investigating and will provide regular updates as more information becomes available. As a...

2. investigating 2026-08-22 17:43 UTC

   We are continuing to investigate this issue.

3. resolved 2026-08-22 17:52 UTC

   Capacity constraints impacting cluster creation and edit operations in us-central1 have been fully resolved. Control plane operations for us-central1 are re-enabled, and all YugabyteDB Aeon services are running normally across all regions.

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

Affected: YugabyteDB Aeon Management Services

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

Names an upstream provider: AWS.

1. investigating 2026-07-16 10:23 UTC

   Impact: Users may experience failures or delays when attempting to create or edit clusters. Active, running workloads are completely unaffected. Root Cause: A third-party CDN provider (AWS CloudFront) is currently experiencing an outage, impacting our ability to securely fetch...

2. monitoring 2026-07-16 10:36 UTC

   Monitoring

3. resolved 2026-07-16 10:38 UTC

   This incident has been resolved.

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

Affected: YugabyteDB Aeon Management Services

Failure mode: A provider or third-party service this vendor depends on 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 2026-03-26 13:22 UTC

   We have a scheduled maintenance activity within the next two hours. During this period, you may notice brief, intermittent inconsistencies in the metrics displayed in the cloud UI. These are expected and temporary.

2. resolved 2026-03-26 16:25 UTC

   This incident has been resolved.

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

Affected: YugabyteDB Aeon Management Services

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. identified 2026-03-03 12:25 UTC

   Newly added nodes are displayed as down after cluster edit operations, although the operations completed successfully. The issue has been identified, and remediation is currently in progress.

2. monitoring 2026-03-03 15:20 UTC

   The issue has been mitigated and under monitoring.

3. resolved 2026-03-04 05:10 UTC

   This incident has been resolved.

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

Affected: YugabyteDB Aeon Management Services

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-03-03 11:15 UTC

   Inaccurate values were observed on several dashboard charts, including inflated metrics such as disk space appearing doubled. No clusters were impacted and no functionality was degraded, as the issue was limited strictly to the reporting layer. The root cause was identified as a...

2. monitoring 2026-03-03 15:23 UTC

   We are continuing to monitor for any further issues.

3. resolved 2026-03-03 15:25 UTC

   This incident has been resolved.

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

Affected: YugabyteDB Aeon Management Services

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-07 07:12 UTC

   We have identified a partial service disruption affecting control plane operations. Our engineering team is currently investigating the issue. Impact Summary: • Creating, modifying, and deleting resources (clusters) may be failing or experiencing delays. • Management APIs and...

2. identified 2025-10-07 08:06 UTC

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

3. monitoring 2025-10-07 09:30 UTC

   Update - The control plane service disruption has been resolved, and all functionality has been restored. We have confirmed that all services are now operating normally, and we are continuing to monitor the situation. The issue was diagnosed as a misconfiguration in a runtime...

4. resolved 2025-10-07 11:19 UTC

   This incident has been resolved.

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

Affected: YugabyteDB Aeon Databases

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

Names an upstream provider: Azure.

Started during Azure: Network Connectivity – Multiple services impacted in Switzerland North.

1. investigating 2025-09-27 01:20 UTC

   We are currently experiencing a partial service disruption affecting YugabyteDB Aeon deployments on Microsoft Azure in the Switzerland North region. This is due to an ongoing Azure platform outage: https://azure.status.microsoft/en-us/status Impact Summary: • All YugabyteDB Aeon...

2. investigating 2025-09-27 05:00 UTC

   All YugabyteDB Aeon clusters hosted on Azure in Switzerland North are still experiencing a partial service disruption. The Azure platform continues to have an ongoing outage in the region. https://azure.status.microsoft/en-us/status We will provide another update as soon as more...

3. resolved 2025-09-27 09:24 UTC

   Update: The service disruption affecting YugabyteDB Aeon deployments in the Switzerland North region on Microsoft Azure has been fully resolved. The Azure platform has restored full functionality. We apologize for any inconvenience this may have caused and thank you for your...

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

Affected: YugabyteDB Aeon Management Services

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-09-14 00:47 UTC

   We are currently experiencing connectivity issues between our cloud environments that are preventing administrative operations on AWS-hosted clusters. Impact: Cluster management functions (provisioning, scaling, configuration updates, and administrative tasks) are temporarily...

2. resolved 2025-09-14 01:26 UTC

   The connectivity issue affecting administrative operations on AWS-hosted clusters has been fully resolved. All AWS clusters are now fully operational with both database operations and administrative functions available. We apologize for any inconvenience caused during this...

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

Affected: YugabyteDB Aeon Management Services

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

Names an upstream provider: Azure.

1. identified 2024-12-30 21:04 UTC

   We are currently experiencing a partial service disruption impacting YugabyteDB Aeon deployments on Microsoft Azure. Impact Summary: • New Cluster Creation: Temporarily unavailable on Azure. • Scaling Operations: Cluster scale-up and scale-out processes are affected. •...

2. identified 2024-12-31 05:53 UTC

   The root cause has been identified: On December 30, 2024, AlmaLinux replaced its previous Azure Marketplace offer for AlmaLinux OS images with a new one. This change is currently affecting the creation of virtual machines using the previous AlmaLinux OS images on the Azure...

3. identified 2024-12-31 23:17 UTC

   We are pleased to share an update regarding the service disruption affecting YugabyteDB Aeon deployments on Microsoft Azure. Update Summary: New Cluster Creation: Resolved and fully operational on Azure. Scaling Operations: Scale-up and scale-out processes are fully operational...

4. resolved 2025-01-04 05:01 UTC

   We are pleased to announce that the service disruption affecting YugabyteDB Aeon deployments on Microsoft Azure has been fully resolved. Update Summary: New Cluster Creation: Fully operational on Azure. Scaling Operations: Scale-up and scale-out processes are now fully...

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

Affected: YugabyteDB Aeon Management Services

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 2024-11-12 18:50 UTC

   At approximately 6:00 PM UTC, we identified an issue with editing existing clusters in YugabyteDB Aeon, which is failing in certain scenarios. Our team is actively investigating, and we will provide regular updates as more information becomes available. As a temporary measure,...

2. identified 2024-11-13 11:05 UTC

   The issue has been identified, and a maintenance patch including an OS upgrade will be available as a maintenance event in the next few hours. Customers should accept the maintenance event from the cluster Maintenance tab by clicking 'Upgrade Now'. The Yugabyte team will monitor...

3. identified 2024-11-13 16:56 UTC

   The issue has been mitigated, and a maintenance patch including an OS upgrade is available as a maintenance event. Please note, customers who need to edit clusters are required to complete this upgrade before proceeding with any edits. The Yugabyte team will monitor the...

4. monitoring 2024-11-13 20:47 UTC

   The issue has been resolved. To fully restore all cluster operations, a maintenance operation to upgrade system OS packages has been scheduled for affected clusters. Customers may initiate this operation immediately—without waiting for the next maintenance window—by navigating...

5. resolved 2024-11-13 21:18 UTC

   This incident has been resolved.

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

Affected: YugabyteDB Aeon Management Services

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

Names an upstream provider: Google Cloud.

1. investigating 2024-10-08 10:49 UTC

   At approximately 09:21 AM UTC, we observed that new YugabyteDB Aeon cluster creations are failing in the GCP cloud. This issue is currently under investigation. We will provide regular updates as we investigate this issue.

2. resolved 2024-10-08 12:08 UTC

   [11:55 am UTC] The issue was identified in YugabyteDB Aeon cluster creation in the GCP cloud and resolved. Customers can now create YugabyteDB Aeon clusters in GCP. The root cause was identified as an error from a third-party service used for cost calculation. To resolve the...

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

Affected: YugabyteDB Aeon Databases

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS, Cloudflare.

1. investigating 2024-09-23 17:17 UTC

   We are currently aware of an issue affecting any new YugabyteDB Aeon clusters created after 3:52 PM UTC on Sunday September 22 and configured to use AWS Privatelink for connectivity. The issue causes the connections to the YugabyteDB Aeon cluster using AWS Privatelink to fail....

2. monitoring 2024-09-23 18:56 UTC

   Issue: Using Cloudflare DNS was causing issues with AWS PrivateLink DNS name verification step Fix implemented: AWS PrivateLink DNS records are being updated to be looked up from AWS Route53 directly, propagation may take up-to 24 hours

3. resolved 2024-09-23 19:58 UTC

   This incident has been resolved.

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

Affected: YugabyteDB Aeon Databases

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. investigating 2024-09-22 17:04 UTC

   At approximately 3:52 PM UTC on Sunday September 22, we were alerted that many customers may have received hostname resolving errors while connecting to their YugabyteDB Managed database endpoints. We have identified the errrors to be related to a DNS name issue on our end. We...

2. identified 2024-09-22 18:10 UTC

   The issue has been identified as an internal DNS issue, and a fix is being worked on.

3. identified 2024-09-22 21:08 UTC

   A fix for the issue has been successfully deployed, and detailed mitigation measures are being communicated to the affected customers.

4. monitoring 2024-09-22 22:31 UTC

   Affected customers were notified with detailed mitigation measures. This incident is now in monitoring state.

5. resolved 2024-09-22 22:39 UTC

   This incident is now resolved.

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

Affected: YugabyteDB Aeon Management Services

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 2024-03-27 01:25 UTC

   We are investigating reports of management operations involving AWS clusters failing. If you require additional information or support during this outage please see our support portal at https://support.yugabyte.com.

2. identified 2024-03-27 01:38 UTC

   The issue has been identified and a fix is being implemented. We are also seeing missing metrics for the affected period for AWS clusters.

3. monitoring 2024-03-27 01:56 UTC

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

4. monitoring 2024-03-27 08:02 UTC

   This issue has now been resolved

5. resolved 2024-03-27 08:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on YugabyteDB'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 medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. resolved 2024-03-27 00:30 UTC

   At approximately 12:25 AM UTC on Wednesday March 27th, some customers may have received alerts from the YugabyteDB Managed system indicating their clusters were offline. Most of these alerts were false positives due to an administrative issue in YugabyteDB Managed impacting...

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

Affected: YugabyteDB Aeon Management Services

Failure mode: A provider or third-party service this vendor depends on 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: Azure.

1. investigating 2024-01-23 20:44 UTC

   YugabyteDB Managed is currently experiencing an intermittent issue where creation of Virtual Networks (VPCs) for Azure database clusters is taking significantly longer than normal to complete. We are working with Azure support to identify the cause, but at present all creations...

2. identified 2024-01-24 23:34 UTC

   The issue has been identified and the team is working on rolling out a fix.

3. resolved 2024-01-26 16:00 UTC

   The issue has been resolved.

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

Affected: YugabyteDB Aeon Management Services

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 medium confidence (taxonomy v0.2).

1. identified 2023-11-01 16:26 UTC

   YugabyteDB Managed is currently experiencing an issue where a portion of customer clusters are not displaying metrics on cluster performance. We are working on correcting the problem. Only collection & display of metrics, and alerting based on that data, is impacted by this...

2. monitoring 2023-11-01 18:22 UTC

   The YugbyteDB Managed team has deployed a temporary change which has resolved the metrics issue. A further change will be required to fully deploy this change which will result in brief outages of metrics as the permanent change is released. We will update again by 20:00 UTC,...

3. resolved 2023-11-01 21:03 UTC

   The issue with cluster metrics is now fully resolved. For impacted customers, metrics from the window of the outage will not be available, but metrics before and after that window are unaffected.

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

Affected: YugabyteDB Aeon Management Services

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 high confidence (taxonomy v0.2).

1. identified 2023-07-20 12:33 UTC

   During a routine monitoring upgrade that occurred between 10:00 - 11:00 UTC, several customers received emails alerting them that one or more of their DB Nodes were down. This alert was triggered erroneously and should be ignored, Yugabyte are correcting the issue now and will...

2. monitoring 2023-07-20 13:00 UTC

   A fix has been implemented and Yugabyte are monitoring results.

3. monitoring 2023-07-20 15:55 UTC

   We are continuing to monitor for any further issues.

4. resolved 2023-07-20 17:30 UTC

   A new component was added during the regular deployment process for YugabyteDB Managed to improve monitoring. This new component’s metrics were included in the monitoring for customer alerts before all the required infrastructure changes were made. The preemptive addition of...

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

Affected: YugabyteDB Aeon Management Services

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

Names an upstream provider: Google Cloud.

1. resolved 2023-06-21 23:12 UTC

   YugabyteDB Managed users might have noticed a recent loss of database metrics. At 2:30pm UTC, June 19th, GCP encountered a significant outage in the us-west1 region that impacted access to their storage services. While that issue was marked resolved at around 10pm UTC, June...

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

Affected: YugabyteDB Aeon Management Services

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-03-07 17:56 UTC

   We are currently investigating an issue that prevents users from logging in to https://cloud.yugabyte.com Databases hosted on YugabyteDB Managed are not affected. We will provide further communication as needed.

2. identified 2023-03-07 18:06 UTC

   We've identified the issue, and a fix is being deployed.

3. resolved 2023-03-07 18:37 UTC

   This incident has been resolved.

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

Affected: YugabyteDB Aeon Management Services

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 medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2022-11-17 08:16 UTC

   Operations such as creation, editing as well as monitoring for the free tier AWS clusters in US and AP regions aren't functioning properly.

2. monitoring 2022-11-17 08:29 UTC

   Incident is mitigated.

3. resolved 2022-11-17 09:25 UTC

   This incident has been resolved.

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

Affected: YugabyteDB Aeon Management Services

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2022-11-11 00:16 UTC

   Yugabyte Managed users may have recently received an email alert with a subject similar to "YugabyteDB Managed - Db Node Down Severe Alert". This was a false alert sent in error, there are not currently any issues with Yugabyte Managed Clusters. We are reviewing our alerting...

2. resolved 2022-11-11 01:31 UTC

   This incident has been resolved.

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

Affected: YugabyteDB Aeon Management Services

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

Names an upstream provider: AWS.

1. investigating 2022-09-28 18:44 UTC

   We are investigating an issue that is causing sporadic failures for AWS cluster management operations. This issue only affects a subset of AWS clusters during management operations. There is no impact to DB availability or performance. If you require additional information or...

2. monitoring 2022-09-28 21:28 UTC

   This issue has been traced to an elevated error rate from one of our upstream provider services, which impacted a subset of Yugabyte Managed database clusters which are managed from within that region. Only management operations were impacted, such as cluster creations and...

3. resolved 2022-09-28 22:09 UTC

   This incident has been resolved. The upstream provider resolved the problems with their service, and no further error have occurred in the Yugabyte Managed system for over an hour. All impacted customer clusters have been returned to normal operation. If you require additional...

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

Affected: YugabyteDB Aeon Management Services

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. monitoring 2022-08-26 00:22 UTC

   We are seeing transient failures with our upstream infrastructure providers. Most errors are handled via internal retries but customers may experience some task failures during cluster operations including creating, updating and deleting YugabyteDB Managed clusters. In most...

2. monitoring 2022-08-26 00:22 UTC

   We are continuing to monitor for any further issues.

3. monitoring 2022-08-28 03:11 UTC

   We are continuing to monitor for any further issues.

4. resolved 2022-08-28 03:11 UTC

   This incident has been resolved.

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

Affected: YugabyteDB Aeon Management Services

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 2022-08-02 07:35 UTC

   CloudShell is not available due to internal issues. Clusters availability is not affected.

2. monitoring 2022-08-02 08:31 UTC

   Issue is mitigated and we are monitoring CloudShell service.

3. resolved 2022-08-02 09:49 UTC

   This incident has been resolved.

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

Affected: YugabyteDB Aeon Databases

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2022-04-20 00:34 UTC

   Yugabyte is aware of a of an outage impacting access to Yugabyte Managed databases. We have deployed a change to correct the problem and are monitoring for any ongoing problems. If you are experiencing problems connecting to your Yugabyte Managed database please reach out to...

2. monitoring 2022-04-20 00:54 UTC

   At approximately 21:00 UTC on 2022-04-19 (2:00 PM US/Pacific) a change was made to the domain registration for ybdb.io that broke the delegation to our provider. Because of caching behaviors in the global domain name system, customers did not immediately see an impact from this...

3. resolved 2022-04-20 01:20 UTC

   At this time the issue is fully resolved and all cached DNS records should have expired across the global Domain Name System. If you are still seeing any impact from this incident please contact Yugabyte Support.

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

Affected: YugabyteDB Aeon Databases, YugabyteDB Aeon Management Services

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

1. identified 2021-12-15 16:14 UTC

   Cluster operations are failing due to connectivity issues with AWS in US-WEST-1 and US-WEST-2. This affects all cluster creations and operations (edit infrastructure, monitoring). Existing clusters are unaffected except ones in affected regions. But we recommend that you defer...

2. monitoring 2021-12-15 16:34 UTC

   We believe that issue is recovered, but we're continue monitoring the situation.

3. resolved 2021-12-15 17:50 UTC

   This incident has been resolved.

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

Affected: YugabyteDB Aeon Management Services

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

Names an upstream provider: AWS.

1. monitoring 2021-12-07 19:59 UTC

   Some cluster creations are failing due to issues with AWS Route53. This affects all cluster creations. If your cluster creation fails feel free to try again as the nature of the upstream outage is intermittent. Existing clusters are unaffected. Existing clusters are unaffected,...

2. monitoring 2021-12-07 20:00 UTC

   We are continuing to monitor for any further issues.

3. resolved 2021-12-13 20:49 UTC

   This incident has been resolved.

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