MongoDB Atlas incident: Atlas Data Federation and Online Archive cloud-provider IAM authentication error

Affected components

• MongoDB Atlas Data Federation and Online Archive

1. resolvedJul 9, 2026, 11:06 UTC

   This incident has been resolved.

2. monitoringJul 9, 2026, 11:01 UTC

   A fix has been implemented and we are monitoring the results.

3. identifiedJul 9, 2026, 10:57 UTC

   We have identified that the issue is caused by a recent configuration change to IAM authentication and are working on a fix.

4. investigatingJul 9, 2026, 10:23 UTC

   Users of Atlas Data Federation and Online Archive using cloud-provider IAM authentication may see pipelines fail with an error when querying backing Atlas clusters. Other authentication methods are unaffected. As a temporary workaround, users can use SCRAM authentication.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in MongoDB Atlas's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Mux: Live Stream DisruptionsMajor · Jul 8, 2026, 17:29 UTC
• Pinecone: [Serverless][Azure][eastus2] 5xx errors on some requests for some indexesMajor · Jul 9, 2026, 09:50 UTC
• Calendly: Degraded performance on Calendly.comMinor · Jul 8, 2026, 17:25 UTC

How often does MongoDB Atlas have incidents?

MongoDB Atlas reported 15 incidents in the last 90 days, 7 of them major or critical. A typical incident lasted 2h 31m. See MongoDB Atlas's uptime and incident history