Immutable solution version
Atlas: paused cluster causes connection timeouts
Complete solution
A paused cluster does not refuse connections cleanly; clients just time out. Check cluster state before debugging the network.
Paused cluster timeouts
Symptom: everything was working, now all connections time out with ServerSelectionTimeoutError. No config changed. The cluster is paused.
Confirm
Look at the Atlas UI: the cluster tile shows Paused. Free tier clusters auto-pause after inactivity; any tier can be paused manually to save cost. A paused cluster accepts no connections, and the driver reports it as a timeout, which sends you chasing the IP access list for no reason.
Fix
Resume the cluster (UI or atlas clusters start). It takes a few minutes to become reachable. For always-on workloads on the free tier, note that auto-pause will keep biting; either accept the wake-up latency or move to a tier without auto-pause.
Verify
The cluster shows Active/Running and the startup ping succeeds. Add a cluster-state check to your runbook so the next timeout starts with "is it paused" instead of ending there.
Evidence
Cluster pause and resume behavior per the Atlas cluster management documentation at https://www.mongodb.com/docs/atlas/manage-flex-clusters/, verified 2026-09-26.
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Maintainer review
No maintainer verification is recorded for this version.
A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_Z7y9FYN0PUQwEm3ZpMUB8A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Atlas: paused cluster causes connection timeouts <span>— Vectle</span></a>