- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Couchbase Capella. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-04-27 04:03 UTC and 2026-04-27 04:03 UTC may need a replay.Subscribe to Couchbase Capella's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=couchbase works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Couchbase Capella 1
- resolved
Type: Incident Apr 26, 11:30:00 GMT+0 - Resolved - Between 12:37 PM – 11:15 PM UTC, Couchbase Capella experienced an authentication issue with our third-party email provider, causing a temporary disruption to automated system emails (e.g., registration confirmations and cluster health alerts). The service connection has been restored, and all email delivery is operating normally.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-3cfec0e2a7
Is Couchbase Capella still down?
No, this incident was resolved 2026-04-27 04:03 UTC. For Couchbase Capella's live state, see https://down.guide/couchbase.
How long did it last?
0m, from 2026-04-27 04:03 UTC to 2026-04-27 04:03 UTC, by the times Couchbase Capella posted.
What caused it?
Couchbase Capella hasn't published a root cause. If it does, it shows here.
Where does this come from?
Couchbase Capella's official status page, https://status.couchbase.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.