MongoDB Atlas status · Data & Backend · checked (3s ago)
Also searched as MongoDB, Atlas.
Operational
No — MongoDB Atlas is not down. All MongoDB Atlas systems are reported operational.
According to MongoDB Atlas's official status page, MongoDB Atlas was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, MongoDB Atlas's feed reported no outage in 99.10% of our checks.
No outage reported (30d)
99.10%
Share of our checks where MongoDB Atlas's feed reported no outage. Degraded counts as no-outage. Not an SLA.
Response time
1.24 s
How long the last status check took
Reported by
Operational
All Systems Operational
Is MongoDB Atlas down for you right now?
Everything above is read from MongoDB Atlas's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported MongoDB Atlas in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
What MongoDB Atlas is
MongoDB Atlas is the managed cloud version of MongoDB, run across AWS, Google Cloud and Azure, with Atlas Search, Charts, Data Federation and serverless instances alongside the core database.
What MongoDB Atlas's status feed covers
Atlas's status page reports by cloud provider and region, because Atlas clusters run on top of those providers — an underlying AWS regional incident surfaces here as an Atlas one. It reports on the Atlas control plane and regional infrastructure, not on individual clusters, so your specific cluster's health is a separate question.
One bar per day. Each shows the share of that day's checks where MongoDB Atlas's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days MongoDB Atlas was down.
2026-08-2530 of 30 days recorded · lowest day 73.26%Today
No outage reported (99%+)
95–99%
80–95%
Under 80%
No data
Other services reporting problems right now
9 other services isuptime tracks were also reporting a problem as of the same check, 3s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of MongoDB Atlas's status endpoint.
MongoDB Atlas outage history
MongoDB Atlas has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what MongoDB Atlas posted itself — not every problem users hit.
No — MongoDB Atlas is not down. All MongoDB Atlas systems are reported operational. Checked (3s ago).
What is MongoDB Atlas's status right now?
MongoDB Atlas is reporting “All Systems Operational” on its official status page — Operational — as of . That status feed answered our last check in 1.24 s. isuptime reads this from MongoDB Atlas's own published feed and does not test MongoDB Atlas independently.
When did MongoDB Atlas last go down?
The most recent incident MongoDB Atlas published was “Support Portal Outage”, opened Sep 16, 09:06 AM UTC (7d ago) and marked resolved Sep 16, 03:31 PM UTC. That is the latest entry in MongoDB Atlas's own incident feed, not every problem users experienced.
What is MongoDB Atlas's uptime?
isuptime does not measure MongoDB Atlas's uptime directly — it reads MongoDB Atlas's own published status feed. Over the last 30 days, MongoDB Atlas's own status feed reported no outage in 99.10% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
Is it just me, or is MongoDB Atlas down for everyone?
MongoDB Atlas reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.
MongoDB Atlas says operational but it is not working for me
The most common cause of a healthy-looking Atlas and a broken application is the IP access list — a new deploy from a new address is refused, which the driver reports as a connection timeout. Check that first. After that: connection limits on the M0/M2/M5 tiers, an expired database user password, and clusters paused for inactivity.
