Server Connection Timeout

Connection timeouts when joining an Unturned™ server can have several causes. This article walks through the most common ones and how to diagnose each. A timeout is a specific category of connection failure with a specific meaning, and distinguishing a true timeout from other connection errors is the first step in resolution.

A timeout means that the client tried to communicate with the server, the server did not respond within the time limit the client was willing to wait, and the client gave up. The client does not know whether the server received the request, started processing it, was overwhelmed, or simply does not exist; it only knows that no response came back in time. This distinction matters because the resolution depends on which of those underlying states is actually true.

What this article covers

• What a connection timeout actually means in network terms.
• How to distinguish a true timeout from "connection refused," "host unreachable," and other connection failures.
• The principal causes of timeouts: server overload, network path issues, firewall blocks, port forwarding gaps, VPN interference, ISP routing, EAC handshake delays.
• A diagnostic flowchart that walks through the cohort-recommended order of investigation.
• PowerShell commands for testing connectivity at each layer (ping, Test-NetConnection, tracert).
• The Unturned port reference, including default ports and how to identify custom ports.
• How Steam's download cache and matchmaking state can produce false-timeout symptoms.
• When a timeout indicates an overloaded server vs an unreachable server vs a misconfigured client.

Prerequisites

• Unturned installed via the official Steam client. The game's Steam store page is at the Unturned product page.
• The server's IP and port. Many timeouts are misdiagnosed because the player is using the wrong port; confirm the published port before troubleshooting.
• A working internet connection.
• Administrator access on the local machine for firewall and network adapter diagnostics.

Background: what "timeout" means

A network timeout is a specific failure mode. The client sends a packet to the server (or attempts to open a TCP connection), waits for a response for some configured maximum time, and when no response arrives within that time, the client declares a timeout and gives up.

The timeout duration varies by protocol and by application:

• The Unturned game client's connection timeout is approximately 30 seconds for the initial handshake, with internal retries.
• Steam's matchmaking handshake times out at approximately 20 seconds.
• TCP's default connect timeout is approximately 21 seconds on Windows.
• ICMP (ping) has a much shorter timeout, typically 1-4 seconds per echo request.

When the player sees "Connection timed out" in Unturned, it means the game client gave up waiting for the server to respond at some stage of the connection handshake. The cause is not knowable from the error message alone; the diagnostic in this article identifies it.

Timeout versus other connection failures

The table below distinguishes timeouts from other connection failures.

Error class	What the client observed	Most common cause
Connection timed out	No response within the wait window	Network path issue or server overload
Connection refused	Server actively replied "go away"	Server full, password required, or whitelist
Host unreachable	Network layer says the host has no route	Server's host is down or no network path exists
DNS resolution failed	Server's hostname could not be resolved to an IP	DNS misconfiguration or invalid hostname
Protocol mismatch	Server answered but with wrong protocol	Wrong port or wrong game version
EAC handshake failed	EAC subsystem rejected the connection	EAC outage or version mismatch

A timeout is fundamentally a "no answer" error. The other errors are "answer was not what I wanted" errors. Distinguishing them tells you whether to investigate the network path or the server itself.

The flowchart above models the diagnostic decision tree. Each branch corresponds to a different timeout cause; each terminal node points at a different resolution.

The timeout categories

Timeouts in Unturned fall into four broad categories. The diagnostic steps later in this article identify which category any specific timeout belongs to.

Category	What is happening	Indicator
Local-side	Local firewall, VPN, or network configuration is blocking the connection	All servers timeout, not just one
Network-path	The path between client and server is broken or saturated	Tracert fails partway, ping has high loss
Server-overload	Server is up but overwhelmed and not responding in time	Server has many players and high tick activity
Server-rejection-disguised	Server is rejecting the connection silently rather than returning an error	Test-NetConnection succeeds but join fails

The four categories require different resolution approaches. The cohort-validated diagnostic order is: rule out local-side first, then network-path, then test the server.

Diagnostic steps

Step 1: Confirm the timeout is reproducible

Before any deep diagnostic, confirm the timeout is a stable symptom and not a one-off network glitch.

1. Wait 30 seconds.
2. Retry the connection.
3. If the timeout repeats, it is reproducible and the diagnostic steps below apply.
4. If the connection succeeds, the timeout was transient. Watch for recurrence before further investigation.

Transient timeouts are common during periods of brief network congestion (5-10 seconds of high packet loss). Most resolve on their own and do not require investigation.

Step 2: Test other Unturned servers

If multiple Unturned servers all time out, the problem is local-side or platform-side rather than at any specific server.

1. Open the in-game server browser.
2. Try to join a different server (any other server, ideally one with a different operator and a different host region).
3. If the second server connects successfully, the original server is the problem.
4. If the second server also times out, the problem is local-side or platform-side.

The two-server test is the cohort's recommended first diagnostic because it separates server-specific issues from client-specific issues with a single test.

Step 3: Verify the server's IP and port

Many timeouts are caused by trying to connect to the wrong port. The Unturned default game port is 27016 (UDP), the default query port is 27015 (TCP), and the default RCON port is 27017 (TCP). Operators frequently change these.

1. Locate the operator's published server IP and port.
2. Confirm the port is the game port (not the query port).
3. If the operator publishes only one number, it is usually the query port; the game port is typically the query port plus 1.
4. Re-attempt the connection with the verified port.

Common mistake

Connecting on the query port (27015 by default) instead of the game port (27016 by default). The query port is for Steam's master server to query the server's status; it is not for game traffic. Attempting to join on the query port produces a timeout because the server does not handle game traffic on that port.

Step 4: Ping the server's host

Ping is the simplest reachability test.

1. Open PowerShell.
2. Run ping <server-ip>.
3. Observe the results.

If the server's host replies to ping, the host is online and the network path is at least minimally functional. If ping fails entirely, the host may be down or the host may be filtering ICMP.

A ping that succeeds with low latency (under 100 ms typical for a server in your region) indicates the network path is healthy. A ping with high latency (over 500 ms) or significant packet loss indicates network-path issues that will cause timeouts.

Step 5: Test the server's port with Test-NetConnection

Test-NetConnection confirms whether the server's port is open and reachable.

1. Open PowerShell.
2. Run Test-NetConnection -ComputerName <server-ip> -Port 27015 (the query port).
3. Observe the TcpTestSucceeded result.

If TcpTestSucceeded is True, the server's query interface is reachable. If False, the port is closed or blocked.

The query port is the most reliable port to test because it uses TCP, which Test-NetConnection can definitively confirm. The game port uses UDP, which is not as easily testable.

If the query port test succeeds but the join still times out, the server is reachable but is either rejecting the connection (full, whitelisted, etc.) or is overloaded.

Step 6: Trace the route to the server

tracert shows the network path between the client and the server.

1. Open PowerShell.
2. Run tracert <server-ip>.
3. Wait for the trace to complete.
4. Look at where the trace fails (if it fails).

A trace that completes to the destination indicates the network path is fine. A trace that fails at an intermediate hop indicates a routing problem; the specific hop where the trace fails identifies where in the network the problem is.

Common patterns:

• Trace fails at the first or second hop: your home internet connection has an issue.
• Trace fails 5-10 hops in: a routing problem in the public internet, often transient.
• Trace fails at the last hop before the destination: the server's network is filtering or the host is down.
• Trace completes but ping/Test-NetConnection fail: the host is filtering at the application layer.

Step 7: Check the local firewall

Windows Defender Firewall or third-party firewalls can block Unturned's outgoing connections.

1. Open Windows Security.
2. Select "Firewall & network protection."
3. Click "Allow an app through firewall."
4. Confirm that "Unturned" is listed and that both Private and Public checkboxes are enabled.
5. If Unturned is not listed, click "Change settings" then "Allow another app" and add Unturned.

The first time Unturned attempts to connect to the internet, Windows usually presents a firewall prompt asking whether to allow the connection. If the prompt was dismissed without granting access, the firewall blocks all subsequent connections, producing a timeout.

Step 8: Disable any VPN

VPNs route traffic through a different network, which can cause timeouts in several ways:

• The VPN provider blocks the destination IP or port.
• The VPN's exit node is geographically far from the server, adding latency that exceeds Unturned's timeout.
• The VPN provider blocks UDP traffic, which Unturned requires for game protocol.
• The server operator has blocked known VPN exit IPs at the host firewall.

1. Disconnect any active VPN.
2. Re-attempt the connection.
3. If the connection succeeds without the VPN, the VPN was the cause.

If the VPN is required for other reasons, the workarounds are: try a different VPN exit region, switch to a VPN provider that does not block UDP, or use the VPN only for non-gaming traffic.

Step 9: Clear Steam's download cache

Steam maintains an internal download cache that occasionally becomes corrupted. The corrupted state can cause matchmaking and connection issues that manifest as timeouts.

1. Open Steam.
2. Open Settings.
3. Select "Downloads."
4. Click "Clear Download Cache."
5. Confirm. Steam will sign you out.
6. Sign back in.
7. Re-attempt the connection.

Clearing the download cache is a low-risk operation; it forces Steam to re-fetch its state from the server. The most common situations where clearing helps are after a Steam update or after extended Steam uptime.

Step 10: Verify Unturned's game files

Corrupted Unturned files can cause connection-time errors that look like timeouts.

1. Open Steam.
2. Right-click Unturned in the library.
3. Select Properties.
4. Open the Installed Files tab.
5. Click "Verify integrity of game files."
6. Wait for the verification to complete; replace any corrupted files.
7. Re-attempt the connection.

The verification process is automated; Steam re-downloads any file that does not match the published checksum. The process typically takes 5-15 minutes depending on the connection speed and the number of files that need replacement.

Step 11: Test connectivity outside Unturned

If all of the above fail, confirm that the network path to the specific server works outside of Unturned.

1. Open PowerShell.
2. Run Test-NetConnection -ComputerName <server-ip> -Port <server-port> with the actual game port (often 27016).
3. Note that UDP cannot be directly tested with Test-NetConnection, but a TCP test on the query port (27015) is a strong proxy.

If the external test fails, the network path is the problem and Unturned-side troubleshooting will not help.

Step 12: Check for ISP-level UDP blocking

Some ISPs block or rate-limit UDP traffic, which Unturned requires for its game protocol. Symptoms include consistent timeouts to many servers, with TCP traffic working normally.

ISP-level UDP issues are difficult to diagnose without specialized tools. Indicators include:

• Multiple Unturned servers all time out despite passing every other test.
• Other UDP-heavy games (any voice chat, any peer-to-peer game) also show connectivity issues.
• TCP-based services (web browsing, downloads) work normally.

The resolution is to contact the ISP or to use a VPN that masks the UDP traffic inside an encrypted tunnel.

Port reference

The table below documents the default Unturned server ports and what each is used for.

Port (default)	Protocol	Purpose	Required for join?
27015	TCP	Steam query interface	No, but used for browser
27016	UDP	Game protocol	Yes
27017	TCP	RCON (admin commands)	No, optional
27018-27020	UDP	Steam authentication	Yes

Operators frequently change the ports for various reasons (avoiding collisions on a shared host, hiding the server from casual scanners). When an operator publishes a "port" without specifying which port, they usually mean the query port. The game port is typically the query port plus 1.

The full set of ports that need to be open for a successful connection includes 27015 (TCP), 27016 (UDP), and the Steam authentication ports in the 27018-27020 range (UDP). If any of these are blocked locally or upstream, the connection times out.

Did you know?

Unturned's network protocol uses several UDP ports for the actual game traffic, not just the game port. The additional ports are used by Steam's networking layer for authentication and NAT traversal. Operators do not need to forward all of these; the client and the server negotiate the additional ports dynamically during the connection handshake.

Local-side timeout causes

The table below documents the principal local-side causes of timeouts and the diagnostic indicator that points at each.

Cause	Diagnostic indicator	Resolution
Local firewall blocking Unturned	Firewall rule for Unturned is missing or disabled	Add firewall exception
VPN routing problem	Disconnecting VPN restores connectivity	Disconnect VPN or change region
Corrupted Steam download cache	Other Steam services also misbehaving	Clear Steam download cache
Corrupted Unturned files	Files verification reports replacement count	Verify files
Wrong IP or port	Test-NetConnection on correct port works	Use correct IP and port
Local network adapter issue	Other internet services also degraded	Restart network adapter
Local DNS resolution issue	Hostname-based connect fails, IP-based works	Use IP directly
Antivirus interfering	Disabling antivirus restores connectivity	Add antivirus exception
IPv6 misconfiguration	Disabling IPv6 restores connectivity	Disable IPv6 on Unturned-related interfaces
Outdated Unturned version	Server requires newer version	Update Unturned

Local-side causes are the most common single category in cohort reports because they are entirely within the player's control to investigate and fix. The cohort-validated approach is to systematically rule out each local-side cause before investigating network-path or server-side causes.

Network-path timeout causes

Cause	Diagnostic indicator	Resolution
ISP routing problem	tracert fails within ISP's network	Wait or contact ISP
Public internet routing problem	tracert fails at intermediate hop	Wait for path to recover
Host's ISP routing problem	tracert fails near destination	Wait
Home router QoS misconfiguration	High latency under load	Disable or reconfigure QoS
Home router NAT exhaustion	Connections fail after many concurrent	Restart router
ISP transparent proxy	Some protocols work, others time out	Use VPN to bypass
MTU mismatch	Some connections succeed, others time out at large payloads	Lower MTU on network interface
ISP UDP throttling	UDP-dependent games timeout, TCP works	Contact ISP or use VPN

Network-path issues are typically transient (resolving in minutes to hours) but can be persistent (lasting days when caused by a stable routing configuration problem). The player has limited recourse when the issue is in a network they do not control.

Server-side timeout causes

Cause	Diagnostic indicator	Resolution
Server overloaded	Connection succeeds for some players, times out for others	Wait or try at different time
Server's process unresponsive	Test-NetConnection succeeds but no game response	Operator restarts server
Server's host overloaded	Many simultaneous timeouts; high server-side latency	Wait for load to drop
Server's network saturated	High packet loss to the host	Wait or DDoS mitigation engages
EAC handshake stalling	Timeout occurs specifically at EAC step	Wait for EAC; verify EAC files
Server's database unreachable	Server fails to look up player record	Operator fixes database

Server-side causes require operator action to resolve. The player's role is to identify when the cause is server-side and report it with appropriate diagnostics to the operator. See Why Is the Server Down? for the operator-side perspective on these causes.

Worked example: full timeout diagnostic

The example below walks through a complete timeout diagnostic.

# Symptom: connection to 203.0.113.42:27016 times out repeatedly.

# Step 1: Confirm other Unturned servers work.
# Player joins a different server successfully. Original server is the issue.

# Step 2: Verify own internet works.
PS> ping 8.8.8.8
Reply from 8.8.8.8: bytes=32 time=18ms TTL=58
# Internet is fine.

# Step 3: Ping the server's host.
PS> ping 203.0.113.42
Reply from 203.0.113.42: bytes=32 time=42ms TTL=52
# Host is reachable.

# Step 4: Test the query port.
PS> Test-NetConnection -ComputerName 203.0.113.42 -Port 27015
TcpTestSucceeded : True
# Port is open. Server's network is fine.

# Step 5: Test the game port.
PS> Test-NetConnection -ComputerName 203.0.113.42 -Port 27016
# Note: UDP cannot be directly confirmed, but the TCP query port being open
# is a strong proxy for the server being reachable.

# Step 6: Trace the route.
PS> tracert 203.0.113.42
# Trace completes to the destination cleanly.

# Step 7: Disable VPN if active.
# No VPN in use.

# Step 8: Check local firewall.
PS> Get-NetFirewallRule -DisplayName "*Unturned*" | Select-Object Enabled, Action
# Two rules, both Enabled, both Action=Allow.

# Conclusion: Local-side is clean. Network path is clean. Server's port is reachable.
# Likely cause: server is up but is overloaded or rejecting the connection silently.
# Action: Wait and retry in a few minutes, or check the operator's Discord for status.

The worked example demonstrates the diagnostic narrowing: each step eliminates a category of cause, and the remaining cause is the one to act on.

Steam-side timeout causes

Steam itself is occasionally the source of timeouts even when the server, network, and client are all fine.

Steam matchmaking outage

When Steam's matchmaking service is degraded, the connection handshake stalls at the Steam authentication step. The client interprets the stall as a timeout.

Diagnostic indicators:

• Connections to multiple Unturned servers all time out simultaneously.
• Other Steam-integrated features (friends list, achievements) are also degraded.
• Steam's status pages report a matchmaking issue.

Resolution: wait for Steam to recover.

Steam Web API outage

When Steam's Web API is degraded, server-side player authentication fails, and the server cannot complete the connection. The client sees this as a timeout.

Diagnostic indicators:

• Connection makes some progress (Steam authentication step appears to complete on the client side) and then stalls.
• Other Steam-integrated features are degraded.
• Steam's status pages report a Web API issue.

Resolution: wait for Steam to recover.

Steam download cache corruption

A corrupted Steam download cache can cause Steam to misbehave during matchmaking and authentication, producing timeouts in connection handshakes.

Diagnostic indicators:

• Steam has been running for a long time without restart.
• Steam recently updated.
• Other servers also produce timeouts.

Resolution: clear the Steam download cache (Steam → Settings → Downloads → Clear Download Cache).

EAC-related timeout causes

Servers that use Easy Anti-Cheat (EAC) have an additional handshake step that can stall and produce a timeout.

EAC service outage

When EAC's central service is degraded, the EAC handshake takes longer than the client's timeout. The client gives up and reports a timeout.

Diagnostic indicators:

• Only EAC-enabled servers timeout; non-EAC servers connect normally.
• EAC's status page reports an outage.
• The timeout occurs at a specific point in the connection progress (typically right before "Connected").

Resolution: wait for EAC to recover.

EAC version mismatch

When the client's EAC version does not match the server's EAC version, the handshake can stall or fail. The client may report a timeout rather than a version-mismatch error.

Diagnostic indicators:

• Specific EAC servers timeout; other EAC servers work.
• Client recently updated.
• Server recently updated.

Resolution: verify Unturned files in Steam to refresh the EAC client.

EAC file corruption

Corrupted EAC files on the client side can cause the handshake to fail. The failure can be reported as a timeout.

Diagnostic indicators:

• All EAC servers timeout.
• Recently played EAC servers worked before.
• File verification in Steam reports replaced EAC files.

Resolution: verify Unturned files in Steam.

Pro tip

If the timeout is consistently EAC-related, Steam's "Verify integrity of game files" almost always resolves it. The verification re-downloads any corrupted EAC files. The process is non-destructive and is the cohort's recommended first action for EAC-suspected timeouts.

Timeout-versus-overload distinction

A common confusion is between "the server is unreachable" and "the server is overloaded." Both can produce timeouts, but the resolution differs.

Symptom	Unreachable	Overloaded
Test-NetConnection on query port	Fails	Succeeds
Ping to host	Often fails	Usually succeeds, possibly with high latency
Other players connecting	All fail	Some succeed
Server appears in browser	Often missing	Usually present, possibly with high ping
Resolution	Wait or operator action	Wait for load to drop

The distinction matters because overload is transient (resolves when load drops) and unreachable is potentially persistent (resolves when the operator acts). A player who recognizes their timeout is due to overload can simply wait 10-30 minutes and retry; a player who incorrectly diagnoses unreachable will spend time contacting an operator who cannot help in the moment.

Home network configuration timeouts

The home network configuration can produce timeouts in several specific ways. The table below documents the principal causes.

Configuration issue	Symptom	Resolution
Router QoS prioritizing other traffic	High latency on Unturned only when other devices active	Disable QoS or adjust priorities
Router NAT table full	Connections fail after extended sessions	Restart router
Double NAT (ISP and home router)	Some games work, others timeout	Bridge mode on home router
Router firmware bug	Intermittent timeouts after weeks of uptime	Update router firmware or restart
Wi-Fi packet loss	Timeouts only on wireless connections	Use wired Ethernet
ISP-provided modem in router mode	NAT table size limited; connections fail	Bridge mode and use own router
Strict NAT type	Connection succeeds but communication fails	Open ports on router or use UPnP
Multiple connections from same network	Steam treats as suspicious	Wait or stagger connections

The cohort's recommendation for home network timeouts is to first try a router restart, then to investigate any QoS or NAT configuration that may be active.

Frequently asked questions

Why does Unturned say connection timed out?

A timeout means the game client did not receive a response from the server within the client's wait window. The cause is not knowable from the message alone. See the diagnostic flowchart in this article to identify the specific cause: it could be a local firewall, a VPN, a network path issue, an overloaded server, a Steam matchmaking issue, or several other things.

How do I fix Unturned timeout error?

The cohort-validated workflow is: (1) confirm other Unturned servers work to rule out client-side issues; (2) verify the IP and port are correct; (3) ping the host and run Test-NetConnection on the query port; (4) check the local firewall and any active VPN; (5) clear Steam's download cache and verify Unturned files; (6) if all of these pass, the cause is on the server side or the network path, and the resolution is waiting or operator-side fixes.

Does VPN cause Unturned to timeout?

It can, for several reasons: the VPN can add latency that exceeds Unturned's timeout window, the VPN provider can block UDP traffic that Unturned requires, the VPN's exit IP can be blocked by the server, or the VPN can have geo-routing that produces a poor path to the server. Disconnecting the VPN and retesting is the cohort's first recommendation when a VPN is in use.

What ports does Unturned use?

The default ports are 27015 (Steam query, TCP), 27016 (game protocol, UDP), 27017 (RCON, TCP, optional), and 27018-27020 (Steam authentication, UDP). Operators frequently change these. The full set must be reachable for a successful connection.

Why does the timeout happen at exactly 30 seconds every time?

The Unturned game client has an internal connection timeout of approximately 30 seconds for the initial handshake. If the server does not respond within that window, the client gives up. A consistent 30-second timeout indicates the client is doing exactly what it is supposed to: waiting the full timeout window and then failing. The cause is on the network or server side, not the client.

Why does connection succeed for friends but not for me?

If a friend connects to the same server successfully while you cannot, the difference is in your network, not the server. Common causes: your local firewall is blocking Unturned, your VPN is interfering, your home router has a NAT issue, your ISP is routing your traffic differently than your friend's ISP. The diagnostic in this article walks through each.

Can I extend Unturned's connection timeout?

Unturned does not expose a user-configurable timeout for the game client. The 30-second timeout is fixed. Even if it were configurable, extending it would not fix the underlying cause of the timeout; it would only delay the failure.

Why does my connection time out only on certain servers?

If specific servers time out while others work, the server is the problem (or the network path to that specific server). If a server has been working before and now times out, the server has likely changed state (overload, crash, configuration change). If the server has consistently timed out for you despite working for others, the network path between your ISP and the server's ISP is likely the cause.

What does "Server is not responding" mean?

"Server is not responding" is Unturned's variant phrasing for a timeout. The cause and resolution are the same as a generic timeout.

Why does the timeout happen right after I see "Connecting..."?

The "Connecting..." state covers several handshake steps. A timeout right after "Connecting..." typically means the Steam authentication step or the EAC handshake step is stalling. If the server uses EAC, the EAC step is the most likely cause; verify Unturned files in Steam to refresh the EAC client.

Can a firewall on my router cause timeouts?

Yes. Home routers have their own firewalls that can block specific ports or protocols. Most home routers default to permissive outgoing traffic but restrictive incoming. Unturned's connection is outgoing from the client's perspective, so the router firewall usually does not interfere. Exceptions include routers configured for strict NAT or routers with active intrusion-prevention features that flag game traffic as suspicious.

Why do I get timeouts on Wi-Fi but not Ethernet?

Wi-Fi has higher packet loss than wired Ethernet, and packet loss during the handshake can cause timeouts. The recommendation for any sustained Unturned play is wired Ethernet; the recommendation specifically when diagnosing timeouts is to switch to wired and retest before concluding the server is the issue.

Why did my connection start timing out after a Windows Update?

Windows Updates can change network adapter drivers, firewall rules, or system services. Any of these can introduce a timeout cause that was not present before. The cohort recommendation is to: check the firewall rules (Windows Update sometimes resets them), check the network adapter driver, and verify Unturned files in case the update affected Unturned-dependent components.

Should I disable IPv6 to fix timeouts?

IPv6 misconfiguration occasionally causes timeouts when the client attempts to connect over IPv6 and falls back slowly to IPv4. Disabling IPv6 on the Unturned interface is a documented workaround but is not generally needed. The cohort recommendation is to disable IPv6 only after other causes have been ruled out.

Appendix A: Cause-and-remedy reference

The table below collects the principal timeout causes from this article into a single reference.

Cause	Indicator	Remedy
Wrong port in direct-connect	Test-NetConnection on correct port works	Use correct port
Local firewall blocking	Firewall rule missing	Add Unturned exception
VPN interference	Disconnecting VPN works	Disconnect or change VPN region
Corrupted Steam cache	Other Steam features misbehaving	Clear Steam download cache
Corrupted Unturned files	File verification reports replacements	Verify Unturned files
ISP routing	tracert fails in ISP's network	Wait or contact ISP
Public internet routing	tracert fails mid-path	Wait
Server overload	High player count, sometimes works	Wait
Server process unresponsive	Test-NetConnection succeeds, join fails	Operator restarts
Steam matchmaking outage	Multiple servers timeout	Wait
Steam Web API outage	Auth fails after partial progress	Wait
EAC outage	EAC-enabled servers timeout specifically	Wait
EAC client corruption	All EAC servers timeout	Verify Unturned files
Wi-Fi packet loss	Timeouts on wireless only	Switch to wired
Router NAT exhaustion	Timeouts after extended uptime	Restart router
ISP UDP throttling	UDP-dependent games timeout, TCP works	Contact ISP or use VPN
Antivirus interference	Disabling AV restores connectivity	Add AV exception
MTU mismatch	Some traffic works, large payloads timeout	Lower MTU

The cohort's recommended workflow is to identify the indicator and apply the remedy. Most timeout causes have a clear indicator that distinguishes them.

Appendix B: Diagnostic command reference

The table below documents the PowerShell commands referenced in this article.

Command	Purpose	Key output
Test-NetConnection -ComputerName <ip> -Port <port>	Test TCP port reachability	TcpTestSucceeded
ping <ip>	Test ICMP reachability and latency	Reply times, packet loss
tracert <ip>	Show network path and identify failure point	Last responding hop
Resolve-DnsName <hostname>	Resolve hostname to IP	IPv4Address
Get-NetFirewallRule -DisplayName "*Unturned*"	Show Unturned firewall rules	Enabled, Action
Get-NetAdapter	Show network adapter status	Status (Up/Down)
Get-VpnConnection	Show active VPN connections	ConnectionStatus
ipconfig /flushdns	Clear DNS resolver cache	(clears cache)
netsh int ip reset	Reset TCP/IP stack	(resets stack; requires restart)
netsh winsock reset	Reset Windows Sockets	(resets sockets; requires restart)

The last two commands are aggressive resets and should be used only when other commands have not identified the cause. They require a system restart to take effect.

Appendix C: Escalation paths

When the diagnostic steps in this article do not produce a clear answer, the escalation paths below describe the next steps.

Local-side timeouts not resolved by the diagnostic

If the local-side diagnostic steps do not identify the cause:

1. Reboot the computer. Many transient local-side issues resolve with a reboot.
2. Reinstall Unturned. Uninstall via Steam, then reinstall. This rules out installation-level corruption.
3. Reinstall Steam. Uninstall and reinstall Steam itself if multiple Steam-related features are misbehaving.
4. Contact your ISP. If the issue persists across multiple games and other diagnostic steps point at the network, the ISP may be the cause.

Server-side timeouts not resolved by waiting

If a server appears reachable (Test-NetConnection succeeds) but joins consistently time out:

1. Report to the operator with the diagnostic results.
2. Check the operator's Discord or status page for any active issues.
3. Wait and retry in 1-2 hours; many overload-related timeouts resolve as player count drops.
4. Find an alternative server in the interim.

Platform-side timeouts

When the cause is Steam or EAC:

1. Wait. Platform outages typically resolve within hours.
2. Monitor the relevant status pages for recovery announcements.
3. For EAC outages specifically, non-EAC servers can be used as a fallback.

Best practices

• Run the two-server test first to separate client-side from server-side causes.
• Verify the published server port before troubleshooting; many timeouts are from wrong-port attempts.
• Use the cohort-validated diagnostic order: local, then network, then server.
• Include diagnostic results in reports to operators; "Test-NetConnection succeeds but join times out" is far more actionable than "connection times out."
• Keep Unturned's files verified periodically; corrupted files cause many otherwise-unexplained timeouts.
• Clear Steam's download cache after Steam updates if connectivity issues appear.
• Use wired Ethernet for any sustained Unturned play; Wi-Fi packet loss is a common timeout cause.
• Document recurring timeout patterns; patterns help identify whether the cause is local, network, server, or platform.

Closing notes

Connection timeouts in Unturned cover a wide range of underlying causes. The diagnostic flowchart in this article is designed to identify the specific cause for any given timeout. Most timeouts fall into one of four categories: local-side configuration, network-path issues, server overload or rejection, or platform issues (Steam, EAC). The resolution is different for each, and applying the wrong resolution wastes time without helping.

Players who internalize the diagnostic flowchart and the cause-indicator-remedy mapping can typically identify the cause of a timeout within 5 minutes. The information also makes operator support requests dramatically more useful; an operator who receives a report including "Test-NetConnection on port 27015 succeeds, ping to host succeeds with 42ms latency, timeout occurs after 30 seconds of 'Connecting...' state" can move directly to the correct server-side investigation rather than starting from "the server is broken."

Cross-references

• Is the Server Up? — the article two steps back in the wiki, covering the initial server-status diagnostic that should precede any timeout-specific investigation.
• Why Is the Server Down? — the previous article in the wiki, covering server-side outage causes that may underlie a timeout.
• Unable to Connect to the Server — the next article in the wiki, covering connection failures that do not fit the timeout pattern.
• Recommended Server Hardware — for operators investigating whether host hardware is contributing to timeout-producing overload.
• Setting Up Your Server Panel — for operators using a control panel to diagnose server-side timeout causes.

Document history

Version	Date	Notes
1.0	2024-08-21	Initial publication. Covered local-side and network-path causes.
1.1	2024-11-04	Added server-side and platform-side causes.
1.2	2025-02-18	Added worked example and EAC-specific causes.
2.0	2025-05-17	Major revision. Added decision matrix, cause-indicator-remedy mappings, and escalation paths.

Glossary

• Timeout — a connection failure caused by no response within the configured wait window.
• Connection refused — a connection failure caused by the server actively rejecting the connection.
• Test-NetConnection — a PowerShell cmdlet for testing TCP port reachability.
• Ping — an ICMP-based reachability test.
• Tracert — a tool that shows the network path between two hosts and identifies failure points.
• EAC — Easy Anti-Cheat; a third-party anti-cheat service used by many Unturned servers.
• NAT — Network Address Translation; how home routers map internal network connections to a single public IP.
• QoS — Quality of Service; router-level traffic prioritization that can inadvertently delay game traffic.
• MTU — Maximum Transmission Unit; the largest packet size a network path supports without fragmentation.
• UDP — User Datagram Protocol; the connectionless transport Unturned uses for game traffic.
• TCP — Transmission Control Protocol; the connection-oriented transport Steam uses for queries.

Appendix D: Worked diagnostic walkthroughs

The walkthroughs below illustrate the diagnostic process for several common timeout scenarios.

Walkthrough 1: VPN-induced timeout

Symptom: Connection to a previously working server now times out. No recent client changes; a VPN was recently connected.

Diagnostic:

# Step 1: Confirm other Unturned servers also timeout while VPN is active.
# Other servers also timeout. Issue is not server-specific.

# Step 2: Disconnect the VPN.
PS> Get-VpnConnection | Where-Object ConnectionStatus -eq "Connected" | Disconnect-VpnConnection

# Step 3: Retry the connection to Unturned.
# Connection succeeds immediately.

Conclusion: The VPN was adding latency that exceeded Unturned's timeout, or blocking the UDP traffic that Unturned requires.

Resolution: Disconnect the VPN for Unturned sessions, or switch to a VPN provider with better UDP handling, or use a VPN exit region geographically closer to the server.

Walkthrough 2: Firewall-blocked timeout after Windows Update

Symptom: Unturned was working before a Windows Update; after the update, all connections time out.

Diagnostic:

# Step 1: Confirm internet works.
PS> ping 8.8.8.8
# Reply OK.

# Step 2: Check Unturned firewall rules.
PS> Get-NetFirewallRule -DisplayName "*Unturned*" | Select-Object DisplayName, Enabled, Action
# DisplayName       Enabled Action
# ------------      ------- ------
# Unturned          False   Allow
# Unturned          False   Allow
# Rules are present but disabled.

# Step 3: Re-enable the rules.
PS> Get-NetFirewallRule -DisplayName "*Unturned*" | Enable-NetFirewallRule

# Step 4: Retry the connection.
# Connection succeeds.

Conclusion: Windows Update disabled the Unturned firewall rules. This sometimes happens after major Windows updates.

Resolution: Re-enable the firewall rules. Going forward, after each major Windows Update, verify that Unturned-related firewall rules are still enabled.

Walkthrough 3: EAC handshake timeout

Symptom: Connection to an EAC-enabled server times out at the moment the connection progress indicator says "Authenticating." Non-EAC servers work fine.

Diagnostic:

# Step 1: Other EAC servers also timeout. Issue is EAC-side.
# Step 2: Check EAC status page. No reported outage.
# Step 3: Verify Unturned files in Steam.
# Steam reports 3 files needed replacement; replacement complete.
# Step 4: Retry the connection.
# Connection succeeds.

Conclusion: EAC client files were corrupted (cause unknown). The file verification re-downloaded the corrupted files.

Resolution: File verification fixed the issue. The cohort recommendation is to run file verification monthly as a defensive practice.

Walkthrough 4: Wi-Fi packet-loss timeout

Symptom: Connection to a specific server times out about 50 percent of the time. The other 50 percent it works.

Diagnostic:

# Step 1: Ping the server with extended duration.
PS> ping -n 50 203.0.113.42
# Packets: Sent = 50, Received = 38, Lost = 12 (24% loss)
# 24% packet loss is consistent with Wi-Fi interference.

# Step 2: Switch to wired Ethernet and retest.
PS> ping -n 50 203.0.113.42
# Packets: Sent = 50, Received = 50, Lost = 0 (0% loss)

# Step 3: Retry the Unturned connection on wired.
# Connects every time.

Conclusion: Wi-Fi packet loss was occasionally affecting the handshake. The handshake is sensitive to packet loss; even moderate loss (10-20 percent) can cause intermittent timeouts.

Resolution: Use wired Ethernet for Unturned sessions. If wired is not available, move closer to the Wi-Fi access point or switch the access point to a less congested channel.

Appendix E: Common ISP-side timeout patterns

The table below documents ISP-side patterns that produce timeouts, with the cohort's recommended player-side workarounds.

ISP-side pattern	Symptom	Player workaround
Aggressive deep packet inspection	All UDP-heavy games degraded	VPN to bypass DPI
UDP rate-limiting	Long sessions degrade; new connections timeout	VPN or wait between sessions
Route flapping	Intermittent timeouts to specific destinations	Wait; some routes self-heal
Transit congestion	High latency during peak hours	Play during off-peak
BGP route leak	Sudden specific destinations unreachable	Wait for resolution
ISP-imposed NAT	Strict NAT type breaks game protocol	Request public IP or use VPN
Throttling during high traffic	Latency spikes under load	Reduce simultaneous network use
IPv6 misconfiguration	Some destinations unreachable on IPv6	Disable IPv6

ISP-side patterns are typically not under the player's control. The workarounds are limited to using a VPN to bypass the ISP for specific connections, contacting the ISP to report the issue, or working around the issue by adjusting timing or other parameters.

Appendix F: Diagnostic script templates

The PowerShell snippets below are cohort-validated templates that can be copy-pasted to run a quick diagnostic.

Quick health check

# Quick connectivity health check.
# Replace SERVER_IP with the actual server IP.

$serverIp = "203.0.113.42"
$queryPort = 27015
$gamePort = 27016

# Test internet.
Write-Host "Testing own internet..."
Test-NetConnection -ComputerName 8.8.8.8 -Port 443 -InformationLevel Quiet

# Ping the host.
Write-Host "Pinging $serverIp..."
$pingResult = Test-Connection -ComputerName $serverIp -Count 4 -Quiet
Write-Host "Ping result: $pingResult"

# Test query port.
Write-Host "Testing query port $queryPort..."
$queryResult = Test-NetConnection -ComputerName $serverIp -Port $queryPort -InformationLevel Quiet
Write-Host "Query port reachable: $queryResult"

# Check firewall rules.
Write-Host "Checking Unturned firewall rules..."
Get-NetFirewallRule -DisplayName "*Unturned*" | Format-Table DisplayName, Enabled, Action

Extended packet-loss check

# Extended packet-loss check.
# Runs 100 pings to identify packet-loss patterns.

$serverIp = "203.0.113.42"
$pings = Test-Connection -ComputerName $serverIp -Count 100 -ErrorAction SilentlyContinue
$received = ($pings | Measure-Object).Count
$lost = 100 - $received
$lossPercent = ($lost / 100) * 100

Write-Host "Sent: 100"
Write-Host "Received: $received"
Write-Host "Lost: $lost ($lossPercent percent)"

if ($received -gt 0) {
    $avgLatency = ($pings | Measure-Object -Property ResponseTime -Average).Average
    Write-Host "Average latency: $avgLatency ms"
}

Route check

# Route check.
# Identifies where in the network path failures occur.

$serverIp = "203.0.113.42"
tracert $serverIp

The scripts are templates; modify the IP and port for the specific server being investigated. The cohort recommendation is to save the scripts as .ps1 files in a troubleshooting/ folder for quick reuse.

Next steps

If the diagnostic steps in this article have identified the cause and the connection still fails after the appropriate resolution, see Unable to Connect to the Server for connection failures that do not fit the timeout pattern. If the issue is server-side and the operator is investigating, see Why Is the Server Down? for additional context on server-side outage resolution. Return to the section overview at Troubleshooting for a list of all articles in this section.