MongoDB Atlas incident: DataDog Integration Degraded Experience

Affected components

• MongoDB Cloud

1. resolvedFeb 26, 2026, 20:04 UTC

   The issue has been resolved

2. monitoringFeb 26, 2026, 19:51 UTC

   A fix has been implemented and we're monitoring the results.

3. investigatingFeb 26, 2026, 19:21 UTC

   We are currently experiencing degraded service with our DataDog integration for several DataDog regions. This may result in incomplete metrics, or issues with alerting for customers using the DataDog integration. We are investigating this issue.

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.

• Confluent Cloud: Some Confluent Cloud customers accessing services in GCP us-south1 region might experience elevated errors ratesMajor · Feb 25, 2026, 05:01 UTC
• Confluent Cloud: Network provisioning service in Azure East US region is degradedMajor · Feb 26, 2026, 13:59 UTC
• Confluent Cloud: All new dedicated kafka cluster provisioning and expansion in Azure westus3, southcentralus, and eastus2 are failingMajor · Feb 26, 2026, 19:56 UTC

How often does MongoDB Atlas have incidents?

MongoDB Atlas reported 9 incidents in the last 90 days, 4 of them major or critical. A typical incident lasted 5h. See MongoDB Atlas's uptime and incident history