CockroachDB

CockroachDB takes its name from the organism that survives nearly anything — an aspiration that describes its core design goal accurately. Founded in 2015 by former Google engineers who worked on Spanner, the distributed database underlying Google's core infrastructure, Cockroach Labs built a distributed SQL database that provides strong consistency across geographically distributed nodes without sacrificing familiar SQL semantics. The key design decisions — serialisable isolation, automatic sharding, and multi-region active-active replication — address failure modes that eventually-consistent NoSQL databases accepted as unavoidable trade-offs.

CockroachDB Cloud offers Serverless and Dedicated cluster options, with the Dedicated tier providing predictable performance isolation and the Serverless tier automatically scaling to zero and charging by resource consumption. The CockroachDB Cloud Console provides cluster management, performance monitoring, backup scheduling, and SQL editor access through a web interface. The distributed nature of the database means operations teams interacting with CockroachDB through the Cloud Console or the DB Console (the built-in cluster monitoring dashboard) have visibility into replication health, range distribution, and node liveness — metrics that reflect the database's distributed state in real time.

CockroachDB service problems present across the cluster management and database access layers distinctly. The Cloud Console failing to load blocks cluster provisioning, connection string retrieval, and backup management, though existing cluster operations continue independently of the management plane. SQL client connections fail with "connection refused" or TLS handshake errors when the cluster's load balancer layer is degraded. Range under-replication warnings appear in the DB Console when a node loses contact with its peers, indicating a replication health problem that, if persistent, could affect consistency guarantees. Serverless cluster scaling events sometimes introduce brief connection interruptions as routing is updated. Webhook-delivered cluster alerts stop delivering when the alerting backend has connectivity issues.

Outage.gg tracks CockroachDB service status using real-time community reports from developers and database administrators. If the Cloud Console is unavailable, cluster connections are failing, or replication health is degraded, the live status page shows current impact from the CockroachDB user community.