MongoDB Atlas: MongoDB Cloud and Support: Cluster connectivity issues in some regions. Login buttons greyed out.

MinorStatus: resolvedStarted 2021-12-15 15:28 UTCResolved 2021-12-15 16:38 UTC (1.2 h)1 updatestatus.mongodb.com

Part of an outage event

AWS outage, Dec 15, 2021 · 49 vendors, 50 incidents

MongoDB Atlas’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted −4 min vs the first vendor naming AWS)

Swipe sideways to see the whole diagram.

MongoDB Atlas is outlined in red. Groups show up to a few vendors each; the event page lists every incident.

Mermaid source

flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>15 vendors, 11 blamed AWS<br/>Daily, Gusto, Logz.io +12"]:::blames
  root --> h1
  me["MongoDB Atlas (this incident)<br/>posted −4 min"]:::me
  root -.->|"same window"| 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.

Timeline of updates

resolved2021-12-15 16:38 UTC
This incident has been resolved.

From MongoDB Atlas’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

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

MongoDB Atlas profile Recent MongoDB Atlas incidents Markdown JSON