Server Triage Checks
| Check | What it tells you | Next step |
|---|---|---|
| Status | Unknown. No official real-time server status signal is available from the checked sources. | Do not infer Online from the absence of a maintenance announcement. |
| Official news | Steam News and the Steam News API support announcement checks such as updates or maintenance notices. | Use them for notices, not live health. |
| Local troubleshooting | tinyBuild support helps with local restart, file, firewall, NAT, VPN, and client checks. | Use it to test your setup, not to label global server status. |
| Community reports | Steam Discussions and Reddit can show symptom volume, but they are not official status endpoints. | Compare exact symptoms and timing before reporting. |
Server Status Starts With Symptoms
Players want to know whether a connection issue is global or local.
Global Outage Or Local Blocker
A server check that only says "check back later" is not enough. Players need a triage chain: official source, report volume, local checks, retry timing, and report path.
The Same Error Can Have Different Causes
Server symptoms can come from maintenance, launch load, patch mismatch, NAT, local connection, Steam outage, firewall, BattlEye, or anti-cheat startup. The same symptom does not always have the same cause.
Check Reports Before Changing Settings
Use the order: official update, community report volume, Steam restart, game restart, file verification, firewall check, same-platform friend test, then support report with timestamp and exact symptom.
- Check Steam News for maintenance or patch notes.
- Check Steam Discussions and Reddit for many fresh reports before calling it global.
- Restart Steam and the game, then test a second route or mode.
- Verify files if the failure began after an update or rollback.
- Check firewall, NAT, VPN, and same-platform friend status if only your machine fails.
- Move to black-screen or Linux/Steam Deck troubleshooting when the symptom is launch, graphics, or BattlEye rather than matchmaking.
Server Status Misreads
- Calling a local firewall problem a server outage.
- Ignoring patch mismatch after an update.
- Refreshing repeatedly before checking official updates or fresh community reports.
- Using one Reddit comment as proof of a full outage.
- Changing graphics settings when the real symptom is party or queue failure.
- Reporting "servers down" without region, time, mode, error text, and platform.
What To Include In A Useful Report
- Exact time and region.
- Platform and store: Steam, Xbox, PlayStation, Deck, or Linux.
- Mode or step: launch, login, party, matchmaking, route, extraction, or return to base.
- Error text or what the UI did instead.
- Whether Steam restart, file verification, firewall/VPN test, and same-platform friend test changed anything.
Why The Status Remains Unknown
The checked official sources returned pages and news data on July 14, 2026, but they did not provide a real-time server-health endpoint.
Because of that boundary, this page keeps the status Unknown instead of calling the service Online.
SAND Servers Symptoms To Compare
SAND servers can look broken when the real problem is patch mismatch, firewall, NAT, local files, or a platform outage. Use the SAND server status check to separate those cases before changing settings.
Use SAND servers reports as symptom evidence, not as proof by themselves. A good SAND server status check compares official updates, fresh report volume, same-platform friends, and one local restart or file verification.
- Check SAND servers reports before changing graphics or launch settings.
- Use SAND server status after a patch when login, matchmaking, or extraction fails for many players.
- Do not call SAND servers down from one comment if same-platform friends can play.
- Keep SAND server status notes current because live-service symptoms can change hour by hour.
- Use SAND servers checks again when a same-platform friend sees a different login or matchmaking result.
- Repeat the SAND servers check after restarting Steam so local client state and live status are not mixed together.
- Check SAND servers again before reinstalling, because local fixes do not help during a broad outage.
- Use SAND servers notes to separate login trouble from route or extraction bugs.
Sources and Version Notes
Verified July 14, 2026. Store price, platform status, server health, player-count snapshots, database stats, and build advice can change after patches.
FAQ
How do I know if SAND servers are down?
This page cannot label SAND available or down because no official real-time server status signal is available. Check official news for announcements, then compare fresh report volume and local tests.
Can a patch make matchmaking fail?
Yes. Maintenance, rollback, version mismatch, or update timing can make queue and login symptoms look like a server outage.
What if only I cannot connect?
Restart Steam and the game, verify files, check firewall/NAT/VPN, and test with a same-platform friend before reporting a global outage.