Space for ads
Checked every 5 minutes · How we measure this
As of 14:35 EDT on 8 Sep 2026, MongoDB Atlas reports degraded or failing components on its own status page. Our probe still reached mongodb.com in 1,455 ms, with 100.00% availability over the last 24 hours.
Availability is the share of our automated checks that succeeded in each interval. Response time is measured from our probe to mongodb.com and 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
MongoDB Atlas degraded performance
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 reporting degraded or failing components on its own status page. Our probe is still reaching mongodb.com normally — 24-hour availability from our checks is 100.00% — so the front door is up while something behind it is not. The component list on this page shows which parts MongoDB Atlas says are affected. Last checked 6 minutes ago.
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 2 incidents in the last 30 days.
MongoDB Atlas has averaged 1,585 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.
Our probe is also failing to reach mongodb.com normally, so this is not just you. 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
