- Detected by Pingoru
- Jun 09, 2026, 09:26 PM UTC
- Resolved
- Jun 09, 2026, 10:02 PM UTC
- Duration
- 36m
Affected: CockroachDB Cloud Console
Timeline · 2 updates
-
identified Jun 09, 2026, 09:26 PM UTC
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.
-
resolved Jun 09, 2026, 10:02 PM UTC
Fix deployment is complete, tested and verified.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 02:13 AM UTC
- Resolved
- May 08, 2026, 09:53 PM UTC
- Duration
- 19h 40m
Affected: CockroachDB Advanced
Timeline · 4 updates
-
monitoring May 08, 2026, 02:13 AM UTC
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.
-
monitoring May 08, 2026, 03:24 AM UTC
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.
-
monitoring May 08, 2026, 08:25 AM UTC
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.
-
resolved May 08, 2026, 09:53 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2026, 03:23 PM UTC
- Resolved
- Mar 18, 2026, 04:02 PM UTC
- Duration
- 39m
Affected: CockroachDB Cloud Console
Timeline · 2 updates
-
investigating Mar 18, 2026, 03:23 PM UTC
Social logins for customers using personal/non-SSO Microsoft accounts is currently unavailable. Our teams are aware and currently investigating.
-
resolved Mar 18, 2026, 04:02 PM UTC
Social login for Microsoft accounts is now available. Please reach out to support if you continue to experience issues.
Read the full incident report →
- Detected by Pingoru
- Mar 01, 2026, 03:11 PM UTC
- Resolved
- Mar 11, 2026, 07:51 PM UTC
- Duration
- 10d 4h
Affected: CockroachDB Advanced
Timeline · 8 updates
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 03:04 AM UTC
- Resolved
- Feb 09, 2026, 03:20 PM UTC
- Duration
- 12h 16m
Affected: CockroachDB Basic/Standard
Timeline · 3 updates
-
investigating Feb 09, 2026, 03:04 AM UTC
We are investigating connectivity issues to Standard and Basic clusters on AWS.
-
monitoring Feb 09, 2026, 04:15 AM UTC
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.
-
resolved Feb 09, 2026, 03:20 PM UTC
Standard and Basic clusters continue to function normally.
Read the full incident report →
- Detected by Pingoru
- Feb 02, 2026, 04:56 PM UTC
- Resolved
- Feb 02, 2026, 07:46 PM UTC
- Duration
- 2h 49m
Affected: CockroachDB Advanced
Timeline · 4 updates
-
identified Feb 02, 2026, 04:56 PM UTC
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.
-
identified Feb 02, 2026, 05:57 PM UTC
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.
-
identified Feb 02, 2026, 07:31 PM UTC
We are continuing to work on the fix for this issue. Next update will be at 15:00 US/Eastern.
-
resolved Feb 02, 2026, 07:46 PM UTC
We have deployed and verified a fix. Advanced clusters should now create within normal time frames.
Read the full incident report →
Critical October 31, 2025 - Detected by Pingoru
- Oct 31, 2025, 03:54 PM UTC
- Resolved
- Oct 31, 2025, 10:09 PM UTC
- Duration
- 6h 15m
Affected: CockroachDB Basic/Standard
Timeline · 7 updates
-
investigating Oct 31, 2025, 03:54 PM UTC
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.
-
investigating Oct 31, 2025, 04:21 PM UTC
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.
-
identified Oct 31, 2025, 06:22 PM UTC
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.
-
identified Oct 31, 2025, 06:59 PM UTC
We are continuing to work on a fix for this issue. Next update will be by 4:00 PM US/Eastern time.
-
identified Oct 31, 2025, 07:58 PM UTC
We are continuing to work on a fix for this issue. Next update will be by 4:30 PM US/Eastern time.
-
monitoring Oct 31, 2025, 08:18 PM UTC
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.
-
resolved Oct 31, 2025, 10:09 PM UTC
All cluster operations are working normally.
Read the full incident report →
- Detected by Pingoru
- Oct 30, 2025, 02:50 PM UTC
- Resolved
- Oct 30, 2025, 04:05 PM UTC
- Duration
- 1h 15m
Affected: CockroachDB Advanced
Timeline · 3 updates
-
investigating Oct 30, 2025, 02:50 PM UTC
We are investigating errors that cause creation for Advanced clusters to take longer than usual. Standard and Basic cluster creation is operating normally.
-
monitoring Oct 30, 2025, 03:25 PM UTC
We have applied a mitigation and observe that cluster creations are proceeding again. We will monitor all impacted cluster creations to ensure they succeed.
-
resolved Oct 30, 2025, 04:05 PM UTC
Cluster creation is operating normally, and all delayed clusters have finished creation.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 01:28 PM UTC
- Resolved
- Oct 21, 2025, 02:56 PM UTC
- Duration
- 1d 1h
Timeline · 3 updates
-
identified Oct 20, 2025, 01:28 PM UTC
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.
-
monitoring Oct 20, 2025, 10:52 PM UTC
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.
-
resolved Oct 21, 2025, 02:56 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Sep 24, 2025, 12:31 PM UTC
- Resolved
- Sep 24, 2025, 04:00 PM UTC
- Duration
- 3h 28m
Affected: CockroachDB Advanced
Timeline · 2 updates
-
identified Sep 24, 2025, 12:31 PM UTC
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.
-
resolved Sep 24, 2025, 04:00 PM UTC
Google has reported the issue has been resolved and we've verified cluster operations are functional.
Read the full incident report →
- Detected by Pingoru
- Jul 29, 2025, 11:08 PM UTC
- Resolved
- Jul 29, 2025, 11:35 PM UTC
- Duration
- 26m
Affected: CockroachDB Basic/Standard
Timeline · 3 updates
-
investigating Jul 29, 2025, 11:08 PM UTC
We are observing an incident impacting SQL availability across multiple Serverless clusters. We are currently investigating the issue.
-
monitoring Jul 29, 2025, 11:17 PM UTC
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.
-
resolved Jul 29, 2025, 11:35 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2025, 09:39 PM UTC
- Resolved
- Jul 22, 2025, 04:22 AM UTC
- Duration
- 6h 42m
Affected: CockroachDB Advanced
Timeline · 2 updates
-
identified Jul 21, 2025, 09:39 PM UTC
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.
-
resolved Jul 22, 2025, 04:22 AM UTC
LetsEncrypt has indicated the issue has been mitigated. We have validated cluster creation behaviour is now returning to normal.
Read the full incident report →
- Detected by Pingoru
- Jul 03, 2025, 04:58 PM UTC
- Resolved
- Jul 03, 2025, 05:39 PM UTC
- Duration
- 41m
Affected: CockroachDB Basic/StandardCockroachDB Advanced
Timeline · 2 updates
-
investigating Jul 03, 2025, 04:58 PM UTC
We are investigating an issue that may prevent or delay cluster operations from succeeding.
-
resolved Jul 03, 2025, 05:39 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2025, 05:42 PM UTC
- Resolved
- Jul 02, 2025, 08:46 PM UTC
- Duration
- 3h 3m
Timeline · 4 updates
-
investigating Jul 02, 2025, 05:42 PM UTC
We are investigating cluster operations, including creating or editing clusters, that are taking longer than usual.
-
identified Jul 02, 2025, 06:50 PM UTC
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.
-
monitoring Jul 02, 2025, 07:32 PM UTC
We continue to see cluster operations succeeding, and will actively monitor to ensure the issue does not reoccur.
-
resolved Jul 02, 2025, 08:46 PM UTC
All cluster operations are succeeding normally at this time.
Read the full incident report →
- Detected by Pingoru
- Jun 27, 2025, 10:29 PM UTC
- Resolved
- Jun 27, 2025, 10:36 PM UTC
- Duration
- 6m
Affected: CockroachDB Basic/Standard
Timeline · 2 updates
-
identified Jun 27, 2025, 10:29 PM UTC
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.
-
resolved Jun 27, 2025, 10:36 PM UTC
We have identified and rolled out a fix for the issue impacting cluster creation in AWS. This incident is now resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 06:22 PM UTC
- Resolved
- Jun 12, 2025, 09:31 PM UTC
- Duration
- 3h 8m
Affected: CockroachDB Advanced
Timeline · 4 updates
-
identified Jun 12, 2025, 06:22 PM UTC
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.
-
identified Jun 12, 2025, 07:08 PM UTC
In addition to cluster operations, backups to Google Cloud Storage, including managed backups from CockroachDB Cloud clusters on GCP, may be impacted.
-
monitoring Jun 12, 2025, 07:54 PM UTC
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.
-
resolved Jun 12, 2025, 09:31 PM UTC
Google has reported that mitigations have been applied and services are now recovering.
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2025, 07:10 PM UTC
- Resolved
- Jun 04, 2025, 09:35 PM UTC
- Duration
- 2h 25m
Affected: CockroachDB Cloud Console
Timeline · 4 updates
-
investigating Jun 04, 2025, 07:10 PM UTC
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.
-
identified Jun 04, 2025, 07:31 PM UTC
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.
-
monitoring Jun 04, 2025, 08:19 PM UTC
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.
-
resolved Jun 04, 2025, 09:35 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2025, 07:29 AM UTC
- Resolved
- Jun 01, 2025, 07:29 AM UTC
- Duration
- —
Affected: CockroachDB Basic/Standard
Timeline · 1 update
-
resolved Jun 02, 2025, 07:45 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Nov 19, 2024, 04:48 PM UTC
- Resolved
- Nov 19, 2024, 06:36 PM UTC
- Duration
- 1h 48m
Timeline · 3 updates
-
investigating Nov 19, 2024, 04:48 PM UTC
We have received alerts indicating elevated error rates on isolated Standard and Basic clusters. The Engineering team is currently investigating the issue.
-
monitoring Nov 19, 2024, 05:06 PM UTC
The root cause of the issue was identified and resolved. Engineering is monitoring the situation.
-
resolved Nov 19, 2024, 06:36 PM UTC
The Engineering team has isolated and resolved the elevated error rate for all affected clusters.
Read the full incident report →
- Detected by Pingoru
- Nov 13, 2024, 04:24 PM UTC
- Resolved
- Nov 12, 2024, 01:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Nov 13, 2024, 04:24 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Oct 24, 2024, 07:00 PM UTC
- Resolved
- Oct 24, 2024, 09:05 PM UTC
- Duration
- 2h 4m
Timeline · 3 updates
-
identified Oct 24, 2024, 08:04 PM UTC
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.
-
identified Oct 24, 2024, 08:06 PM UTC
We are continuing to monitor the upstream incident.
-
resolved Oct 24, 2024, 09:15 PM UTC
The upstream incident has been resolved, and we have confirmed that cluster creation is working normally.
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2024, 02:15 PM UTC
- Resolved
- Sep 25, 2024, 02:30 PM UTC
- Duration
- 15m
Affected: CockroachDB Basic/Standard
Timeline · 2 updates
-
investigating Sep 25, 2024, 02:27 PM UTC
We are aware of an issue affecting a small number of serverless clusters that is causing unavailability. Our SRE team is investigating.
-
resolved Sep 25, 2024, 02:35 PM UTC
We have deployed a mitigation and all clusters are available again.
Read the full incident report →
- Detected by Pingoru
- Sep 18, 2024, 07:24 PM UTC
- Resolved
- Sep 18, 2024, 09:33 PM UTC
- Duration
- 2h 9m
Affected: CockroachDB Advanced
Timeline · 2 updates
-
identified Sep 18, 2024, 07:24 PM UTC
We have identified an issue where some AWS clusters are unable to list available backups on the "Backups and Restore" page. Backups are still being performed and available if a restore of a database or table is required.
-
resolved Sep 18, 2024, 09:33 PM UTC
We have deployed a fix which has resolved the issue.
Read the full incident report →
- Detected by Pingoru
- Aug 09, 2024, 09:37 PM UTC
- Resolved
- Aug 09, 2024, 10:33 PM UTC
- Duration
- 56m
Affected: CockroachDB Basic/Standard
Timeline · 2 updates
-
investigating Aug 09, 2024, 09:37 PM UTC
We are investigating increased errors in restore operations to serverless clusters.
-
resolved Aug 09, 2024, 10:33 PM UTC
We have corrected a misconfiguration that was causing restore errors, and have applied the fix to all serverless clusters.
Read the full incident report →
- Detected by Pingoru
- Jul 18, 2024, 11:20 PM UTC
- Resolved
- Jul 19, 2024, 03:09 PM UTC
- Duration
- 15h 49m
Affected: CockroachDB Advanced
Timeline · 3 updates
-
identified Jul 18, 2024, 11:36 PM UTC
CockroachDB clusters with nodes in Microsoft’s Central US region may be unavailable. We are monitoring the situation and waiting for an update from Microsoft. For more information see Microsoft’s status page at https://azure.status.microsoft/en-us/status/
-
monitoring Jul 19, 2024, 05:49 AM UTC
Latest update from Microsoft status page is all green, with some residual effects. CockroachDB clusters with nodes in Microsoft’s Central US region are all up and running with some background jobs like backup failing. We are continuously monitoring the status of the clusters.
-
resolved Jul 19, 2024, 03:09 PM UTC
We have now verified that all Azure clusters are operational and have completed backup jobs.
Read the full incident report →
