Repository navigation
Region Radar
Region Radar shows where Roblox servers are, and offers a manual way to join a server in a different region.
It does not measure latency. Every region shows "Latency unavailable — not measured". This is honest, not broken — see Platform-Limits.
| Region | Status |
|---|---|
| US East | Latency unavailable — not measured |
| US West | Latency unavailable — not measured |
| Frankfurt | Latency unavailable — not measured |
| Singapore | Latency unavailable — not measured |
| Tokyo | Latency unavailable — not measured |
Additional honest notes:
- US East and US West cannot be distinguished by the available country-level discovery source. Country data does not identify a specific region.
- Country information cannot prove a city. A result reporting Frankfurt is not proof the server is in Frankfurt.
Roblox publishes no region-specific probe endpoint that a launcher can safely query. Fabricating a ping figure would be worse than useless — it would look actionable and be wrong. So GokuTrap shows nothing rather than showing something invented.
Refresh availability re-queries discovery. If no public place has been observed recently, the page says:
"No recently observed public place. Join an experience with activity tracking enabled, then try again."
This is because discovery needs to know which place you want a server for. See Integrations#Activity tracking.
The supported alternative to latency measurement.
-
GokuTrap cross-checks discovered server IDs against Roblox's own public server list for the observed place. A candidate is only accepted if Roblox's API confirms it.
-
Server IDs are GUID-formatted, matching what Roblox's API returns.
-
You are shown a confirmation that states plainly what the data does and does not prove:
"Leave your current session and request the discovered server for {place}? Discovery reports country {country}, NOT a verified city or region."
-
Only after you confirm does GokuTrap re-verify the place context and then hand off to Roblox's official join.
| Can | Cannot |
|---|---|
| Find a public server with spare capacity in the place you are in | Prove which city or datacenter it is in |
| Report the country the server reports | Distinguish US East from US West |
| Hand off to Roblox's official join flow | Guarantee the join succeeds — Roblox decides that |
| Message | Meaning |
|---|---|
| "Country candidate cross-checked against Roblox's public server list. Confirmation required." | A candidate was verified and is awaiting your confirmation |
| "No matching public server with capacity was verified in the first 100 discoverable Roblox servers." | Nothing suitable was found. Your current session was not changed |
| "Official Roblox join handoff requested. This does not guarantee join success or city location." | The handoff happened; the outcome is Roblox's |
| "Discovery unavailable or cancelled. Your current session was not changed." | Nothing was altered |
Discovery only examines the first 100 public servers Roblox's API returns. This is not an exhaustive search.
There is a 30 second cooldown between server searches, and each individual request has a 10 second timeout. Exceeding the cooldown reports:
"Please wait 30 seconds between server searches."
- Joining a discovered server leaves your current session. This is why it requires confirmation. Save your work.
- Private servers are never discovered.
- Stale candidates are reported as stale rather than presented as current.
- Integrations#Activity tracking — required for place context
- Platform-Limits — why latency measurement is unavailable
- Feature-Tools-Overview — the shared safety rules