> ## 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.

# Regions & Locations

export const SiteFeatureAvailability = ({src = 'https://www.latitude.sh/dashboard/api/public/site-features'}) => {
  const [features, setFeatures] = useState(null);
  const [failed, setFailed] = useState(false);
  useEffect(() => {
    fetch(src).then(response => response.ok ? response.json() : Promise.reject(response)).then(body => setFeatures(body.data || [])).catch(() => setFailed(true));
  }, [src]);
  if (failed) return <p>Feature availability is temporarily unavailable. Please try again later.</p>;
  if (!features) return <p>Loading feature availability.</p>;
  if (features.length === 0) return <p>All features are currently available in every location.</p>;
  return <table>
      <thead>
        <tr>
          <th style={{
    textAlign: 'left'
  }}>Feature</th>
          <th style={{
    textAlign: 'left'
  }}>Locations</th>
        </tr>
      </thead>
      <tbody>
        {features.map(feature => <tr key={feature.id}>
            <td>
              {feature.docsPath ? <a href={feature.docsPath}>{feature.label}</a> : feature.label}
            </td>
            <td>{feature.locations.join(', ')}</td>
          </tr>)}
      </tbody>
    </table>;
};

On the [Latitude.sh dashboard](https://www.latitude.sh/dashboard) and [API](https://www.latitude.sh/docs/api-reference/summary), 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](https://www.latitude.sh/locations) to view all locations available.

## 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 <br /> Frankfurt 2 | Shared network | Servers can communicate via private networking across both locations |
| Sydney | Sydney <br /> Sydney 2 | Shared network | Servers can communicate via private networking across both locations |
| Tokyo | Tokyo <br /> Tokyo 4 | Shared network | Servers can communicate via private networking across both locations |
| Ashburn | Ashburn <br /> Ashburn 2 | Shared network | Servers can communicate via private networking across both locations |
| Silicon Valley | Silicon Valley <br /> Silicon Valley 2 | Shared network | Servers can communicate via private networking across both locations |
| Brazil | São Paulo <br /> São Paulo 2 | Isolated networks | Each location has its own independent network |
| London | London <br /> London 2 | Isolated networks | Each location has its own independent network |
| Los Angeles | Los Angeles <br /> Los Angeles 2 | Isolated networks | Each location has its own independent network |

<Note>
  When creating a [private network](/docs/networking/private-networks) 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.
</Note>

## Feature availability by location

Some features are enabled per location while they roll out. The table lists the features that are currently available in a subset of locations.

<SiteFeatureAvailability />


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.