Outages and root causes.
Two years of public outages, and what each company said caused them. Every entry links to the company's own write-up; nothing here is our speculation.
Status pages re-read 3 min ago
Incidents listed
By month, last two years · MongoDB Atlas
Peak 6 · March 2026
- Total: 19
- December 2024: 0
- January 2025: 0
- February 2025: 0
- March 2025: 0
- April 2025: 0
- May 2025: 0
- June 2025: 0
- July 2025: 0
- August 2025: 0
- September 2025: 0
- October 2025: 0
- November 2025: 0
- December 2025: 0
- January 2026: 0
- February 2026: 1
- March 2026: 6
- April 2026: 2
- May 2026: 1
- June 2026: 1
- July 2026: 2
- August 2026: 2
- September 2026: 2
- October 2026: 2
- November 2026: 0
- Incidents listed
- 19
- Last two years
- Official write-ups
- 0
- Linked from the incident
- Major outages
- 0
- As graded by each company
- Services
- 1
- With at least one entry
From the status pages
MongoDB Atlas · Issue impacting Atlas Search availability on certain clusters
Partial outage · Oct 9, 2026 · 1 h 48 min
MongoDB Atlas · Trigger processing may be delayed globally
Partial outage · Oct 1, 2026 · 5 h 13 min
MongoDB Atlas · Support Portal Outage
Partial outage · Sep 16, 2026 · 6 h 25 min
MongoDB Atlas · Impaired Cluster operations in AWS me-central-1 and AWS me-south-1
Partial outage · Sep 3, 2026 · Ongoing
MongoDB Atlas · GCP capacity constraints affecting Atlas deployments
Partial outage · Aug 5, 2026 · 6 h 57 min
MongoDB Atlas · Elevated errors on VoyageAI APIs
Partial outage · Aug 3, 2026 · 2 h 31 min
MongoDB Atlas · VoyageAI elevated errors
Partial outage · Jul 27, 2026 · 11 min
MongoDB Atlas · Cluster connectivity issues in Azure westus
Partial outage · Jul 23, 2026 · 4 h 7 min
MongoDB Atlas · Investigating connection issues to ADFA in GCP
Partial outage · Jun 2, 2026 · 1 h 11 min
MongoDB Atlas · AWS Cluster DNS Changes Degraded Performance
Partial outage · May 7, 2026 · 6 h 58 min
MongoDB Atlas · Increase in Billing for Backup Usage
Partial outage · Apr 27, 2026 · 3 h 33 min
MongoDB Atlas · MongoDB Atlas BI Connector: Connections and queries fail
Partial outage · Apr 17, 2026 · 3 d 20 h
MongoDB Atlas · Intermittent 503 Errors on Atlas Admin API and Automation Tooling
Partial outage · Mar 25, 2026 · 1 d 15 h
MongoDB Atlas · Issue querying Azure blob storage containers in Atlas Data Federation
Partial outage · Mar 19, 2026 · 1 h 9 min
MongoDB Atlas · MongoDB Atlas: Clusters page failing to load
Partial outage · Mar 19, 2026 · 45 min
MongoDB Atlas · Atlas Clusters Snapshot Failures
Partial outage · Mar 10, 2026 · 3 h 11 min
MongoDB Atlas · MongoDB Atlas: Email notifications may be failing
Partial outage · Mar 2, 2026 · 39 min
MongoDB Atlas · Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)
Partial outage · Mar 1, 2026 · 185 d 21 h
MongoDB Atlas · MongoDB App Services: Connectivity issues
Partial outage · Feb 28, 2026 · 1 d 7 h
Who publishes root causes
Write-ups posted on status pages, last two years
Public information only
Everything on this page was already published by the companies themselves or by public bodies. statuswall gathers it in one place, links every item to its original, and adds nothing from private or leaked sources.
Sources
- Official status pages: incident titles, severity, times and the link to each published root-cause analysis, exactly as each company posted them
- Company engineering blogs and incident reports: the basis for the notable-outage summaries, each linked from its card
How fresh it is
- Incidents and RCA links: re-read from every status page about once an hour; last run 3 min ago
- Notable-outage summaries: written by hand and last checked against their sources on Nov 10, 2026
Titles, severity and times are as published on each company's status page. "Published RCA" means the company posted a postmortem on that incident's official page; we link to it and do not reproduce it. Many companies publish root causes on a blog instead, or not at all, so the absence of a link is not evidence that no analysis exists. Severity grading differs between companies and is not comparable across them. This is not a complete record of every outage.
statuswall is independent and is not affiliated with, sponsored by or endorsed by any company named here. Company and product names are used only to identify whose public information is being referred to. The information is provided as is, for general reference, with no guarantee that it is complete, current or free of error; it is not security, legal or purchasing advice. Where this page and an official source differ, the official source is right.