An Azure NoSQL database service for app development.
Azure Cosmos DB (MongoDB API): Connection issues and timeouts since November 15, 2026 — Cluster appears healthy in portal
Problem description
I am experiencing connection timeouts and inability to perform management actions on my Azure Cosmos DB (MongoDB API) cluster since November 15, 2026, 05:15. Client applications, including my .NET app and mongosh, fail with 'MongoServerSelectionError: Server selection timed out after 30000 ms.' The cluster still shows as 'Ready' in the portal, and I cannot update firewall rules or perform other management tasks. The issue has persisted for over 24 hours.
Environment
Azure Cosmos DB for MongoDB (vCore), client application with .NET, client region: Germany West Central, access via MongoDB SRV endpoint.
What I've already tried
At case intake, I documented the start time, observed duration, client region, SDK used, and error messages. I reviewed the cluster's status in the Azure portal, noting it remained 'Ready' despite connection failures. I attempted to modify firewall rules, but that also failed. I checked general self-help guidance for connection issues, such as DNS resolution, port accessibility, and resource load, but did not find conclusive results. No further diagnostic data, such as exception counts or activity logs, are available.
Current status
The cluster continues to appear as 'Ready' in the portal, but connection attempts fail with timeout errors across multiple clients. Management actions are unresponsive. I seek assistance in diagnosing whether this is a cluster-side issue, network problem, or configuration error, and guidance on steps to resolve or escalate further.