CockroachDB Status · History · Incident #2287

RESOLVED

Degraded performance in one AWS us-east-1 availability zone

Major · Started May 8, 2026 · 2:13 AM

  • Duration

    19h 40m

  • Severity

    Major

  • Detection lead

  • User reports

Summary

Degraded performance in one AWS us-east-1 availability zone

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.


  • Started

    May 8, 2026 · 2:13 AM

  • Resolved

    May 8, 2026 · 9:53 PM

  • Duration

    19h 40m

  • Severity

    Major

Event timeline

How this incident unfolded

  • Monitoring

    May 8 · 2:13 AM CockroachDB

    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 8 · 3:24 AM CockroachDB

    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 8 · 8:25 AM CockroachDB

    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 8 · 9:53 PM CockroachDB

    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.

Get alerted before the next CockroachDB outage.

Pulsetic catches degradations minutes before vendors acknowledge them.

Start monitoring free
Hey there 👋  Friends from designmodo are here to help!