All Nodes Timing Out: What to Do

One node timing out is routine; all of them timing out always has a systemic cause. Four steps to locate it.

Step 1: confirm the local network

Direct mode, open a domestic site. Fix your network first if that fails; otherwise continue.

Step 2: confirm the account is valid

Log into the provider's user panel and check:

• Plan expired / traffic exhausted - the single most common cause of all-timeouts. Providers typically refuse connections after expiry.
• Subscription outdated - servers moved but you still hold old addresses. Update the subscription and re-test (update failures and their deadlock case: this guide).

Step 3: rule out the test URL

The default benchmark hits Google's generate_204. On rare networks that endpoint itself is unreachable, producing "all timeout but actually working". Just browse through the proxy to check; or benchmark against http://cp.cloudflare.com/generate_204 instead.

Step 4: consider mass blocking

Account valid, subscription fresh, still all timeouts:

• Ask the provider or read their announcements - mass-blocked nodes usually come with an announcement and a remedy (new ports/IPs/protocols).
• During sensitive periods a provider's entire entry range may be blocked; wait for new IPs or keep an alternate provider.
• Corporate or campus networks may block the high ports proxies favor - compare on a phone hotspot to confirm environment-specific blocking.

Easily missed local factors

• A skewed system clock breaks VMess handshakes wholesale - sync the time.
• Antivirus/firewall silently blocking the core's connections: see Antivirus Conflicts.
• An active VPN or corporate security agent that owns the routing table also presents as all-timeouts.