outages.live
Live
MongoDB AtlasIncident · 2026-09-16 09:06 UTC

Support Portal Outage

ResolvedOfficial update

The MongoDB Support Portal experienced service degradation issues between approximately 2026-09-16 09:00 UTC and 2026-09-16 15:15 UTC. These platform issues have been resolved. We apologize for the service interruption and greatly appreciate your patience. Regards, The MongoDB Team

The latest update from MongoDB Atlas.

State

Resolved

Started

46 d ago

2026-09-16 09:06 UTC

Lasted

6 h 25 min

until 2026-09-16 15:31 UTC

Worst impact

Partial outage

Timeline

3 updates
09:0610:4312:1913:5515:31
Partial outageUpdate postedTimes in UTC

Investigating

6 h 25 min 100%

Updates

Times in UTC

As posted by MongoDB Atlas

Resolved2026-09-16 15:31 UTC

The MongoDB Support Portal experienced service degradation issues between approximately 2026-09-16 09:00 UTC and 2026-09-16 15:15 UTC. These platform issues have been resolved. We apologize for the service interruption and greatly appreciate your patience. Regards, The MongoDB Team

Investigating2026-09-16 09:09 UTC

We are continuing to investigate this issue.

Investigating2026-09-16 09:06 UTC

MongoDB customers are currently experiencing degraded or limited access to the MongoDB Customer Support Portal (https://support.mongodb.com/). If you require assistance with a critical MongoDB Technical Support issue and are unable to access the Customer Support Portal, please contact us using one of the numbers listed below: [These numbers have been removed. Active MongoDB customers can access them at the support portal.] We appreciate your patience.

Affected components

1
MongoDB Support Portal

MongoDB Atlas in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

14

Days with an incident

90

Median duration

5 h

This incident

1.3× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

59 days
median 5 h
90 days agoToday

Other MongoDB Atlas incidents

All incidents

MongoDB Atlas·GCP Availability Zone europe-west2-b connectivity issues

This incident has been resolved.

Resolvedresolved 12 d ago

MongoDB Atlas·Issue impacting Atlas Search availability on certain clusters

This incident has been resolved.

Resolvedresolved 23 d ago

MongoDB Atlas·Admin Admin API: Intermittent Increase in 5xx errors

This incident has been resolved.

Resolvedresolved 23 d ago

MongoDB Atlas·MongoDB Charts: Infinite login loop when creating new Charts projects

This incident has been resolved.

Resolvedresolved 30 d ago

MongoDB Atlas·Trigger processing may be delayed globally

This incident has been resolved.

Resolvedresolved 31 d ago

Follow MongoDB Atlas

Your coding agent knows when MongoDB Atlas is down, and tells you when a failure is theirs, not yours. You can also get MongoDB Atlas incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "mongodb" and tell me if MongoDB Atlas has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=mongodb
Slack
/feed subscribe https://outages.cc/feed.xml?providers=mongodb

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane