Aug <var data-var='date'> 5</var>, <var data-var='time'>19:50</var> UTC Resolved - Following an extended period of monitoring, the team has confirmed that the cluster remains healthy and stable. Aug <var data-var='date'> 5</var>, <var data-var='time'>03:55</var> UTC Monitoring - Teams have mitigated the immediate active impact, but work continues to ensure the problem does not recur and to fully understand the root cause. For now we will continue to monitor the situation. If you continue to experience impacts, please reach out to Support. Aug <var data-var='date'> 4</var>, <var data-var='time'>23:52</var> UTC Update - We are investigating an issue affecting a subset of Basic and Standard clusters in eu-west1, where some clusters may be unable to connect or execute queries. Teams have been notified and are actively working on mitigation. Aug <var data-var='date'> 4</var>, <var data-var='time'>23:47</var> UTC Update - We are investigating an issue affecting a subset of Basic clusters in eu-west1, where some clusters may be unable to connect or execute queries. Teams have been notified and are actively working on mitigation. Aug <var data-var='date'> 4</var>, <var data-var='time'>23:46</var> UTC Investigating - We are investigating an issue affecting a subset of Free Tier clusters in eu-west-1, where some clusters may be unable to connect or execute queries. Teams have been notified and are actively working on mitigation.

Cluster connectivity and execution issues

Jul <var data-var='date'>12</var>, <var data-var='time'>21:24</var> UTC Resolved - The cluster creation issue has been restored. Issue is resolved. Jul <var data-var='date'>12</var>, <var data-var='time'>20:08</var> UTC Investigating - We are currently aware of and investigating a cluster creation failure. Teams are engaged and actively working to mitigate as quickly as possible.

Cluster Creation Failure

Jun <var data-var='date'> 9</var>, <var data-var='time'>22:02</var> UTC Resolved - Fix deployment is complete, tested and verified. Jun <var data-var='date'> 9</var>, <var data-var='time'>21:26</var> UTC Identified - We have identified a minor issue affecting Cloud customers who are unable to accept invites, preventing them from inviting new users to their organizations. Internal teams are aware and a fix is in flight. ETA: 30min - 1hour. We will provide the next update at the top of the hour or prior if the fix is deployed before that time.

Unable to accept invites

May <var data-var='date'> 8</var>, <var data-var='time'>21:53</var> UTC Resolved - All CockroachDB clusters in the affected AWS availability zone have been restored to a fully operational state. We will continue to monitor the upstream incident from AWS, but do not expect any impact to CockroachDB clusters. May <var data-var='date'> 8</var>, <var data-var='time'>08:25</var> UTC Update - AWS reports continued progress towards resolving the issue in the US-EAST-1 Region and is working towards full recovery. Affected services may continue to experience elevated error rates and latencies until recovery is complete. We continue to monitor the situation and take appropriate action to ensure uptime and availability for CockroachDB clusters. We'll provide another update as we learn more from AWS. May <var data-var='date'> 8</var>, <var data-var='time'>03:24</var> UTC Update - AWS's latest status update reports that they are continuing to work on the situation, and progress is slow. AWS has advised a next update time at 05:00 UTC. We continue to monitor the situation and take appropriate action to ensure uptime and availability for Cockroach DB clusters. We'll next update by about 05:00 UTC when we learn more from AWS. May <var data-var='date'> 8</var>, <var data-var='time'>02:13</var> UTC Monitoring - AWS is experiencing elevated error rates and degraded performance in a single availability zone in the us-east-1 region. CockroachDB clusters in us-east-1 remain available, and we are monitoring the situation and taking corrective action as appropriate to ensure SQL availability of CockroachDB clusters in this region.

Degraded performance in one AWS us-east-1 availability zone

Mar <var data-var='date'>18</var>, <var data-var='time'>16:02</var> UTC Resolved - Social login for Microsoft accounts is now available. Please reach out to support if you continue to experience issues. Mar <var data-var='date'>18</var>, <var data-var='time'>15:23</var> UTC Investigating - Social logins for customers using personal/non-SSO Microsoft accounts is currently unavailable. Our teams are aware and currently investigating.

Cloud Console Social Login Auth Unavailable

Mar <var data-var='date'>11</var>, <var data-var='time'>19:51</var> UTC Resolved - Beginning March 1, 2026, a power outage caused by physical damage to AWS infrastructure affected multiple Availability Zones in the AWS me-central-1 (UAE) region, resulting in the unavailability of CockroachDB Cloud clusters in that region. A single Availability Zone in me-south-1 was also impacted, causing degraded performance for clusters in that region. While AWS has not yet fully restored power to all affected Availability Zones, Cockroach Labs has directly engaged all customers impacted by this incident, providing resolution guidance and hands-on remediation assistance, including cross-region data restoration where applicable. As remediation steps have been completed or provided to all directly impacted customers, we are resolving this incident from Cockroach Labs' perspective. Cluster creation in the affected regions remains restricted pending full AWS recovery. Customers with outstanding questions or concerns are encouraged to contact Cockroach Labs Support. Mar <var data-var='date'> 2</var>, <var data-var='time'>17:50</var> UTC Update - AWS me-central-1 region is impacted with two AZs out. Clusters in that region are currently unavailable. AWS me-south-1 region is also experiencing a single AZ outage, which causes degraded performance of clusters in that region. While no impact has been observed on GCP or Azure in those regions, customers with single-region deployments are advised to have their disaster recovery plans ready should the need to restore from a backup to another region be required. We are closely tracking AWS's status. Impacted customers can track AWS status here https://health.aws.amazon.com/health/status. Mar <var data-var='date'> 2</var>, <var data-var='time'>09:01</var> UTC Update - me-central-1 region is impacted more with two AZs out and the clusters in that region are unavailable. In addition to this, me-south-1 region is also experiencing an AZ outage, which causes degraded performance of clusters in me-south-1. We are closely tracking AWS's status. Impacted customers can track AWS status here https://health.aws.amazon.com/health/status Mar <var data-var='date'> 2</var>, <var data-var='time'>02:47</var> UTC Update - AWS continues to work on mitigation efforts, including stabilizing impacted APIs and implementing interim workarounds. Our teams are actively reviewing and validating these mitigations; however, this effort will continue into tomorrow. We will provide our next update at 7:00 AM PST, or sooner if additional information becomes available. Mar <var data-var='date'> 2</var>, <var data-var='time'>01:51</var> UTC Update - AWS is reporting significant signs of recovery for specific APIs and requests, but several still remain to be mitigated and will likely take several hours more to complete, if not into tomorrow. Our teams have begun testing with this update but have reported we are still impacted at this time. We will continue to monitor the situation closely and will provide one more update this evening by 7PM PST, or sooner if we have additional information to share. Mar <var data-var='date'> 1</var>, <var data-var='time'>23:09</var> UTC Update - AWS is reporting positive signs of recovery at this time, but are still working on multiple mitigation paths to fully restore services. We continue to keep a close eye on the situation and will provide another update by 6PM PST, or sooner if we have additional information to share. Mar <var data-var='date'> 1</var>, <var data-var='time'>20:43</var> UTC Update - Current conflict in the region has led to objects impacting the AWS data center creating a fire earlier today. Power was shut down to prevent further damage. AWS is working on multiple mitigation paths to restore services as quickly as possible. We will provide the next update by 4PM PST or sooner if we have more to share. Mar <var data-var='date'> 1</var>, <var data-var='time'>15:11</var> UTC Monitoring - A power outage at an AWS facility in the me-central-1 (Mid-East) region may cause failures or slower than usual progress on cluster operations. AWS is aware of the issue and is working to restore power. We are monitoring the situation, and will provide updates as we receive them from AWS.

Cluster unavailability and degraded cluster operations in AWS me-central...

Feb <var data-var='date'> 9</var>, <var data-var='time'>15:20</var> UTC Resolved - Standard and Basic clusters continue to function normally. Feb <var data-var='date'> 9</var>, <var data-var='time'>04:15</var> UTC Monitoring - We have resolved an internal misconfiguration, and see that Standard and Basic clusters are functioning normally again. We will continue to monitor to ensure that the error does not recur. Feb <var data-var='date'> 9</var>, <var data-var='time'>03:04</var> UTC Investigating - We are investigating connectivity issues to Standard and Basic clusters on AWS.

Connectivity issues to Standard and Basic clusters on AWS

Feb <var data-var='date'> 2</var>, <var data-var='time'>19:46</var> UTC Resolved - We have deployed and verified a fix. Advanced clusters should now create within normal time frames. Feb <var data-var='date'> 2</var>, <var data-var='time'>19:31</var> UTC Update - We are continuing to work on the fix for this issue. Next update will be at 15:00 US/Eastern. Feb <var data-var='date'> 2</var>, <var data-var='time'>17:57</var> UTC Update - We are preparing a fix for deployment, which should restore AWS cluster creation times to normal levels. We will update the status page when the fix is deployed, or by 14:30 US/Eastern with more information. Feb <var data-var='date'> 2</var>, <var data-var='time'>16:56</var> UTC Identified - We have identified an issue that is causing Advanced cluster creation on AWS to take longer than usual. We are preparing a fix, and will update this status page with more information when we have an ETA for resolution.

Advanced cluster creation on AWS taking longer than expected

Oct <var data-var='date'>31</var>, <var data-var='time'>22:09</var> UTC Resolved - All cluster operations are working normally. Oct <var data-var='date'>31</var>, <var data-var='time'>20:18</var> UTC Monitoring - We have resolved the underlying issue that was preventing cluster creation and other cluster operations. We have re-enabled cluster creation on all clouds. We will monitor the situation to ensure that everything continues to operate normally. Oct <var data-var='date'>31</var>, <var data-var='time'>19:58</var> UTC Update - We are continuing to work on a fix for this issue. Next update will be by 4:30 PM US/Eastern time. Oct <var data-var='date'>31</var>, <var data-var='time'>18:59</var> UTC Update - We are continuing to work on a fix for this issue. Next update will be by 4:00 PM US/Eastern time. Oct <var data-var='date'>31</var>, <var data-var='time'>18:22</var> UTC Identified - We have identified the cause of cluster creation failures impacting Basic and Standard AWS clusters. As a precautionary measure, while we apply a fix, we have disabled all cluster creation in Cockroach Cloud. We will restore cluster creation when it is safe to do so. There is no SQL availability impact to any existing clusters. We will update here by 3:00 PM US/Eastern with more information. Oct <var data-var='date'>31</var>, <var data-var='time'>16:21</var> UTC Update - We are investigating errors with Basic and Standard clusters on AWS. Cluster creation, certain cluster edit operations (such as adding a region), and certain CockroachDB Cloud Console functionality (such as listing databases or users) are also impacted. Basic and Standard clusters on GCP are operating normally at this time. Oct <var data-var='date'>31</var>, <var data-var='time'>15:54</var> UTC Investigating - We are investigating errors that are causing delays in creation of Basic and Standard clusters on AWS. Basic and Standard cluster creation on GCP is operating normally at this time.

Standard and Basic cluster creation on AWS delayed

Oct <var data-var='date'>30</var>, <var data-var='time'>16:05</var> UTC Resolved - Cluster creation is operating normally, and all delayed clusters have finished creation. Oct <var data-var='date'>30</var>, <var data-var='time'>15:25</var> UTC Monitoring - We have applied a mitigation and observe that cluster creations are proceeding again. We will monitor all impacted cluster creations to ensure they succeed. Oct <var data-var='date'>30</var>, <var data-var='time'>14:50</var> UTC Investigating - We are investigating errors that cause creation for Advanced clusters to take longer than usual. Standard and Basic cluster creation is operating normally.

Advanced Cluster Creation Delayed

Oct <var data-var='date'>21</var>, <var data-var='time'>14:56</var> UTC Resolved - The earlier AWS outage in the us-east-1 region has been fully resolved. All CockroachDB Cloud operations, including cluster creation, scaling, and backups, are functioning normally again. We’ve verified recovery across affected systems and customer clusters, and normal operations have resumed. Oct <var data-var='date'>20</var>, <var data-var='time'>22:52</var> UTC Monitoring - AWS has resolved the underlying outage in the us-east-1 region, and we’re seeing recovery across CockroachDB Cloud operations. Cluster creation, scaling, and backups are now succeeding again. We’re continuing to monitor for full stability before marking this incident as resolved. Oct <var data-var='date'>20</var>, <var data-var='time'>13:28</var> UTC Identified - We’re currently impacted by an ongoing AWS outage in the us-east-1 region. Customers may experience failures or delays when creating new clusters, adding nodes, or running backups in this region. Existing clusters remain operational, but backup operations may be delayed or fail intermittently. We’re continuing to monitor AWS recovery efforts and will provide updates as more information becomes available.

AWS us-east-1 outage impacting cluster operations and backups

Sep <var data-var='date'>24</var>, <var data-var='time'>16:00</var> UTC Resolved - Google has reported the issue has been resolved and we've verified cluster operations are functional. Sep <var data-var='date'>24</var>, <var data-var='time'>12:31</var> UTC Identified - We are currently experiencing an incident impacting certain cluster operations on Google Cloud Platform due to an known ongoing Google Kubernetes-related issue. Customers may encounter errors when creating or editing clusters. Our engineering teams are actively monitoring the situation and communicating with Google regarding resolution.

Google Kubernetes incident impacting cluster operations in GCP.

Aug <var data-var='date'>26</var>, <var data-var='time'>04:00</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>26</var>, <var data-var='time'>03:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>25</var>, <var data-var='time'>19:34</var> UTC Scheduled - We will be performing scheduled maintenance on our control plane during this window. While we do not anticipate any impact, customers may observe brief disruptions to control plane operations (such as cluster creation, scaling, or similar jobs). There will be no impact to SQL traffic or cluster availability.

Planned Maintenance: Control Plane

Jul <var data-var='date'>29</var>, <var data-var='time'>23:35</var> UTC Resolved - We have confirmed resolution of the incident impacting SQL availability for the affected cluster. SQL availability is restored and the associated cluster is now healthy. Jul <var data-var='date'>29</var>, <var data-var='time'>23:17</var> UTC Monitoring - Correction from the original status update. This issue appears to have been isolated to cluster crl-prod-6rw. We have identified the cause, mitigated and confirmed that cluster availability has returned. We are currently completing additional validations. Jul <var data-var='date'>29</var>, <var data-var='time'>23:08</var> UTC Investigating - We are observing an incident impacting SQL availability across multiple Serverless clusters. We are currently investigating the issue.

SQL availability impacted across multiple Serverless clusters.

Jul <var data-var='date'>22</var>, <var data-var='time'>04:22</var> UTC Resolved - LetsEncrypt has indicated the issue has been mitigated. We have validated cluster creation behaviour is now returning to normal. Jul <var data-var='date'>21</var>, <var data-var='time'>21:39</var> UTC Identified - We are aware of an ongoing Incident with dependent service "Let's Encrypt": https://letsencrypt.status.io/, which may impact cluster creation and add region operations for CockroachDB Cloud Advanced clusters. We will update this status page with more information as it becomes available.

Dependent Service incident intermittently impacting CockroachCloud Operations

Jul <var data-var='date'>16</var>, <var data-var='time'>16:58</var> UTC Resolved - The maintenance has been completed, and the cloud console and API are working normally. Jul <var data-var='date'>16</var>, <var data-var='time'>16:01</var> UTC Update - Maintenance is beginning now. The next update will be before 17:00 UTC. Jul <var data-var='date'>16</var>, <var data-var='time'>12:30</var> UTC Identified - We will be performing a planned maintenance operation on Cockroach DB Cloud Console and the Cockroach DB Cloud API today from 16:00 - 17:00 UTC. During this time, you may experience errors attempting cluster create or edit operations. Cockroach DB Cloud Advanced, Standard, and Basic clusters will remain fully available during this time. (An earlier version of this notice incorrectly stated the time of maintenance as 14:00 - 15:00 UTC; the maintenance will be from 16:00 - 17:00)

Cloud Console and API Planned Maintenance 16:00 - 17:00 UTC

Jul <var data-var='date'> 3</var>, <var data-var='time'>17:39</var> UTC Resolved - We have corrected a misconfiguration which was preventing cluster operations from succeeding. We are monitoring the success of cluster operations already in progress and new operations. Jul <var data-var='date'> 3</var>, <var data-var='time'>16:58</var> UTC Investigating - We are investigating an issue that may prevent or delay cluster operations from succeeding.

Cluster operations impaired

Jul <var data-var='date'> 2</var>, <var data-var='time'>20:46</var> UTC Resolved - All cluster operations are succeeding normally at this time. Jul <var data-var='date'> 2</var>, <var data-var='time'>19:32</var> UTC Monitoring - We continue to see cluster operations succeeding, and will actively monitor to ensure the issue does not reoccur. Jul <var data-var='date'> 2</var>, <var data-var='time'>18:50</var> UTC Identified - We have identified the issue preventing cluster operations from proceeding, and we see that operations are moving forward. We will next update this incident by 16:00 EDT. Jul <var data-var='date'> 2</var>, <var data-var='time'>17:42</var> UTC Investigating - We are investigating cluster operations, including creating or editing clusters, that are taking longer than usual.

Cluster operations taking longer than expected

Jun <var data-var='date'>27</var>, <var data-var='time'>22:36</var> UTC Resolved - We have identified and rolled out a fix for the issue impacting cluster creation in AWS. This incident is now resolved. Jun <var data-var='date'>27</var>, <var data-var='time'>22:29</var> UTC Identified - We have identified an issue impacting Basic and Standard tier cluster creation in AWS. We have conducted an initial investigation and actively working to resolve the issue.

Issue impacting Basic and Standard tier cluster creation in AWS.

Jun <var data-var='date'>12</var>, <var data-var='time'>21:31</var> UTC Resolved - Google has reported that mitigations have been applied and services are now recovering. Jun <var data-var='date'>12</var>, <var data-var='time'>19:54</var> UTC Monitoring - Google has updated their public status page to indicate the underlying issue is resolved, and individual Google Cloud services are in the process of restoring full service. We are continuing to monitor the issue and impact to CockroachDB Cloud. Jun <var data-var='date'>12</var>, <var data-var='time'>19:08</var> UTC Update - In addition to cluster operations, backups to Google Cloud Storage, including managed backups from CockroachDB Cloud clusters on GCP, may be impacted. Jun <var data-var='date'>12</var>, <var data-var='time'>18:22</var> UTC Identified - We are aware of errors in the Google Cloud API which may impact cluster creation and edit operations for CockroachDB Cloud Advanced clusters in GCP. We will update this status page with more information as it becomes available.

Upstream cloud provider API is unavailable

Jun <var data-var='date'> 4</var>, <var data-var='time'>21:35</var> UTC Resolved - The issue that was preventing metrics pages from loading in the Cockroach Cloud console for Basic and Standard tier clusters has been fully resolved. Metrics are now loading as expected, and we’ve received confirmation from our service provider that the underlying issue has been addressed. We will continue to monitor for any signs of recurrence, but no further impact is expected at this time. Thank you for your patience. Jun <var data-var='date'> 4</var>, <var data-var='time'>20:19</var> UTC Monitoring - Metrics visualizations are now loading as expected. We are continuing to monitor system behavior to ensure stability and will mark this incident as resolved once we confirm full recovery. Jun <var data-var='date'> 4</var>, <var data-var='time'>19:31</var> UTC Identified - We’ve identified the source of the issue that was preventing metrics pages from loading in the Cockroach Cloud console for Basic and Standard tier clusters. The underlying service has recovered, and metrics visualizations are now loading as expected. We are continuing to monitor the situation to ensure full stability. Jun <var data-var='date'> 4</var>, <var data-var='time'>19:10</var> UTC Investigating - We are currently investigating an issue that is preventing some metrics pages from loading in the Cockroach Cloud console for Basic and Standard tier clusters. Metrics data collection remains unaffected; however, we are seeing unexpected errors when retrieving metrics for display in the console. We are actively working to identify the root cause and restore full functionality. Further updates will be provided as our investigation continues.

Metrics Pages Unavailable in Cockroach Cloud Console for Basic and Standard Clusters

Jun <var data-var='date'> 1</var>, <var data-var='time'>07:29</var> UTC Resolved - Incident Start AWS experienced a brief network blip in the eu-west-1, eu-west-2, and eu-central-1 regions. Clusters in these regions were unavailable between June 1, 19:29–19:35 UTC. Incident End The network issue affecting clusters in the impacted AWS regions has been fully resolved *automatically* as of 19:35 UTC. All affected clusters are now operating normally. Please contact support if you have any concerns.

A brief network disruption affecting clusters in the AWS eu-west-1, eu-west-2, and eu-central-1 regions.

Nov <var data-var='date'>19</var>, <var data-var='time'>18:36</var> UTC Resolved - The Engineering team has isolated and resolved the elevated error rate for all affected clusters. Nov <var data-var='date'>19</var>, <var data-var='time'>17:06</var> UTC Monitoring - The root cause of the issue was identified and resolved. Engineering is monitoring the situation. Nov <var data-var='date'>19</var>, <var data-var='time'>16:48</var> UTC Investigating - We have received alerts indicating elevated error rates on isolated Standard and Basic clusters. The Engineering team is currently investigating the issue.

Elevated error rate for some Standard and Basic clusters

Nov <var data-var='date'>12</var>, <var data-var='time'>01:00</var> UTC Resolved - On Tuesday Nov 12, at approximately 1am UTC, we received alerts of elevated errors due to an underlying host hardware failure. The workloads on this host were migrated to a healthy host and the errors resolved once the migration was complete.

Elevated errors on serverless platform

Oct <var data-var='date'>24</var>, <var data-var='time'>21:05</var> UTC Resolved - The upstream incident has been resolved, and we have confirmed that cluster creation is working normally. Oct <var data-var='date'>24</var>, <var data-var='time'>20:06</var> UTC Update - We are continuing to monitor the upstream incident. Oct <var data-var='date'>24</var>, <var data-var='time'>19:00</var> UTC Identified - We are aware of an AWS incident that is preventing successful completion of Advanced cluster creation and region addition. Once the cloud provider has resolved their incident, we will ensure clusters create successfully.

Is CockroachDB Cloud down?

CockroachDB Cloud status is UP

Lastest published events

Cluster connectivity and execution issues

Cluster Creation Failure

Unable to accept invites

CockroachDB Cloud Services, Components and Regions

Recent CockroachDB Cloud events

Cluster connectivity and execution issues

Cluster Creation Failure

Unable to accept invites

Degraded performance in one AWS us-east-1 availability zone

Cloud Console Social Login Auth Unavailable

Cluster unavailability and degraded cluster operations in AWS me-central...