Incidents

Quoted from each provider's status page.

OngoingAll clear
Where, last 194 daysPlaces 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.
3 places · 5 not pinned
Iowa (us-central1): 1 incident · CockroachDB CloudSão Paulo (southamerica-east1): 1 incident · CockroachDB CloudVirginia (us-east-1): 1 incident · CockroachDB Cloud
Last 90 daysOne square per UTC day, coloured by the worst incident that day. Ongoing incidents count today.
0 Sev 1 days · 83 clean
AugSepOctMonWedFri
CleanSev 3–4Sev 2Sev 1

Tue, Oct 201 incident

07:53SEV 2CockroachDB Cloud · gcp-eu-west2-b-availability-zone-issuesCockroachDB Cloud - CockroachDB Basic/Standard, CockroachDB Cloud - CockroachDB Advanced · source7h 00m

Tue, Oct 61 incident

21:21SEV 3CockroachDB Cloud · Stock out issues in GCP us-central1CockroachDB Cloud - CockroachDB Advanced, Cockroach Continuum - Continuum Mission Critical · source22h 12m

Thu, Sep 171 incident

19:08SEV 2CockroachDB Cloud · Connection attempts failing for multiple Basic tenants in GCP South America (southamerica-east1).CockroachDB Cloud - CockroachDB Basic/Standard · source1h 31m

Tue, Sep 11 incident

15:36SEV 2CockroachDB Cloud · Cloud Latency, Delays, Connection IssuesCockroachDB Basic/Standard · source4h 09m

Tue, Aug 41 incident

23:46SEV 2CockroachDB Cloud · Cluster connectivity and execution issuesCockroachDB Basic/Standard · source20h 04m

Sun, Jul 121 incident

20:08SEV 3CockroachDB Cloud · Cluster Creation FailureCockroachDB Basic/Standard · source1h 17m

Tue, Jun 91 incident

21:26SEV 3CockroachDB Cloud · Unable to accept invitesCloud Console, CockroachDB Cloud Console · source36m

Fri, May 81 incident

02:13SEV 2CockroachDB Cloud · Degraded performance in one AWS us-east-1 availability zoneCockroachDB Advanced · source19h 40m