Space for ads
Checked every 5 minutes · How we measure this
As of 17:30 EDT on 23 Oct 2026, mongodb.com responded to our check in 2,478 ms, with 100.00% availability over the last 24 hours.
Checked every 5 minutes · last checked 7 minutes ago
The line is response time measured from our probe to mongodb.com, which rises when the service slows down. Shaded red marks intervals where checks actually failed. It excludes your own connection and browser rendering.
Reported by MongoDB Atlas on its own status page. Verify on their status page.
This includes MongoDB Cloud Manager and MongoDB Atlas
The MongoDB Support Portal provides access to MongoDB Technical Services Engineers who can help subscribers with their issues with MongoDB or MongoDB Cloud.
This includes Atlas Triggers, Device Sync, and the Atlas Data API
This includes Atlas Data Federation, Atlas Online Archive, Atlas Data Lake, and Atlas SQL
Advanced full text and vector search for your MongoDB Atlas data
MongoDB Charts is MongoDB's native visualization tool. It is tightly integrated into MongoDB Atlas.
Atlas Stream Processing enables processing streams of complex data using the same data model and Query API used in Atlas databases.
A FedRAMP Ready environment for MongoDB Atlas
VoyageAI's embedding and reranking models, including API access.
0 problem reports
GCP Availability Zone europe-west2-b connectivity issues
We are seeing signs of Availability Zone connectivity improving and are continuing to monitor.
Confirmed on the vendor status page
MongoDB Atlas degraded performance
DownBits detected degraded performance on MongoDB Atlas between 9 Oct 2026, 22:10 – 23:55 IST, lasting ongoing. Detected across 21 consecutive automated checks of mongodb.com.
Detected by DownBits probe
Issue impacting Atlas Search availability on certain clusters
A fix has been deployed and we are monitoring.
Confirmed on the vendor status page
Admin Admin API: Intermittent Increase in 5xx errors
We have deployed a mitigation for the elevated HTTP 500 errors affecting the MongoDB Atlas Admin API. We are seeing signs of recovery and are monitoring the service to confirm the issue does not recur before resolving this incident.
Confirmed on the vendor status page
MongoDB Atlas degraded performance
DownBits detected degraded performance on MongoDB Atlas between 2 Oct 2026, 05:40 – 10:40 IST, lasting ongoing. Detected across 60 consecutive automated checks of mongodb.com.
Detected by DownBits probe
MongoDB Charts: Infinite login loop when creating new Charts projects
Since approximately 23:30 UTC on 2026-10-01, users creating new Charts projects by clicking on the "Visualization" tab will repeatedly be prompted to login and will not be able to view the Charts interface. While these Charts projects will be created, we cannot guarantee the timing at this moment. Existing Charts projects are not affected.
Confirmed on the vendor status page
MongoDB Atlas degraded performance
DownBits detected degraded performance on MongoDB Atlas between 1 Oct 2026, 21:20 – 01:35 IST, lasting ongoing. Detected across 51 consecutive automated checks of mongodb.com.
Detected by DownBits probe
Trigger processing may be delayed globally
Atlas Triggers are firing again, and trigger processing is operational. We are monitoring the service and verifying the status of triggers affected during the incident, including any delayed events. We will provide a further update once verification is complete.
Confirmed on the vendor status page
Delays in Atlas cluster management operations
The team has implemented a fix and latency of Atlas Cluster management operations are returning to normal. Clusters that incorrectly appeared as degraded in the Atlas UI are also beginning to correctly update their status.
Confirmed on the vendor status page
MongoDB Atlas outage
DownBits detected an outage on MongoDB Atlas between 16 Sep 2026, 14:45 – 21:10 IST, lasting ongoing. Detected across 77 consecutive automated checks of mongodb.com.
Detected by DownBits probe
Support Portal Outage
We are continuing to investigate this issue.
Confirmed on the vendor status page
Atlas is experiencing issues with issuing certificates from Lets Encrypt
Atlas is seeing elevated errors rates of certificate issuance due to a Let's Encrypt outage (https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/6aa35c1d892d7304f2747e01). Free and flex tier cluster provisioning may be delayed.
Confirmed on the vendor status page
MongoDB Atlas degraded performance
DownBits detected degraded performance on MongoDB Atlas between 8 Sep 2026, 21:48 – 09:30 IST, lasting ongoing. Detected across 716 consecutive automated checks of mongodb.com.
Detected by DownBits probe
Impaired Cluster operations in AWS me-central-1 and AWS me-south-1
We are continuing to monitor for any further issues.
Confirmed on the vendor status page
MongoDB Atlas is responding normally. Our last automated check of mongodb.com completed 7 minutes ago and succeeded in 2,478 ms. Over the past 24 hours the service answered 100.00% of our checks.
Measured from our automated checks, MongoDB Atlas has been available 100.00% over 24 hours, 100.00% over 7 days, 100.00% over 30 days. We recorded 9 incidents in the last 30 days.
MongoDB Atlas has averaged 1,798 ms across our successful checks in the past 24 hours, which is slower than ideal and may feel sluggish on a weak connection. Response time is measured from our probe to mongodb.com and does not include rendering time in your browser.
The most recent incident DownBits recorded for MongoDB Atlas began on 9 October 2026 at 22:10 IST and lasted 1 hr 45 min. It was logged as degraded performance. Detected by DownBits probe.
Our probe is reaching mongodb.com normally right now, so the problem is more likely to be local to you than a full outage. Use the report button on this page to add your own signal — when several people report the same problem within a short window, it appears on the chart above.
A working marketing site does not mean a working API. Call the API host directly — curl -s -o /dev/null -w "%{http_code}" https://mongodb.com/ — and check the vendor status page linked above for component-level detail, since one component can fail while the rest stay green.
HTTP 429 and 529 mean you are being throttled, not that the service is down. Inspect the response headers for a retry-after value and back off exponentially rather than retrying immediately.
A 401 or 403 is an authentication problem on your side. Rotated keys, an expired billing method, or a revoked token all present as sudden total failure.
Open any other site. If nothing loads, the issue is your network rather than MongoDB Atlas. On Windows run ping mongodb.com and nslookup mongodb.com in Command Prompt; on macOS or Linux use Terminal. A DNS failure and a server failure look identical in a browser but are very different problems.
Load mongodb.com in a private or incognito window. If it works there, clear cookies and site data for mongodb.com in your normal browser rather than clearing everything.
Switch from Wi-Fi to mobile data, or vice versa. Regional ISP routing problems are common and often affect one carrier while others are unaffected.
We link the vendor status page so you can check our reading against theirs.
No comments received
