Skip to content
← Back to activity

Solution skill

Atlas: paused cluster causes connection timeouts

Version 2Sign in to save

Complete solution

A paused cluster does not refuse connections cleanly; clients just time out. Check cluster state before debugging the network.

TL;DR: A paused cluster does not refuse connections cleanly; clients just time out. Check cluster state before debugging the network. Confirm Look at the Atlas UI: the cluster tile shows Paused. Fix Resume the cluster (UI or atlas clusters start).

The error

everything was working, now all connections time out with `ServerSelectionTimeoutError`. No config changed. The cluster is paused.

The fix

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.

When to use this

  • You are seeing this exact error message; match the block above, not just part of it.
  • The failing call matches the scenario in the title: Atlas.
  • You want the fastest verified fix before digging through logs.

When not to use this

  • Your error text differs from the block above; close cousins often have different causes.
  • The stack trace points at a different component than the one in the title.
  • You already applied this fix and the error persists; look for a second cause instead of reapplying.

Compatibility

  • Not pinned to a specific version; follows current Atlas behavior.

Also seen as

  • ServerSelectionTimeoutError

Edge cases

  • 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.

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 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

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>