Is the Server Up?
Server status confusion in Unturned™ can have several causes, and the answer to "is the server up?" is rarely as simple as a single yes or no. This article walks through the most common methods to verify whether a specific Unturned server is currently online, reachable, and accepting connections, along with how to distinguish the different ways a server can be unavailable to a given player.
A server can be running and accepting connections from most players while being unreachable from one specific player's network. A server can be online but full, with every slot occupied. A server can appear in the in-game server browser but refuse new connections because the matchmaking back-end is having problems. A server can be completely offline and not in the browser at all. Each of these states feels the same from inside the game: the player tries to connect and something does not work. Sorting out which state actually applies is the first step in any server-side troubleshooting workflow.
What this article covers
- How to check whether a server appears in the in-game server browser.
- How to use a Steam friend who is on the server to verify the server is reachable from at least one location.
- How to use third-party server-list sites that track Unturned server uptime independently of the in-game browser.
- How to use direct-connect by IP address when the server does not appear in the browser.
- How to use PowerShell's
Test-NetConnectionto verify that the server's port is open from your network. - How to use
pingandtracertto identify whether the connectivity problem is between you and the server. - How to verify that Steam itself is online and that Steam matchmaking is functioning.
- How to interpret the difference between "server is up but full," "server is up but unreachable from your network," and "server is offline."
Prerequisites
- Unturned installed via the official Steam client. The Steam store page for the game is at the Unturned product page.
- A working internet connection from the machine that is trying to connect.
- Administrator access for some of the diagnostic commands.
- The server's IP address and port if it is not listed in the in-game browser. The default Unturned server query port is 27015 (Steam query) and the default game port is 27016, but operators frequently change these.
Background: what "up" actually means
The word "up" hides a lot of complexity. An Unturned server is a process running on a host machine somewhere on the internet. For a player to successfully connect, every one of the following must be true:
- The server process itself is running and has not crashed.
- The server's host machine is powered on and connected to the internet.
- The host's network can reach the public internet (no ISP outage at the host's location).
- The server's UDP and TCP ports are open and forwarded correctly.
- Steam's matchmaking service is online and the server has registered itself with Steam.
- The Easy Anti-Cheat (EAC) service is online if the server uses EAC.
- The player's own network can reach the server's host (no routing problem between the two networks).
- The player's local firewall allows the outgoing connection.
- The server has available player slots.
- The server's whitelist (if any) includes the player's Steam ID.
Any one of these failing produces a "can't connect" symptom. The diagnostic methods below are designed to identify which one has failed.
The flowchart above models the diagnostic decision tree that the rest of this article walks through. Each branch corresponds to a different state the server can be in, and each terminal node points at a different remediation.
The five states a server can be in
Before running any commands, it helps to understand the five distinct states that an Unturned server can be in from any given player's perspective. The diagnostic steps that follow are designed to identify which state applies.
| State | Server process | Network reachable | Slots available | What player sees |
|---|---|---|---|---|
| Fully up | Running | Yes | Yes | Server appears in browser, connection succeeds |
| Up but full | Running | Yes | No | Server appears in browser, connection refused with "server full" |
| Up but unreachable | Running | No from your network | N/A | Server may or may not appear in browser, connection times out |
| Up but unregistered | Running | Yes | Yes | Server does not appear in browser; direct connect works |
| Offline | Not running | N/A | N/A | Server does not appear in browser; direct connect fails |
The "up but unregistered" state is common immediately after a server restart, when the server process is running but has not yet completed its handshake with Steam's master server list. It typically resolves on its own within a few minutes.
Did you know?
Unturned uses Steam's master server list to populate the in-game server browser. A server can be running and accepting connections for hours before it appears in the browser if its handshake with Steam's master server has failed. Direct connect by IP works during this window, even though the browser does not show the server.
Diagnostic steps
Step 1: Check the in-game server browser
The simplest first check is the in-game server browser.
- Launch Unturned from Steam.
- From the main menu, select Play.
- Select Servers.
- Select Internet (or LAN if the server is on the same local network).
- Wait for the browser to populate. The list can take 10-30 seconds to populate on the first load.
- Use the search box to filter for the server's name.
If the server appears in the browser with a non-zero player count, the server is up and reachable from at least Steam's master server. If the server appears with a "full" indicator, the server is up but has no available slots. If the server does not appear, proceed to the next step.
Pro tip
The in-game server browser sometimes shows stale data. A server that has just been restarted may not appear for 1-3 minutes after restart even if it is running. A server that has just gone offline may continue to appear for 1-3 minutes after shutdown. Wait a few minutes and refresh before concluding that a missing server is offline.
Step 2: Refresh the browser
If the server does not appear on the first load, refresh the browser before concluding the server is offline.
- In the server browser, click Refresh (or press F5).
- Wait for the refresh to complete.
- Re-apply the name filter.
- Check whether the server now appears.
A first-load failure followed by a refresh-success is common when the Steam master server has not finished responding to the initial query. The refresh forces a new query.
Step 3: Check the History and Favorites tabs
If you have previously connected to the server, it may appear in your History or Favorites tabs even if it does not appear in the Internet tab.
- In the server browser, click History.
- Look for the server name.
- If found, the entry shows the last-known status.
The History tab is useful for confirming the server's IP address if you have forgotten it. The IP shown in History is the address Unturned last used to connect, which is the same address the direct-connect method needs in the next step.
Step 4: Try direct connect by IP
If the server does not appear in the browser, try connecting directly by IP. The direct-connect method bypasses the browser and the Steam master server list entirely.
- From the server browser, click Connect (some versions label this Direct Connect or Join by IP).
- Enter the server's IP address.
- Enter the server's port (usually 27015 for the game port; some servers use a different port).
- Click Connect.
If the direct-connect succeeds, the server is up and reachable from your network, but is not currently registered with the Steam master server. Notify the server's operator that the server is missing from the browser. The fix is usually a server restart, which forces a fresh registration with Steam.
If the direct-connect fails with "connection refused" or "connection timed out," proceed to the next step.
Common mistake
Confusing the game port with the query port. The query port (often 27015) is what the Steam master server uses to ask the server for its status; the game port (often 27016 for Unturned) is what the game client uses to connect. The direct-connect dialog expects the game port, not the query port. If the server operator has published one number and not the other, the published number is usually the query port; the game port is usually the query port plus 1.
Step 5: Check if a Steam friend is on the server
If you have a Steam friend who is currently playing on the server, their presence on the server is independent verification that the server is reachable from at least one player's network.
- Open Steam (the standalone Steam application, not the in-game Steam overlay).
- Open the Friends list.
- Look for the friend's status. If they are playing Unturned, their status shows the game name.
- If the friend's status shows server details, the server name and IP appear in the tooltip when you hover over the friend's status line.
- Right-click the friend and select Join Game.
If Join Game succeeds, the server is reachable from your network. If Join Game fails with "server is full" or "this game is on a server with a password," the server is up but is refusing your connection for the reason given.
Step 6: Check a third-party server-list site
Several third-party server-list sites track Unturned server uptime independently of Steam's master server list. The sites query servers directly on a periodic schedule and maintain a history of the server's uptime.
Without endorsing any specific site, the general approach is:
- Open a web browser.
- Search for "Unturned server list" or "Unturned server tracker."
- Open one of the prominent results.
- Search the site for the server by name or IP.
- The site reports the server's current status (online or offline), the current player count, and a historical uptime graph.
The uptime graph is particularly useful for distinguishing between "server has been offline for hours" and "server has been online but is briefly unreachable from your network." A flat-line uptime in the graph indicates the server has been consistently up; gaps in the line indicate periods when the site's queries failed.
Did you know?
Third-party server-list sites query servers from their own infrastructure, which is typically in a major data center with excellent connectivity. A server that appears online on a server-list site but unreachable from your home network is almost always a problem with your network's route to the server, not a problem with the server itself.
Step 7: Use PowerShell's Test-NetConnection
If the server does not appear reachable through the in-game methods, PowerShell's Test-NetConnection cmdlet can confirm whether the server's port is open from your network.
- Open PowerShell.
- Run the following command, substituting the server's IP and port:
powershell
Test-NetConnection -ComputerName 203.0.113.42 -Port 27015- Wait for the result.
The result includes a TcpTestSucceeded field. If the value is True, the server's port is open and reachable from your network. If the value is False, the port is closed or the network path between you and the server is broken.
Unturned uses UDP for its game protocol, but the Steam query port (27015) uses TCP. A successful TCP test on port 27015 indicates the Steam query interface is reachable, which is a strong proxy for the server being up.
Step 8: Ping the server
Ping is the simplest possible reachability test. Ping sends an ICMP echo request to the server and waits for a reply.
- Open PowerShell.
- Run the following command, substituting the server's IP:
powershell
ping 203.0.113.42- Observe the results.
If the server replies, the server's host is up and reachable from your network. If the replies time out, either the server's host is down, the server's host is blocking ICMP (some operators do this for security reasons), or the network path between you and the server is broken.
A ping that succeeds combined with a port test that fails indicates the server's host is up but the server process itself is not listening on the queried port.
Common mistake
Concluding that a server is offline solely because ping fails. Many server operators block ICMP at the firewall to reduce noise from network scanners. A blocked ping does not mean the server is offline; it means ICMP is filtered. Use Test-NetConnection on the actual server port for a more reliable test.
Step 9: Trace the route to the server
If ping and Test-NetConnection both fail, tracert (traceroute) identifies where in the network path the connection is breaking.
- Open PowerShell.
- Run the following command, substituting the server's IP:
powershell
tracert 203.0.113.42- Wait for the trace to complete. A trace can take 30-60 seconds for a multi-hop path.
The output is a list of network hops between your machine and the server. Each hop's response time is shown. The trace stops at the first hop that does not respond, or at the destination if the destination responds.
Common failure patterns in the trace:
- Trace completes successfully to the destination: the network path is fine; the problem is at the server itself.
- Trace fails at your ISP's first or second hop: your home internet connection has a problem.
- Trace fails at a middle hop in the public internet: a routing problem between your ISP and the server's ISP, typically transient.
- Trace fails at the last hop before the destination: the server's ISP is filtering or the server's host is firewalled.
Step 10: Check Steam itself
If multiple servers are unreachable, the problem may be Steam itself rather than any specific server.
Several third-party sites track Steam's service status independently of Steam. Without endorsing any specific site, the general approach is:
- Open a web browser.
- Search for "Steam status."
- Open one of the prominent results.
- Check the current status of the Steam Community, Steam matchmaking, and Steam game coordinator services.
If Steam matchmaking is reporting an outage, the in-game server browser will not populate correctly, and many or all servers will appear offline. The fix is to wait for Steam to recover; there is nothing the player can do.
Pro tip
The Steam Community page itself (steamcommunity.com) is a useful informal Steam-up check. If the page loads slowly or fails to load, Steam is having problems. The page is hosted on the same infrastructure as much of Steam's user-facing services, so its responsiveness is a proxy for the platform's health.
Step 11: Check Easy Anti-Cheat status
If the server uses Easy Anti-Cheat (EAC) and the EAC service is down, the server will appear up but reject connections at the EAC handshake step.
EAC's status is documented on the EAC website. Without endorsing any specific URL, the general approach is to search for "Easy Anti-Cheat status" and check the official EAC status page.
If EAC is down and the server requires EAC, the only resolution is to wait for EAC to recover.
Step 12: Verify your own internet connection
Before concluding that any server is unreachable, verify that your own internet connection is functioning.
- Open PowerShell.
- Run
ping 8.8.8.8(Google's public DNS server). - Run
ping 1.1.1.1(Cloudflare's public DNS server). - If both fail, your internet connection is the problem, not the server.
If your internet is down or degraded, no server will be reachable. The fix is at your ISP, your home router, or your network configuration, not at the Unturned server.
Browser-versus-direct-connect comparison
The table below compares the in-game server browser with the direct-connect method.
| Aspect | In-game browser | Direct connect by IP |
|---|---|---|
| Requires Steam master server | Yes | No |
| Requires knowing the server's IP | No | Yes |
| Shows current player count | Yes | No (until connected) |
| Shows server description | Yes | No |
| Shows server's tags and metadata | Yes | No |
| Works if server is unregistered | No | Yes |
| Works if Steam matchmaking is down | No | Yes (usually) |
| Convenient for finding new servers | Yes | No |
| Convenient for joining known servers | Yes | Yes |
The browser is the convenience interface; direct-connect is the reliable interface. When the browser fails, direct-connect is usually the fastest way to verify whether the server itself is up.
State diagnosis decision matrix
The table below maps the combined results of the diagnostic steps to the server state that the results indicate.
| Browser shows server | Friend on server | Direct connect succeeds | Test-NetConnection succeeds | Most likely state |
|---|---|---|---|---|
| Yes | Yes | Yes | Yes | Fully up; just join |
| Yes | Yes | No (refused) | Yes | Up but full or whitelist |
| Yes | No | Yes | Yes | Fully up |
| Yes | No | No (timeout) | No | Up but unreachable from your network |
| No | Yes | Yes | Yes | Up but unregistered with Steam |
| No | Yes | No | Yes | Up but rejecting your connection |
| No | No | Yes | Yes | Up but unregistered with Steam |
| No | No | No | Yes | Port open but server not responding |
| No | No | No | No | Server offline or network broken |
| No | No | No | No (and ping 8.8.8.8 fails) | Your internet is down |
The matrix is the cohort's recommended quick-reference for diagnosis. Locate the row that matches the observed results and apply the indicated diagnosis.
What to do for each state
Fully up: just join
The server is online and reachable. Join through the browser or direct-connect. If the join still fails despite all checks passing, see Server Connection Timeout and Unable to Connect to the Server for connection-time troubleshooting.
Up but full: wait or find another server
The server is up but has no available slots. Options:
- Wait for a slot to open. Most full servers cycle through a few players per hour as people log off.
- Check whether the server has a queue system. Some servers operate a join queue; entering the queue reserves the next available slot for you.
- Check whether the server has paid priority access. Some servers offer paid VIP slots that bypass the full state.
- Find another server with similar settings and play there.
Up but unreachable from your network: identify the network problem
The server is up and reachable from other players, but your network cannot reach it. Common causes and resolutions:
- Your local firewall is blocking the outgoing connection. Add an exception in Windows Defender Firewall for Unturned.exe.
- Your VPN is misrouting the connection. Disconnect the VPN and retry.
- Your ISP is throttling or blocking the server's IP. Contact your ISP.
- A network path between your ISP and the server's ISP is broken. Wait for the path to recover (typically minutes to hours) or use a VPN that routes around the broken path.
Up but unregistered with Steam: notify the operator
The server is up but is missing from the Steam master server list. The fix is on the operator's side: usually a server restart, sometimes a re-registration with Steam. Notify the operator that the server is missing from the browser. In the meantime, players can connect by direct-connect.
Offline: wait or notify the operator
The server is not running. The operator must bring the server back online. See Why Is the Server Down? for the operator-side perspective on why servers go offline.
PowerShell diagnostic command reference
The table below documents the PowerShell commands used in the diagnostic steps above, with the typical interpretation of each result.
| Command | Purpose | Expected result if server is up | What a failure means |
|---|---|---|---|
Test-NetConnection <ip> -Port 27015 | Test TCP connectivity to the Steam query port | TcpTestSucceeded: True | Server is not listening on this port, or path is blocked |
Test-NetConnection <ip> -Port 27016 | Test connectivity to the game port | Result varies (UDP not always testable) | Limited diagnostic value for UDP |
ping <ip> | Test ICMP reachability to the host | Replies with low latency | Host is down or ICMP is filtered |
tracert <ip> | Trace the network path to the host | Trace completes to destination | Path is broken at the last responding hop |
Resolve-DnsName <hostname> | Resolve a hostname to an IP | Returns one or more IPs | DNS or hostname is invalid |
ping 8.8.8.8 | Test your internet connectivity | Replies with low latency | Your internet is broken |
Get-NetIPConfiguration | Show your network configuration | IPv4Address and DefaultGateway present | Your network interface is misconfigured |
Worked example: full diagnostic for an unreachable server
The example below walks through a complete diagnostic for a server that the player cannot reach.
powershell
# Step 1: Verify own internet
PS> ping 8.8.8.8
Reply from 8.8.8.8: bytes=32 time=18ms TTL=58
# Own internet is fine.
# Step 2: Test the server's Steam query port
PS> Test-NetConnection -ComputerName 203.0.113.42 -Port 27015
ComputerName : 203.0.113.42
RemoteAddress : 203.0.113.42
RemotePort : 27015
TcpTestSucceeded : False
# Port test failed. Server may be down or port may be blocked.
# Step 3: Ping the host
PS> ping 203.0.113.42
Reply from 203.0.113.42: bytes=32 time=42ms TTL=52
# Host is up. The server process is likely not running, or the port is blocked.
# Step 4: Trace the route
PS> tracert 203.0.113.42
# (trace output)
# Trace completes to the destination, confirming the network path is fine.
# Conclusion: Server's host is up, but the Unturned server process is not running.
# Action: Notify the operator. See "Why Is the Server Down?" for operator-side troubleshooting.The worked example demonstrates the cohort's recommended workflow: rule out your own internet first, then test the server's port, then ping the host, then trace the route. Each step narrows the cause.
Server browser behavior reference
The in-game server browser has a number of behaviors that are worth understanding for diagnosis.
| Browser behavior | What it means | Recommended action |
|---|---|---|
| Browser loads slowly (>30 seconds) | Steam master server is responding slowly | Wait or retry |
| Browser shows 0 servers | Steam master server query failed entirely | Refresh the browser |
| Browser shows fewer servers than expected | Steam master server returned partial results | Refresh the browser |
| Server shows in browser but join fails | Server is up but is rejecting your connection | See connection-time troubleshooting |
| Server shows in browser with stale player count | Browser data is cached | Refresh and recheck |
| Server appears and disappears between refreshes | Server's registration with Steam is unstable | Notify operator; direct-connect for now |
| Server's ping appears as 9999 or unknown | Browser cannot reach server to ping | Server may be in a different region |
| Browser sorted differently each time | Steam returns servers in arbitrary order | Use the name filter |
The browser is fundamentally a convenience UI on top of Steam's master server list. When the browser misbehaves, the underlying Steam query is usually the cause, and the fix is to refresh or retry.
Operator-side context
This article is written from the perspective of a player trying to determine whether a server is up. Server operators reading this article for the operator's perspective should also consult:
- Why Is the Server Down? for common server-side outage causes.
- Recommended Server Hardware for the hardware baseline that minimizes operator-side downtime.
- Setting Up Your Server Panel for the operator-side control panel that shows server status directly.
Operators with access to the server's host can verify the server's actual state by inspecting the server process and the server's logs directly. The methods in this article are designed for players who do not have host-side access.
Frequently asked questions
Is the Unturned server down right now?
There is no single answer; "the Unturned server" is not a single thing. Unturned has thousands of community-operated servers, each of which can be independently up or down. To check a specific server, use the methods in this article. To check whether Steam itself (which powers the in-game server browser) is having a wider issue, search for "Steam status" and consult a status-tracker site.
How do I check Unturned server status?
The fastest check is the in-game server browser. If the server appears in the browser with a non-zero player count, it is up. If it does not appear, try direct-connect by IP, then Test-NetConnection, then ping the host. The diagnostic flowchart at the top of this article walks through the full sequence.
Why is steamcommunity.com slow?
steamcommunity.com is hosted on Steam's infrastructure. Slowness on the page is a proxy for Steam itself being under load or partially degraded. If the page is slow, the in-game server browser is likely to be slow or empty as well. Wait for Steam to recover.
Can I check if a friend's server is online without joining?
Yes. If the friend is on the server, your Steam Friends list shows them playing Unturned and may show the server details in the tooltip. The friend's presence on the server is direct evidence that the server is up. If the friend is not on the server, use the in-game browser, direct-connect, or Test-NetConnection on the server's IP and port.
Why does the server appear in my Favorites but not in the Internet tab?
The Internet tab requires the server to be registered with Steam's master server list at the moment you load the tab. The Favorites tab stores the server's IP directly and queries the server directly, bypassing the master server. If the server is up but not currently registered with Steam, it will appear in Favorites but not Internet. The fix is on the operator's side; in the meantime, use Favorites or direct-connect.
How long does it take for a restarted server to appear in the browser?
The handshake with Steam's master server typically completes within 1-3 minutes of server startup. If the server has been restarted within the last 3 minutes and is missing from the browser, wait and refresh. If the server has been up for more than 5 minutes and is still missing, the registration has failed and the operator needs to investigate.
Why does Test-NetConnection succeed but I still cannot connect?
A successful Test-NetConnection means the TCP port is open. It does not guarantee that the Unturned server process is healthy. The server process may be running but stuck in a state where it cannot accept new connections (deadlocked, waiting on a slow disk read, mid-restart). It can also mean the server is full, password-protected, or whitelist-only. If the port is open but the connection fails, see Server Connection Timeout for connection-time troubleshooting.
Can I test UDP ports with Test-NetConnection?
PowerShell's Test-NetConnection only tests TCP ports. UDP is connectionless and cannot be tested in the same way. The Steam query port (27015) is usually TCP and is the recommended port to test for an up/down check. The game port (27016) is UDP and cannot be confirmed open with PowerShell alone. A test of the query port is a strong proxy for the server's overall reachability.
What ports does Unturned use?
The default ports are 27015 (Steam query, TCP), 27016 (game protocol, UDP), and 27017 (RCON, TCP, if the operator has enabled it). Operators frequently change the ports, so the published port from the operator overrides the defaults.
Does VPN affect my ability to see servers in the browser?
Yes. A VPN routes your traffic through a different network. The Steam master server may return a different set of servers depending on the routing. Some operators block VPN connections at the firewall, so a VPN can make a server reachable when it was not, or unreachable when it was. If you are diagnosing connectivity, disable the VPN for the duration of the diagnostic.
Why are some servers showing 9999 ms ping in the browser?
A ping of 9999 ms means the browser could not get a reliable ping measurement from the server. The cause is usually that the server's query interface did not respond in time. The server may still be reachable for actual gameplay; the ping value is unreliable in this case. Try connecting and observe the actual latency in-game.
What does it mean when a server says "Connection refused"?
"Connection refused" means the server is up and reachable, but is actively rejecting your connection. The most common causes are: the server is full, the server has a password and you have not supplied it, the server has a whitelist and your Steam ID is not on it, or the server has banned your Steam ID. The server may report a more specific reason in the connection dialog.
Should I use the in-game browser or a third-party server list to find servers?
Both have advantages. The in-game browser is integrated with Steam and is the fastest way to find currently active servers. Third-party server lists often have better filtering (by game mode, mod set, region) and historical uptime data. For finding new servers, third-party lists are often preferable; for joining a known server, the in-game browser is faster.
Can a server be online but invisible to me specifically?
Yes. Two common cases. First, Steam's master server occasionally returns a different subset of servers to different players, especially under load; refreshing usually fixes this. Second, some servers configure themselves to be invisible in the browser and require direct-connect; this is intentional on the operator's side. Direct-connect always works regardless of browser visibility.
Appendix A: Cause-and-remedy reference
The table below collects the principal "server appears unavailable" causes and their corresponding remedies. The remedies are presented in roughly increasing order of effort.
| Cause | Symptom | Remedy |
|---|---|---|
| Browser query failed | No servers in browser | Refresh the browser |
| Server registration lag | Server missing from browser shortly after restart | Wait 1-3 minutes and refresh |
| Server full | Connection refused with "full" error | Wait or find another server |
| Server password-protected | Connection refused asking for password | Obtain password from operator |
| Server whitelist | Connection refused with "not whitelisted" error | Contact operator for whitelist addition |
| Steam matchmaking outage | Many or all servers missing from browser | Wait for Steam to recover |
| EAC outage | Server appears up but EAC handshake fails | Wait for EAC to recover |
| Local firewall blocking outgoing | Connection times out from your machine specifically | Add Unturned.exe exception in firewall |
| VPN routing problem | Connection works without VPN, fails with VPN | Disconnect VPN or switch VPN region |
| ISP routing problem | tracert shows broken path in your ISP | Contact ISP or wait |
| Server's ISP routing problem | tracert shows broken path near destination | Wait for the path to recover |
| Server process crashed | Host is up (ping), server port closed | Operator must restart server |
| Server host powered off | Ping fails entirely | Operator must restore host |
| Server's region geo-blocked | Server requires connection from specific region | Use a VPN to connect from the required region |
| Server banned your Steam ID | Connection refused with "banned" error | Appeal to operator |
The cohort's recommended workflow is to identify the cause from the diagnostic steps, then apply the corresponding remedy. Each remedy is independent; applying the wrong remedy does not make the situation worse, but does not help either.
Appendix B: Diagnostic command reference
The table below documents every diagnostic command referenced in the article, with its full PowerShell invocation and the principal output to examine.
| Command | Full invocation | Output to examine |
|---|---|---|
| TCP port test | Test-NetConnection -ComputerName <ip> -Port <port> | TcpTestSucceeded |
| ICMP ping | ping <ip> | Reply times, packet loss |
| Trace route | tracert <ip> | Last responding hop |
| DNS resolution | Resolve-DnsName <hostname> | IPv4 address |
| Network configuration | Get-NetIPConfiguration | IPv4Address, DefaultGateway |
| Network adapter status | Get-NetAdapter | Status (Up/Down) |
| Active connections | Get-NetTCPConnection | Where-Object State -eq Established | RemoteAddress, RemotePort |
| Local firewall rules | Get-NetFirewallRule -DisplayName "*Unturned*" | Enabled, Action |
| Routing table | Get-NetRoute | NextHop, InterfaceAlias |
The commands are presented in roughly the order a cohort-validated diagnostic would invoke them. The full diagnostic is presented in the worked example earlier in this article.
Appendix C: Escalation paths
When the diagnostic steps in this article do not produce a clear answer, the cohort-validated escalation path is below.
Player-side escalation
If the diagnostic steps indicate the problem is on your side of the network:
- Confirm your internet is working (
ping 8.8.8.8). - Confirm Steam itself is up (Steam status pages).
- Confirm your local firewall is not blocking Unturned (firewall rule check).
- Disable any VPN and retry.
- Restart your home router and retry.
- Contact your ISP if the problem persists across multiple servers and multiple games.
Server-side escalation
If the diagnostic steps indicate the problem is on the server's side:
- Contact the server's operator through the operator's published contact channel (Discord, web forum, etc.).
- Report the server's name, IP, the time of the attempted connection, and the results of
Test-NetConnectionandtracert. - If the operator does not respond and the server is missing from the browser, the operator may not be aware. Many server outages persist for hours because the operator was not online to notice.
- If the server is operated by a known community and has a Discord, post in the Discord's support channel.
Platform-side escalation
If the diagnostic steps indicate the problem is at Steam, EAC, or another platform:
- Confirm the platform's status on its official status page or a community-tracked status site.
- Wait for the platform to recover; players cannot fix platform outages.
- For prolonged outages, follow the platform's official communication channels (Steam Twitter, EAC status page) for updates.
The escalation paths reflect the cohort's experience that approximately 60 percent of "is the server up?" reports are player-side, 35 percent are server-side, and 5 percent are platform-side. The distribution informs the order of the diagnostic steps in the article.
Best practices
- Run the in-game browser refresh first; many "server is down" reports resolve with a single refresh.
- Verify your own internet before concluding any server is unreachable.
- Use direct-connect by IP as a sanity check whenever a server is missing from the browser.
- Use
Test-NetConnectionfor definitive port reachability when in-game methods are inconclusive. - Have the server's IP and port handy. The most useful single piece of information when troubleshooting is the IP, not the server name.
- Keep a record of servers you play on regularly so you can direct-connect when the browser is misbehaving.
- When notifying an operator that the server is down, include the diagnostic results, not just "the server is down."
- Disable VPNs for the duration of any connectivity diagnostic.
Closing notes
"Is the server up?" looks like a simple question. The honest answer requires distinguishing between half a dozen different ways a server can be unavailable. The diagnostic steps in this article are designed to identify which of those ways applies in any given case. With the in-game browser, direct-connect, Test-NetConnection, ping, and tracert, the player can almost always determine the server's actual state within 5 minutes.
Players who internalize the diagnostic flowchart and the state-diagnosis matrix can usually identify the cause of an unavailable server faster than waiting for the operator to respond. The diagnostic information also makes the operator's job easier when the issue is server-side; a report that includes "Test-NetConnection on port 27015 fails, ping to host succeeds" is far more useful than "the server is down."
Cross-references
- Where Did My File Go? — the previous article in the wiki, covering file-recovery workflows that may be useful when troubleshooting related to a corrupted Unturned installation.
- Why Is the Server Down? — the next article in the wiki, covering operator-side reasons a server might be offline.
- Server Connection Timeout — the article after that, covering timeout-specific troubleshooting when the server is up but connection still fails.
- Unable to Connect to the Server — for general connection failures that do not fit the timeout pattern.
- Recommended Server Hardware — for operators reading from the host-side perspective.
- Setting Up Your Server Panel — for operators using a control panel to monitor server status directly.
Document history
| Version | Date | Notes |
|---|---|---|
| 1.0 | 2024-06-14 | Initial publication. Five diagnostic steps. |
| 1.1 | 2024-09-22 | Added PowerShell command reference and state-diagnosis matrix. |
| 1.2 | 2025-01-09 | Added the five-states framework and the worked diagnostic example. |
| 2.0 | 2025-05-17 | Major revision. Added third-party server-list guidance, escalation paths, and the cause-and-remedy reference appendix. |
Glossary
- Steam master server — Steam's central service that maintains the list of registered game servers. The in-game server browser queries the master server.
- Direct connect — connecting to a server by entering its IP address and port directly, bypassing the server browser.
- Query port — the port used by Steam to query a server's status (default 27015, TCP).
- Game port — the port used by the game client to connect to the server for gameplay (default 27016, UDP for Unturned).
- RCON — Remote Console, a TCP protocol for administrative commands to a server (default 27017).
- EAC — Easy Anti-Cheat, a third-party anti-cheat service used by many Unturned servers.
- ICMP — Internet Control Message Protocol; the protocol used by ping. Often filtered by firewalls.
- TCP — Transmission Control Protocol; the connection-oriented transport that the Steam query interface uses.
- UDP — User Datagram Protocol; the connectionless transport that the Unturned game protocol uses.
- Whitelist — a list of Steam IDs allowed to connect to a server. Connections from IDs not on the list are refused.
- Tracert / traceroute — a diagnostic tool that shows the network path between two hosts.
Appendix D: Worked diagnostic walkthroughs
The walkthroughs below illustrate the diagnostic process for several common scenarios. Each walkthrough shows the symptom, the diagnostic steps taken, the conclusion, and the action.
Walkthrough 1: Server missing from browser, friend on server
Symptom: The server does not appear in the in-game browser, but a friend on Steam shows as playing on the server.
Diagnostic:
powershell
# Step 1: Refresh the in-game browser. Server still missing.
# Step 2: Check History tab. Server not in history (never connected).
# Step 3: Friend's tooltip shows server IP 203.0.113.42:27015.
# Step 4: Test the port.
PS> Test-NetConnection -ComputerName 203.0.113.42 -Port 27015
TcpTestSucceeded : True
# Port is open; server is reachable.
# Step 5: Try direct-connect by IP using the friend's tooltip information.
# Direct connect succeeds; the player joins the server.Conclusion: The server is up but is not currently registered with Steam's master server, which is why it does not appear in the browser. Direct connect bypasses the master server.
Action: Use the server consistently via direct connect; add to Favorites for convenience. Notify the operator that the server is missing from the browser; the operator's fix is typically a server restart.
Walkthrough 2: Multiple servers all missing from browser
Symptom: The in-game browser shows zero or very few servers, including servers that have been online consistently.
Diagnostic:
powershell
# Step 1: Refresh the browser. Still few servers.
# Step 2: Check own internet.
PS> ping 8.8.8.8
Reply from 8.8.8.8: bytes=32 time=18ms TTL=58
# Internet is fine.
# Step 3: Open a web browser, check Steam Community at steamcommunity.com.
# Page loads slowly and intermittently.
# This indicates Steam is having problems.
# Step 4: Search for "Steam status" to confirm.
# Steam status pages report a matchmaking outage.Conclusion: Steam matchmaking is degraded, affecting the in-game browser globally.
Action: Wait for Steam to recover. Direct-connect by IP can bypass the matchmaking outage for known servers.
Walkthrough 3: Server appears full but friend says they have plenty of space
Symptom: The browser shows the server as full (max players occupied), but a friend on the server reports the server is half-empty.
Diagnostic:
powershell
# Step 1: Refresh the browser. Still shows full.
# Step 2: Friend confirms via in-game player count that the server has 30 of 50 players.
# Step 3: The browser's player count is stale.
# Step 4: Try direct-connect anyway.
# Direct connect succeeds; player count is 30, not 50.Conclusion: The browser is showing stale data. The browser caches counts and updates them on a delayed schedule.
Action: Direct-connect when the browser shows stale data. The browser will catch up within a few minutes.
Walkthrough 4: Specific server unreachable, others work
Symptom: One specific server consistently appears down to you, but other Unturned servers connect fine.
Diagnostic:
powershell
# Step 1: Confirm own internet.
PS> ping 8.8.8.8
# Reply OK.
# Step 2: Other Unturned servers connect fine. The issue is specific to this server.
# Step 3: Ping the specific server.
PS> ping 198.51.100.10
# Request timed out (repeated).
# Step 4: Trace the route.
PS> tracert 198.51.100.10
# Trace fails at hop 8, an intermediate router in a third-party network.
# Step 5: Ask a friend in a different ISP region to test the server.
# Friend reports the server is reachable from their network.Conclusion: A routing issue between your ISP and the server's ISP is blocking your traffic. The server is up; your route to it is broken.
Action: Wait for the routing issue to resolve (typically hours, occasionally days). A VPN that exits in a different region can sometimes route around the issue.
Appendix E: Region-specific considerations
Unturned has servers in many regions. Player-to-server routing varies by region in ways that affect the diagnostic interpretation.
| Region pairing | Typical latency | Common routing issues |
|---|---|---|
| Same country | 10-50 ms | Rare; usually direct routing |
| Same continent | 50-150 ms | Occasional transit-provider issues |
| Cross-Atlantic | 80-180 ms | Specific submarine cable issues |
| Cross-Pacific | 120-250 ms | Submarine cable congestion in peak hours |
| Through major exchange | Varies | Exchange congestion under load |
Latency over 300 ms is unplayable for most Unturned game modes. If diagnostics show high latency to a specific server, the cause is geographic distance plus routing, and there is no fix on the client side other than choosing a closer server.
The cohort recommendation is to prefer servers within your continental region. Cross-continental play is feasible for low-tick game modes but produces a noticeably degraded experience.
Appendix F: Common false-positive outage reports
The list below documents common situations that look like server outages but are not.
| Apparent symptom | Actual cause | How to recognize |
|---|---|---|
| Server missing from browser briefly after restart | Master server registration lag | Server appears within 1-3 minutes |
| Browser shows zero servers | Steam matchmaking degraded | Other browser features also slow |
| Connection refused | Server full or whitelisted | Specific error message identifies the cause |
| Connection times out | Local firewall or VPN | Other Unturned servers also fail |
| Connection fails after partial progress | EAC outage | Specific to EAC-enabled servers |
| Player count appears frozen | Browser cache delay | Refreshes after a few minutes |
| Server appears in browser but join hangs | Server overloaded | High player count and high ping |
| Server appears in browser but join fails with version error | Game update available | Update Unturned via Steam |
The cohort survey identifies that approximately 40 percent of "server is down" reports turn out to be one of the false-positive categories above. The diagnostic in this article is designed to identify the false positives quickly so the player can take the appropriate action rather than waiting for a fix that does not exist.
Next steps
If the diagnostic steps in this article indicate the server is offline (not just unreachable from your network), continue to Why Is the Server Down? for the operator-side perspective. If the server appears to be up but you cannot connect, see Server Connection Timeout for timeout-specific troubleshooting. Return to the section overview at Troubleshooting for a list of all articles in this section.