Hi Creators,
Starting today, you can read the geographic region of your live game servers using the new game.ServerRegion property. You can now build accurate regional telemetry, schedule in-game events based on local time zones, and more. This gives you native access to location data and removes the need for unreliable third-party IP-geolocation services.
How to Access Server Regions
You can access this location data across the engine, the Creator Hub, and the Open Cloud API.
- Read the property in your server-side scripts. It populates at startup for live game servers.
if RunService:IsServer() and game.ServerRegion ~= "" then print("Server Region: ", game.ServerRegion) end
- View regions manually in the Creator Hub. Go to Creations > your game > Server Management to see the region listed for both live and terminated servers.
- Filter and sort by region using the Open Cloud API for server management.
Format
In the engine, Creator Hub, and OpenCloud, the Server Region is a three-letter uppercase IATA airport code, like “IAD” or “SYD” – this designates the “Nearest Airport” to the data center hosting the Server. The property is strictly server-side and fully additive. This will not be populated on any Clients.
What’s Next
ROBLOX rolled this out to all live servers now. We’ll continue to support the property as we expand to new data centers.
Resources
* Engine - ServerRegion: Documentation
Let ROBLOX know if you have any questions or feedback. Thank you.
FAQs
Do I need to delete my existing HttpService workarounds?
- No action is immediately required. Your existing IP-geolocation scripts will continue to function exactly as they do today, but we recommend migrating to game.ServerRegion to improve accuracy and reduce external dependencies, since we’ve noticed these locators may not always be accurate.
What does the property return in clients and in Studio?
- The property returns an empty string in Studio, in play-solo, and on client scripts.
What are the region codes?
- The property returns uppercase IATA airport codes, such as “LAX” or “LHR”. We use string codes rather than enums so we can add new regions continuously over time.
