CockroachDB Outage History
14 incidents recorded over the last 365 days, 14 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded CockroachDB Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 6, 2026 | Stock out issues in GCP us-central1We are continuing to monitor this issue; however Google can not provide an ETA as to when it will be resolved. We will continue to work with them to obtain the needed capacity. Customers are still advised to choose… | 22h 11m | Resolved |
| Sep 17, 2026 | Connection attempts failing for multiple Basic tenants in GCP South America (southamerica-east1).This incident has been resolved. CockroachDB Cloud (Basic) clusters hosted in GCP South America (São Paulo / southamerica-east1) experienced network connectivity issues that have now been fully restored. Connectivity… | 1h 30m | Resolved |
| Sep 1, 2026 | Cloud Latency, Delays, Connection IssuesGoogle impacts are now reported as fully resolved. Internal teams have confirmed this report. All services are restored. Should you need further help, please reach out and file a ticket with Support. | 4h 8m | Resolved |
| Aug 4, 2026 | Cluster connectivity and execution issuesFollowing an extended period of monitoring, the team has confirmed that the cluster remains healthy and stable. | 20h 3m | Resolved |
| Jul 12, 2026 | Cluster Creation FailureThe cluster creation issue has been restored. Issue is resolved. | 1h 16m | Resolved |
| Jun 9, 2026 | Unable to accept invitesFix deployment is complete, tested and verified. | 36 min | Resolved |
| May 8, 2026 | Degraded performance in one AWS us-east-1 availability zoneAll 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… | 19h 40m | Resolved |
| Mar 18, 2026 | Cloud Console Social Login Auth UnavailableSocial login for Microsoft accounts is now available. Please reach out to support if you continue to experience issues. | 39 min | Resolved |
| Mar 1, 2026 | Cluster unavailability and degraded cluster operations in AWS me-central...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… | 244h 39m | Resolved |
| Feb 9, 2026 | Connectivity issues to Standard and Basic clusters on AWSStandard and Basic clusters continue to function normally. | 12h 16m | Resolved |
| Feb 2, 2026 | Advanced cluster creation on AWS taking longer than expectedWe have deployed and verified a fix. Advanced clusters should now create within normal time frames. | 2h 49m | Resolved |
| Oct 31, 2025 | Standard and Basic cluster creation on AWS delayedAll cluster operations are working normally. | 6h 15m | Resolved |
| Oct 30, 2025 | Advanced Cluster Creation DelayedCluster creation is operating normally, and all delayed clusters have finished creation. | 1h 15m | Resolved |
| Oct 20, 2025 | AWS us-east-1 outage impacting cluster operations and backupsThe 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… | 25h 27m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next CockroachDB incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This CockroachDB Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before CockroachDB acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single CockroachDB outage in this window ran 10d 4h, against a mean recovery of 1d 1h. If you depend on CockroachDB in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.