Skip to main content
MongoDB Atlas

MongoDB Atlas for Government: SSO login failures for some users

Degraded Lasted 12d 20h · started · MongoDB Atlas's page

Level
confirmed
Worst impact
Degraded
Components
MongoDB Atlas for Government

What to do

  • Check whether you use MongoDB Atlas MongoDB Atlas for Government. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 12d 20h it lasted.

    Anything that failed between 2026-03-19 00:24 UTC and 2026-03-31 21:19 UTC may need a replay.
  • Subscribe to MongoDB Atlas's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=mongodb-atlas works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from MongoDB Atlas 3

  1. identified

    Impact: Some users may be unable to log into the Atlas for Government UI using SSO. Specifically, users accessing Atlas for Government via a saved SSO login URL may receive an error, and users attempting to log in via a federated identity provider link may be unable to complete authentication. Root cause: We have identified an issue with SSO routing that is preventing some federated login flows from completing successfully. These issues started around 2026-03-18 2:30 UTC. What you might see: - A 400 error when navigating to Atlas for Government via a bookmarked or direct SSO URL. - An inability to complete login when using a federated identity provider link. Our actions: A fix is being implemented. Actively working to restore full SSO login functionality for affected users. User action: As a workaround, users can log in by entering their email address directly at https://account.mongodbgov.com and following the standard prompts. If you have time-sensitive changes that are blocked and need urgent assistance, please contact MongoDB Support. Next update: We will provide updates on this page as we progress toward resolution, or if we observe any change in impact to Atlas for Government.

    provider

  2. monitoring

    A fix has been implemented and we are monitoring the results. Users who were previously unable to log in via SSO should now be able to authenticate successfully.

    provider

  3. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-9837aeb9e1

Is MongoDB Atlas still down?

No, this incident was resolved 2026-03-31 21:19 UTC. For MongoDB Atlas's live state, see https://down.guide/mongodb-atlas.

How long did it last?

12d 20h, from 2026-03-19 00:24 UTC to 2026-03-31 21:19 UTC, by the times MongoDB Atlas posted.

What was affected?

MongoDB Atlas named MongoDB Atlas for Government.

What caused it?

MongoDB Atlas hasn't published a root cause. If it does, it shows here.

Where does this come from?

MongoDB Atlas's official status page, https://status.mongodb.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.