Rewindex

CompaniesCouchbaseIncidents

Couchbase: Capella Operations Impacted by AWS Outage

MinorStatus: resolvedStarted Resolved (9.5 h)6 updatesstspg.io (opens in new tab)
Part of an outage event

AWS us-east-1 outage, Oct 20, 2025 · 141 vendors, 181 incidents

Couchbase’s incident blames AWS as the cause. (hop 1, posted +4 h 52 min vs AWS’s own post)

“…Capella Operations Impacted by AWS Outage All services are operational. All services are operational. AWS continues to apply additional mitigations to address throttling of new EC2 instance launches.…”

Swipe sideways to see the whole diagram.

blamed Twilioblamed Webflowblamed BasetenAWS us-east-1posted 07:11 UTCPosted before AWS did5 vendors, 4 blamed AWSSalesforce, Descope, Ashby +2Within an hour18 vendors, 17 blamed AWSAsana, Firebolt, Monday.com +151 to 4 hours later30 vendors, 29 blamed AWSSingleStore, Loops, Buildkite +27Later45 vendors, 44 blamed AWSRudderStack, Airbyte, Unbounce +42Twilioposted +15 minBigCommerce+2 h 46 minWebflowposted +4 h 37 min, did not name AWSRootly+10 h 23 minBasetenposted +4 minZed+26 h 20 minCouchbase (this incident)posted +4 h 52 min
blamed Twilioblamed Webflowblamed BasetenAWS us-east-1posted 07:11 UTCPosted before AWS did5 vendors, 4 blamed AWSSalesforce, Descope, Ashby +2Within an hour18 vendors, 17 blamed AWSAsana, Firebolt, Monday.com+151 to 4 hours later30 vendors, 29 blamed AWSSingleStore, Loops, Buildkite+27Later45 vendors, 44 blamed AWSRudderStack, Airbyte,Unbounce +42Twilioposted +15 minBigCommerce+2 h 46 minWebflowposted +4 h 37 min, did notname AWSRootly+10 h 23 minBasetenposted +4 minZed+26 h 20 minCouchbase (this incident)posted +4 h 52 min
Couchbase is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS us-east-1<br/>posted 07:11 UTC"]:::root
  before["Posted before AWS did<br/>5 vendors, 4 blamed AWS<br/>Salesforce, Descope, Ashby +2"]:::blames
  root --> before
  h1["Within an hour<br/>18 vendors, 17 blamed AWS<br/>Asana, Firebolt, Monday.com +15"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>30 vendors, 29 blamed AWS<br/>SingleStore, Loops, Buildkite +27"]:::blames
  root --> h4
  later["Later<br/>45 vendors, 44 blamed AWS<br/>RudderStack, Airbyte, Unbounce +42"]:::blames
  root --> later
  p0["Twilio<br/>posted +15 min"]:::blames
  root --> p0
  k0["BigCommerce<br/>+2 h 46 min"]:::hop2
  p0 -->|"blamed Twilio"| k0
  p1["Webflow<br/>posted +4 h 37 min, did not name AWS"]:::timing
  root -.-> p1
  k1["Rootly<br/>+10 h 23 min"]:::hop2
  p1 -->|"blamed Webflow"| k1
  p2["Baseten<br/>posted +4 min"]:::blames
  root --> p2
  k2["Zed<br/>+26 h 20 min"]:::hop2
  p2 -->|"blamed Baseten"| k2
  me["Couchbase (this incident)<br/>posted +4 h 52 min"]:::me
  later --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: Couchbase Capella - Couchbase Capella OperationalCouchbase Capella OperationalCouchbase Capella AnalyticsCouchbase Capella - Couchbase Capella AnalyticsCouchbase Capella - Couchbase Capella ColumnarCouchbase Capella - Couchbase Capella UICouchbase Capella UICouchbase Capella App ServicesCouchbase Capella - Couchbase Capella App ServicesCouchbase Capella - Couchbase Capella Management APICouchbase Capella Management API

Timeline of updates

  1. monitoring

    We are aware of an outage that impacted a large number of AWS services in the us-east-1 region, including several for which Couchbase Capella’s management infrastructure had dependencies. This outage primarily impacted between 7 AM and 11 AM UTC on October 20th. More information on the scope of this outage can be seen on the relevant AWS status page (https://health.aws.amazon.com/health/status). No direct impact to Capella Operational clusters, App Services, or other Couchbase Capella resources that were in a healthy state prior to the outage has been identified. Scheduled activity, primarily backups and cluster hibernation, as well as Capella UI and Management API functionality, during the outage period were seen to be impacted. We are actively reviewing and working on mitigating any remaining impact and will notify affected users accordingly. It is recommended to open a support ticket for any specific questions or to highlight any unexpected behavior observed.

  2. monitoring

    AWS is continuing to address remaining issues with EC2 instance launches in the US-EAST-1 region. Due to this, some Capella operations such as Turn On and Backups might still be impacted. We are closely monitoring the situation and will provide updates as soon as more information is available.

  3. monitoring

    AWS continues to apply additional mitigations to address throttling of new EC2 instance launches. Some Capella operations may still experience intermittent delays. We are closely monitoring the situation and will provide updates as AWS shares further progress.

  4. monitoring

    AWS reports continued progress in resolving EC2 instance launch failures, with increased instance launches and improved network connectivity in the US-EAST-1 region. Capella operations are showing signs of recovery, and we continue to monitor closely.

  5. monitoring

    AWS service recovery continues to improve across all services. Throttling for new EC2 instance launches in the US-EAST-1 region is being reduced, and Capella operations are steadily returning to normal.

  6. resolved

    All services are operational.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Couchbase profileRecent Couchbase incidentsMarkdownJSON