Arcjet’s API minimizes latency by running as close as possible to your application and routing requests based on the lowest latency region.
New regions
We deploy regions based on demand, so if you need a region that isn’t listed below, let us know. We can usually deploy to a new region within a few days.
Current regions
The API is currently deployed to the following regions:
AWS
| Location | Region Code |
|---|
| Northern Virginia, USA | us-east-1 |
| Ohio, USA | us-east-2 |
| Northern California, USA | us-west-1 |
| Oregon, USA | us-west-2 |
| Singapore | ap-southeast-1 |
| Sydney, Australia | ap-southeast-2 |
| Canada (Central) | ca-central-1 |
| Dublin, Ireland | eu-west-1 |
| London, UK | eu-west-2 |
| Frankfurt, Germany | eu-central-1 |
| São Paulo, Brazil | sa-east-1 |
Fly.io
| Location | Region Code |
|---|
| Amsterdam, Netherlands | ams |
| Ashburn, USA | iad |
| Frankfurt, Germany | fra |
| Hong Kong | hkg |
| London, UK | lhr |
| Montreal, Canada | yul |
| Secaucus, NJ (US) | ewr |
| San Jose, California (US) | sjc |
| Singapore | sin |
| Toronto, Canada | yyz |
Render
| Location |
|---|
| Oregon, USA |
| Ohio, USA |
| Virginia, USA |
| Frankfurt, Germany |
| Singapore |
Vercel
| Location | Region Code |
|---|
| Cleveland, USA | cle1 |
| Dublin, Ireland | dub1 |
| London, UK | lon1 |
| Frankfurt, Germany | fra1 |
| São Paulo, Brazil | gru1 |
| Washington, D.C., USA | iad1 |
| Portland, USA | pdx1 |
| San Francisco, USA | sfo1 |
| Singapore | sin1 |
| Sydney, Australia | syd1 |
Discussion
