Is Cockroach Labs down?

Last checked 5m ago
Current status
Cockroach Labs is up

No incidents right now.

Official status page: https://status.cockroachlabs.cloud · Polled every 5 minutes · 13 components tracked

Cockroach Labs is operational right now. Last checked 5m ago; the most recent incident resolved 18d ago.

Real-time Cockroach Labs status, recent outages, and incident history — pulled directly from Cockroach Labs's official status page at https://status.cockroachlabs.cloud every 5 minutes. Pingoru tracks 13 Cockroach Labs services and has captured 3 incidents in the last 90 days (99.66% uptime). Get email, Slack, Discord, or webhook alerts the moment Cockroach Labs reports a new incident — free for 5 monitors, no credit card.

Users who monitor Cockroach Labs also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
Cockroach Labs uptime 99.66% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 16m
    Started Jul 12, 2026, 08:08 PM UTC · Resolved Jul 12, 2026, 09:24 PM UTC
    CockroachDB Basic/Standard
    Timeline · 2 updates
    • investigating · Jul 12, 2026, 08:08 PM UTC

      We are currently aware of and investigating a cluster creation failure. Teams are engaged and actively working to mitigate as quickly as possible.

    • resolved · Jul 12, 2026, 09:24 PM UTC

      The cluster creation issue has been restored. Issue is resolved.

    Latest: The cluster creation issue has been restored. Issue is resolved.

  2. Resolved 36m
    Started Jun 09, 2026, 09:26 PM UTC · Resolved Jun 09, 2026, 10:02 PM UTC
    CockroachDB Cloud Console
    Timeline · 2 updates
    • identified · Jun 09, 2026, 09:26 PM UTC

      We have identified a minor issue affecting Cloud customers who are unable to accept invites, preventing them from inviting new users to their organizations. Internal teams are aware and a fix is in flight. ETA: 30min - 1hour. We will provide the next update at the top of the hour or prior if the fix is deployed before that time.

    • resolved · Jun 09, 2026, 10:02 PM UTC

      Fix deployment is complete, tested and verified.

    Latest: Fix deployment is complete, tested and verified.

  3. Resolved 19h 40m
    Started May 08, 2026, 02:13 AM UTC · Resolved May 08, 2026, 09:53 PM UTC
    CockroachDB Advanced
    Timeline · 4 updates
    • monitoring · May 08, 2026, 02:13 AM UTC

      AWS is experiencing elevated error rates and degraded performance in a single availability zone in the us-east-1 region. CockroachDB clusters in us-east-1 remain available, and we are monitoring the situation and taking corrective action as appropriate to ensure SQL availability of CockroachDB clusters in this region.

    • monitoring · May 08, 2026, 03:24 AM UTC

      AWS's latest status update reports that they are continuing to work on the situation, and progress is slow. AWS has advised a next update time at 05:00 UTC. We continue to monitor the situation and take appropriate action to ensure uptime and availability for Cockroach DB clusters. We'll next update by about 05:00 UTC when we learn more from AWS.

    • monitoring · May 08, 2026, 08:25 AM UTC

      AWS reports continued progress towards resolving the issue in the US-EAST-1 Region and is working towards full recovery. Affected services may continue to experience elevated error rates and latencies until recovery is complete. We continue to monitor the situation and take appropriate action to ensure uptime and availability for CockroachDB clusters. We'll provide another update as we learn more from AWS.

    • resolved · May 08, 2026, 09:53 PM UTC

      All CockroachDB clusters in the affected AWS availability zone have been restored to a fully operational state. We will continue to monitor the upstream incident from AWS, but do not expect any impact to CockroachDB clusters.

    Latest: All CockroachDB clusters in the affected AWS availability zone have been restored to a fully operational state. We will continue to monitor the upstream incident from AWS, but do n…

Outage history

Past 90 days · 3 incidents View full outage history →