← Back to MongoDB Atlas History
major✓ Resolved
Cluster connectivity issues in Azure westus
Status
resolved
Duration
4h 9m
Updates
4
Coverage
0 articles
INCIDENT TIMELINE
✓ ResolvedThu, Jul 23, 2026, 08:31 PM
This incident has been resolved.
identifiedThu, Jul 23, 2026, 06:54 PM
Azure is rolling out a mitigation for the ongoing networking incident affecting the West US region, and we are seeing signs of recovery. Some Atlas clusters hosted in Azure West US may continue to experience intermittent connectivity issues, including failures connecting to clusters, issues with communication between cluster nodes, nodes appearing down, and delays to cluster modifications. We are monitoring recovery closely and will provide additional updates as more information becomes available.
identifiedThu, Jul 23, 2026, 06:26 PM
We are aware of an ongoing Azure networking incident affecting the West US region. Some Atlas clusters hosted in Azure West US may experience intermittent connectivity issues, including failures connecting to clusters, issues with communication between cluster nodes, nodes appearing down, and delays to cluster modifications. Azure is investigating the issue and evaluating mitigation options. We will provide additional updates as more information becomes available.
identifiedThu, Jul 23, 2026, 04:38 PM
Azure has confirmed that there are networking issues in the westus region. Please follow the official azure status post for more detailed updates https://azure.status.microsoft/en-us/status
investigatingThu, Jul 23, 2026, 04:21 PM
We are currently investigating an issue with Azure clusters in westus region. Please refer to the azure status post here for more information https://azure.status.microsoft/en-us/status.
📊 TECHNICAL DETAILS
Internal ID
41a3c216-0229-431b-9ae4-40458d2a1476
External ID
ktcy0km7x49f
🕐 Started
Thu, Jul 23, 2026, 04:21 PM
🔄 Last Updated
Thu, Jul 23, 2026, 08:31 PM
✓ Resolved
Thu, Jul 23, 2026, 08:31 PM
MAJOR
Impact Level
4h 9m
Total Duration
4
Status Updates
Affected Components
MongoDB Cloud
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed