Global Infrastructure
ngrok runs globally distributed tunnel servers around the world to enable fast, low latency traffic to your applications.
Locations
ngrok runs servers in data centers around the world. The location of the data center within a given region may change without notice (e.g. the European servers may move from Frankfurt to London).
| Region Code | Location |
|---|---|
| ap | Asia/Pacific (Singapore) |
| au | Australia (Sydney) |
| eu | Europe (Frankfurt) |
| in | India (Mumbai) |
| jp | Japan (Tokyo) |
| sa | South America (São Paulo) |
| us | United States (Ohio) |
Usage
If you do not explicitly pick a region when starting the ngrok agent, the agent will attempt to pick the region with the least latency, which is usually the one geographically closest to your machine.
To explicitly choose the region, add the --region flag or set the region property in your configuration file. For example, to start a tunnel in the European region:
ngrok http --region eu 8080
Reserved domains and TCP addresses are allocated for a specific region (the US region by default). When you reserve a domain or TCP address, you must select a target region. You may not bind a domain or TCP address reserved in another region other than the one it was allocated for. Attempting to do so will yield an error and prevent your tunnel session from initializing.
Limitations
An ngrok agent may only be connected a single region, meaning you cannot host tunnels in multiple regions simultaneously with the same agent. You can run multiple ngrok agents if you need to do this.
A domain cannot be reserved for multiple regions at the same time. It is not possible to geo-balance DNS to the same tunnel name in multiple regions. Use region-specific subdomains or TLDs if you need to do this.
An ngrok Edge can only contain endpoints in the same region.