major
monitoring
since
Impaired Cluster operations in AWS me-central-1 and AWS me-south-1
We are continuing to monitor for any further issues.
Latest update 63 days ago
Is MongoDB Atlas Down?
Partially — MongoDB Atlas is degraded
- MongoDB Atlas's status page
- Open incident · major incident (“Impaired Cluster operations in AWS me-central-1 and AWS me-south-1”)
- FlareWarden checks
- Website reachable · 8 of 8 regions · 541 ms
Right now
The verdict is the worse of these two. How we decide
MongoDB Atlas's status page
status.mongodb.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| MongoDB Cloud | Operational |
| MongoDB Support Portal | Operational |
| MongoDB Atlas App Services and Device Sync | Operational |
| MongoDB Atlas Data Federation and Online Archive | Operational |
| MongoDB Atlas Search | Operational |
| MongoDB Charts | Operational |
| MongoDB Atlas Stream Processing | Operational |
| MongoDB Atlas for Government | Operational |
| VoyageAI Embedding and Reranking Models | Operational |
| MongoDB Atlas Agent Engine | Operational |
FlareWarden checks
mongodb.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 541 ms
- Checked
By region
- Amsterdam reachable, 350 ms
- Dallas reachable, 130 ms
- Newark reachable, 313 ms
- Paris reachable, 614 ms
- San Jose reachable, 785 ms
- Stockholm reachable, 359 ms
- Sydney reachable, 1550 ms
- Toronto reachable, 233 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 92 ms | 2 ms | 4 ms | 113 ms |
| Dallas | 83 ms | 0 ms | 4 ms | 122 ms |
| Newark | 227 ms | 19 ms | 20 ms | 295 ms |
| Paris | 72 ms | 1 ms | 4 ms | 277 ms |
| San Jose | 185 ms | 3 ms | 5 ms | 522 ms |
| Stockholm | 67 ms | 1 ms | 3 ms | 98 ms |
| Sydney | 203 ms | 1 ms | 5 ms | 677 ms |
| Toronto | 123 ms | 19 ms | 11 ms | 191 ms |
We check that mongodb.com loads, not every feature behind it.
Test it yourself
History
Incidents MongoDB Atlas reported
Since Oct 22, 15 days · from status.mongodb.com
- Incidents
- 1
- Major or critical
- 1
- Median to resolve
- —
- Ongoing
MongoDB Atlas website availability
Measured by FlareWarden · mongodb.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 607ms
Last 30 days
91-day clean streakOct 7
Today
No downtime
Partial
Downtime
Not measurable
No data
Measured by FlareWarden's own checks of mongodb.com from multiple regions every 6 hours. MongoDB Atlas's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What MongoDB Atlas does
MongoDB Atlas is the managed MongoDB service, running clusters on AWS, Google Cloud and Azure. Applications treat it as their primary datastore, so an Atlas incident is rarely a degraded feature: it is an application that cannot read or write anything, returning errors on every request that touches the database.
What an outage looks like
Applications throw connection timeouts or server selection errors as drivers fail to reach a replica set member. Queries that do complete run slowly while a failover is in progress. Atlas Search queries can fail while ordinary reads and writes succeed, because Search is a separate component. The Atlas web console may load normally while clusters stay unreachable.
What to do about it
Check status.mongodb.com, which reports Atlas Search, Data Federation, Charts, Stream Processing and App Services separately from MongoDB Cloud itself, so identify which component your failure actually touches. Drivers retry many operations on their own, so avoid restarting application instances in a loop. Cluster incidents are often confined to one cloud region rather than the whole service.
Is it down for everyone, or just you?
If this page says MongoDB Atlas is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
MongoDB Atlas outage FAQ
Is Atlas down or is my connection string wrong?
A server selection timeout looks identical either way. Check status.mongodb.com first, then confirm whether the failure is new: a connection string that never worked points at configuration, IP access lists or credentials, while one that worked ten minutes ago points at the service. Test from a second network to rule out an access list change on your side.
Will I lose writes during a MongoDB Atlas outage?
Writes acknowledged by the cluster are durable and survive a failover, since Atlas replicates across nodes. Writes in flight when connectivity broke may not have landed, and your driver will surface those as errors rather than silently discarding them. Retryable writes, enabled by default in current drivers, replay many of these automatically once a new primary is elected.
Why is Atlas Search failing when my queries work?
Atlas Search runs as its own service on separate infrastructure and is reported as its own status component. A Search incident breaks text search and aggregation stages that use it, while ordinary find and update operations against the same collections continue normally. If only your search feature is broken, check that component before investigating the cluster.
Does an Atlas outage affect every cloud region?
Rarely. Atlas clusters run in specific regions on AWS, Google Cloud or Azure, and most incidents trace back to a problem in one provider's region rather than to Atlas globally. The status page and incident history name the affected regions. A cluster deployed across regions may lose some nodes and keep serving through the rest.
Should I restart my application during an Atlas incident?
Usually not. MongoDB drivers hold a connection pool and reconnect on their own as nodes become reachable, so restarting mostly discards that state and adds a reconnection storm on top of a recovering cluster. Restarting is worth it only when the application has clearly wedged and is no longer retrying after the cluster is healthy.
How we measure this
- We request MongoDB Atlas's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where MongoDB Atlas publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of MongoDB Atlas itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when MongoDB Atlas goes down
We check MongoDB Atlas every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free MonitoringFree plan available
No credit card required