Regions & endpoints
Landed runs in five regions. Connect directly to whichever is closest to your infrastructure, or run against more than one for redundancy.
Use a production API key from the Console with these regional endpoints.
| Region | Location | Endpoint |
|---|---|---|
| HKG | Hong Kong | https://hkg.rpc.landed.sarl |
| FRA | Frankfurt, Germany | https://fra.rpc.landed.sarl |
| NYC | New York, USA | https://nyc.rpc.landed.sarl |
| TYO | Tokyo, Japan | https://tyo.rpc.landed.sarl |
| SGP | Singapore | https://sgp.rpc.landed.sarl |
Each endpoint accepts both HTTP (https://) JSON-RPC requests and WebSocket (wss://) subscriptions.
Choosing a region
Pick the region nearest to where your requests originate. Each endpoint is a direct connection to that region's infrastructure, with no automatic cross-region routing, so latency is whatever the network path to that region actually is.
Failover
Choose and manage fallback regions in your application. Landed does not automatically route an endpoint to a different region.