Atlas error: ServerSelectionTimeoutError, no suitable servers

TL;DR: The driver found the cluster topology but could not establish a working connection to any node. On Atlas this is the IP access list nine times out of ten. Check the client's egress IP is listed (it is the egress IP, not the IP you think, for CI, VPNs, and containers), then check for a paused cluster, DNS, and local firewall. Then retry.

The error, verbatim:

ServerSelectionTimeoutError: [host]:[port] timed out
No suitable servers found

Steps:

1. IP access list: Security, Network Access in Atlas. Is the client's egress IP listed? Success: the egress IP is on the list (add it with an expiry for temporary access).
2. Cluster state: is the cluster paused? A paused cluster refuses connections with timeouts, not a clear error. Success: the cluster is running.
3. DNS: can the machine resolve the SRV record? nslookup -type=SRV _mongodb._tcp.[cluster-host]. If not, use the standard connection string form. Success: SRV resolves or the standard string works.
4. Local firewall or proxy blocking outbound 27017. Success: the port is reachable.
5. Retry with a startup ping from the failing network. Success: the ping succeeds.

When to use: ServerSelectionTimeoutError or no suitable servers against MongoDB Atlas.

When not to use: authentication failures (wrong error), malformed connection strings, or self-hosted replica sets (different failure modes).

Compatibility: MongoDB drivers (any language), MongoDB Atlas.

Variants:

• mongodb atlas connection timeout
• no suitable servers found atlas
• serverselectiontimeouterror atlas fix

Root cause: the driver knows where the cluster is but cannot open a socket to any node. Atlas's network gate is the access list, and the client IP is almost always the surprise: CI runners, VPNs, and containers egress from IPs nobody configured.

Edge cases:

• It works from your laptop but not the deploy target: the difference is the network path, and the IP access list is still suspect number one.
• A paused cluster looks exactly like a network failure. Check state before debugging DNS.
• For temporary access, add the IP with an expiry so the list does not accumulate stale entries.

Server selection failure causes and the troubleshooting order (IP access list first, then cluster state, DNS, firewall) per https://www.mongodb.com/docs/atlas/troubleshoot-connection/ and https://www.mongodb.com/docs/atlas/security/ip-access-list/, verified 2026-09-26.