Incidents
Quoted from each provider's status page.
OngoingAll clear
Where, Dec 4, 2025 – May 17, 2026
Places named on the status page: cloud regions, cities, countries, data centres. An incident naming only a broad area (Europe, APAC) is counted under the map, not pinned.Last 90 days
One square per UTC day, coloured by the worst incident that day. Ongoing incidents count today.CleanSev 3–4Sev 2Sev 1
Fri, May 81 incident
02:13SEV 2CockroachDB Cloud · Degraded performance in one AWS us-east-1 availability zoneCockroachDB Advanced · source19h 40m
Wed, Mar 181 incident
15:23SEV 3CockroachDB Cloud · Cloud Console Social Login Auth UnavailableCloud Console, CockroachDB Cloud Console · source39m
Sun, Mar 11 incident
15:11SEV 2CockroachDB Cloud · Cluster unavailability and degraded cluster operations in AWS me-central...CockroachDB Advanced · source10d 4h
Mon, Feb 91 incident
03:04SEV 2CockroachDB Cloud · Connectivity issues to Standard and Basic clusters on AWSCockroachDB Basic/Standard · source12h 16m
Mon, Feb 21 incident
16:56SEV 3CockroachDB Cloud · Advanced cluster creation on AWS taking longer than expectedCockroachDB Advanced · source2h 50m