01
Check whether servers should exist
The August Closed Beta was scheduled only for August 21–23. If you open the Playtest client after that window, an empty list is not evidence of a routing problem. Confirm that the official feed says a test or Early Access build is currently live before touching firewall or router settings.
The next confirmed milestone is Early Access on September 10. No extra test between August 24 and that date was confirmed when this page was checked.
02
Use the official browser fix during a live window
The developer’s pinned known-issues post says the Server Browser must have a single region selected. If more than one region is selected, no servers may appear. Clear all regions, choose one nearby region, and refresh once.
This is a more specific instruction than generic port-forwarding advice and should be tested first whenever the service is live.
03
If one region still returns nothing
- Check the official announcement and Discord status before changing the network.
- Restart Steam and the game once to refresh authentication.
- Remove any stale VPN route for one controlled test only if you understand the privacy tradeoff.
- Do not forward random ports unless the developer publishes a required list.
- Capture the selected region, timestamp, and screenshot before reporting the issue.
04
Empty is different from full
An empty list, a visible full server, a failed queue, and a disconnect after joining are different problems. Report the exact state. During the Closed Beta, BULKHEAD said invites were being staged to analyze server scaling and stability, so capacity and browser behavior could change during the event.
Do not claim a “global outage” from one empty client. Cross-check an official status message or multiple regions first.
05
Sources
These are the primary pages used for the verified facts above. Live game behavior and newer developer notes take priority if they differ.