openstatus.dev
Openstatus
www.openstatus.dev
add regions info in docs (#1731)
authored by
Thibault Le Ouay
and committed by
GitHub
7f70da8c
0200f579
+69
+4
apps/docs/astro.config.mjs
+4
apps/docs/astro.config.mjs
+65
apps/docs/src/content/docs/reference/location.mdx
+65
apps/docs/src/content/docs/reference/location.mdx
···
1
+
---
2
+
title: Location Reference
3
+
description: Complete technical specification for Location monitoring
4
+
---
5
+
6
+
## Overview
7
+
8
+
OpenStatus monitors your endpoints from multiple global locations to ensure accurate uptime and latency reporting. Each monitoring location corresponds to a Fly.io region, with both IPv4 and IPv6 addresses available for each.
9
+
10
+
You can use these locations to:
11
+
- Configure region-specific checks
12
+
- Allowlist monitoring IPs in your firewall
13
+
- Understand where requests originate during synthetic monitoring
14
+
15
+
### Fly.io Regions & Monitoring IPs
16
+
17
+
Below is the complete list of regions used for monitoring, along with their associated IPv4 and IPv6 addresses.
18
+
19
+
| Region Code | Location Name | IPv4 Address | IPv6 Address |
20
+
|-------------|-------------------|-------------------|-------------------------------|
21
+
| ams | Amsterdam | 209.71.64.1 | 2a09:8280:e601:1:0:22:b79b:0 |
22
+
| arn | Stockholm | 209.71.98.189 | 2a09:8280:e602:1:0:22:b79b:0 |
23
+
| bom | Mumbai | 209.71.68.172 | 2a09:8280:e605:1:0:22:b79b:0 |
24
+
| cdg | Paris | 209.71.86.183 | 2a09:8280:e607:1:0:22:b79b:0 |
25
+
| dfw | Dallas | 209.71.71.89 | 2a09:8280:e609:1:0:22:b79b:0 |
26
+
| ewr | Newark | 209.71.69.221 | 2a09:8280:e610:1:0:22:b79b:0 |
27
+
| fra | Frankfurt | 209.71.90.204 | 2a09:8280:e612:1:0:22:b79b:0 |
28
+
| gru | São Paulo | 209.71.94.28 | 2a09:8280:e615:1:0:22:b79b:0 |
29
+
| iad | Washington, D.C. | 209.71.81.6 | 2a09:8280:e618:1:0:22:b79b:0 |
30
+
| jnb | Johannesburg | 209.71.83.120 | 2a09:8280:e620:1:0:22:b79b:0 |
31
+
| lax | Los Angeles | 209.71.91.96 | 2a09:8280:e621:1:0:22:b79b:0 |
32
+
| lhr | London | 209.71.85.82 | 2a09:8280:e622:1:0:22:b79b:0 |
33
+
| nrt | Tokyo | 209.71.88.150 | 2a09:8280:e625:1:0:22:b79b:0 |
34
+
| ord | Chicago | 209.71.89.1 | 2a09:8280:e626:1:0:22:b79b:0 |
35
+
| sin | Singapore | 209.71.80.112 | 2a09:8280:e632:1:0:22:b79b:0 |
36
+
| sjc | San Jose | 209.71.101.37 | 2a09:8280:e633:1:0:22:b79b:0 |
37
+
| syd | Sydney | 209.71.97.108 | 2a09:8280:e634:1:0:22:b79b:0 |
38
+
| yyz | Toronto | 209.71.99.51 | 2a09:8280:e637:1:0:22:b79b:0 |
39
+
40
+
41
+
---
42
+
43
+
## Railway Regions & Monitoring IPs
44
+
45
+
Below is the complete list of Railway regions used for monitoring, along with their associated IPv4 addresses.
46
+
47
+
| Region Code | Location Name | IPv4 Address |
48
+
|--------------------------|------------------|-------------------|
49
+
| europe-west4-drams3a | Europe West | 208.77.244.15 |
50
+
| asia-southeast1-eqsg3a | Asia Southeast | 208.77.246.15 |
51
+
| us-east4-eqdc4a | US East | 162.220.234.15 |
52
+
| us-west2 | US West | 162.220.232.99 |
53
+
54
+
---
55
+
56
+
## Koyeb Regions & Monitoring IPs
57
+
58
+
Koyeb does not provide static IP addresses for their regions. For more information, please refer to Koyeb's [documentation](https://www.koyeb.com/docs/faqs/general#i-want-to-restrict-access-to-a-database-or-other-application-by-ip-address-what-ip-addresses-does-koyeb-use).
59
+
60
+
---
61
+
62
+
**Note:**
63
+
64
+
- Both IPv4 and IPv6 addresses are provided for allowlisting and diagnostics.
65
+
- Location names are for reference and may be used in the dashboard UI.