On the Latitude.sh dashboard and API, you’ll see both Regions and Locations: • Region: A geographic area, usually a country, where Latitude.sh operates. Examples include the United States, Brazil, Netherlands, and the United Kingdom. • Location: A specific data center within a region, typically a city. If there are multiple data centers in the same city, they are labeled sequentially, e.g., Miami and Miami 2. Available locations include cities like Dallas, Miami, São Paulo, Amsterdam, and London. Go to the Locations page to view all locations available.Documentation Index
Fetch the complete documentation index at: https://www.latitude.sh/docs/llms.txt
Use this file to discover all available pages before exploring further.
Network connectivity between locations
Some cities have multiple data centers that share a network infrastructure, allowing servers to communicate directly across locations. Other cities have data centers on isolated networks where cross-location communication isn’t possible.Network sharing between city locations
| Region | Locations | Network Status | Notes |
|---|---|---|---|
| Frankfurt | Frankfurt Frankfurt 2 | Shared network | Servers can communicate via private networking across both locations |
| Sydney | Sydney Sydney 2 | Shared network | Servers can communicate via private networking across both locations |
| Tokyo | Tokyo Tokyo 4 | Shared network | Servers can communicate via private networking across both locations |
| Brazil | São Paulo São Paulo 2 | Isolated networks | Each location has its own independent network |
| London | London London 2 | Isolated networks | Each location has its own independent network |
| Los Angeles | Los Angeles Los Angeles 2 | Isolated networks | Each location has its own independent network |
When creating a private network between
servers, you must ensure they are in the same location if the locations do not
share a network. Only servers within the same network can communicate through
private networking.