outages.live
Live

CockroachDB Cloud

CockroachDB Cloud is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

5

Days with an incident

6

Median duration

7 h

Longest incident

22 h 12 min

Components

15

Shared Services

Cloud Console Operational
90 days agoNo incidentsToday
Telemetry & Metrics Operational
90 days agoNo incidentsToday

CockroachDB Cloud

CockroachDB Basic/Standard Operational
90 days ago4 days with an incidentToday
CockroachDB Advanced Operational
90 days ago3 days with an incidentToday

User Authentication

AU Operational
90 days agoNo incidentsToday
EU-2 Operational
90 days agoNo incidentsToday
EU-1 Operational
90 days agoNo incidentsToday
JP-1 Operational
90 days agoNo incidentsToday
UK-1 Operational
90 days agoNo incidentsToday
US-2 Operational
90 days agoNo incidentsToday
US-3 Operational
90 days agoNo incidentsToday
US-4 Operational
90 days agoNo incidentsToday
US-1 Operational
90 days agoNo incidentsToday

Cockroach Continuum

Continuum Standard Operational
90 days agoNo incidentsToday
Continuum Mission Critical Operational
90 days ago2 days with an incidentToday

Past incidents

Provider status pageTimes in UTC

Oct 20, 2026

Duration7 h07:53 to 14:53gcp-eu-west2-b-availability-zone-issuesPartial outage

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.

Oct 6, 2026

Duration22 h 12 min21:21 to 19:33Stock out issues in GCP us-central1Degraded

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.

Sep 17, 2026

Duration1 h 31 min19:08 to 20:39Connection attempts failing for multiple Basic tenants in GCP South America (southamerica-east1).Partial outage

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.

Sep 1, 2026

Duration4 h 9 min15:36 to 19:45Cloud Latency, Delays, Connection IssuesPartial outage

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.

Aug 4, 2026

Duration20 h 4 min23:46 to 19:50Cluster connectivity and execution issuesPartial outage

Following an extended period of monitoring, the team has confirmed that the cluster remains healthy and stable.

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.

Prompt
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.live/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.

RSS
https://outages.live/feed.xml?providers=cockroachdb
Slack
/feed subscribe https://outages.live/feed.xml?providers=cockroachdb

Go from tracking outages to fixing production issues with Polylane.

Try Polylane