Cluster connectivity and execution issues
Following an extended period of monitoring, the team has confirmed that the cluster remains healthy and stable.
The latest update from CockroachDB Cloud.
State
Resolved
Started
88 d ago
2026-08-04 23:46 UTC
Lasted
20 h 4 min
until 2026-08-05 19:50 UTC
Worst impact
Partial outage
Timeline
5 updatesInvestigating
4 h 9 min 21%
Monitoring
15 h 55 min 79%
Updates
Times in UTCAs posted by CockroachDB Cloud
Following an extended period of monitoring, the team has confirmed that the cluster remains healthy and stable.
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.
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.
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.
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.
Affected components
1CockroachDB Cloud in the last 90 days
Full historyIncidents in 90 days
5
Days with an incident
7
Median duration
7 h
This incident
2.9× the median
Other CockroachDB Cloud incidents
All incidentsCockroachDB Cloud·gcp-eu-west2-b-availability-zone-issues
GCP has mitigated the power event that caused this disruption in the europe-west2 region. All GCP and CRL services has returned to normal operation. No further action is required.
CockroachDB Cloud·Stock out issues in GCP us-central1
We 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 another region when spinning up new clusters to circumvent the capacity problems observed with us-central1.
CockroachDB Cloud·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 has returned to normal and all affected clusters are operating as expected. We apologize for any disruption this may have caused. If you continue to experience any issues, please contact support.
CockroachDB Cloud·Cloud Latency, Delays, Connection Issues
Google 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.
Follow CockroachDB Cloud
Your coding agent knows when CockroachDB Cloud is down, and tells you when a failure is theirs, not yours. You can also get CockroachDB Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "cockroachdb" and tell me if CockroachDB Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=cockroachdb/feed subscribe https://outages.cc/feed.xml?providers=cockroachdbFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane