London
United Kingdom
ukAdios global CDN
Adios edges receive traffic, check security rules, serve eligible cached responses, and route other requests to healthy app replicas. The map shows ingress locations, not where your app compute or data is placed.
206.206.80.80Network snapshot
Live36.4 ms
Observed average ping outside China
159 Ping.pe probes · October 23, 2026 snapshot
Map
Explore an example path from a user to an edge and then to an app worker. Green dots mark live edges.
Example request path
User to edge to app worker
Live
These ingress locations are live and receive Adios traffic now. They do not imply that app compute or customer data runs in every listed city. The code is the short name used for each edge.
United Kingdom
ukFrance
frNetherlands
nlSpain
esGermany
deUnited States
laUnited States
miUnited States
njBrazil
brJapan
jpSingapore
sgUnited States
svIndia
mbUnited States
ordAustralia
sySouth Africa
jo| Location | Area | Code |
|---|---|---|
| London, United Kingdom | Europe | uk |
| Paris, France | Europe | fr |
| Amsterdam, Netherlands | Europe | nl |
| Madrid, Spain | Europe | es |
| Frankfurt, Germany | Europe | de |
| Los Angeles, United States | North America | la |
| Miami, United States | North America | mi |
| New Jersey, United States | North America | nj |
| São Paulo, Brazil | South America | br |
| Tokyo, Japan | Asia Pacific | jp |
| Singapore, Singapore | Asia Pacific | sg |
| Silicon Valley, United States | North America | sv |
| Mumbai, India | Asia Pacific | mb |
| Chicago, United States | North America | ord |
| Sydney, Australia | Asia Pacific | sy |
| Johannesburg, South Africa | Africa | jo |
How it works
The request reaches an available Adios edge. The edge ends the secure TLS connection and reads the requested domain and path.
The edge checks access rules and the web firewall. It can block common web attacks or traffic from disallowed countries. Bot and abuse checks can also block suspicious requests or show a CAPTCHA before the request reaches your app.
The edge checks for a fresh cached response. If it finds one, it returns the content to the user without contacting a worker.
If the content is not cached, the request travels to a worker through the internal WireGuard VPN. Some internal connections also use mutual TLS (mTLS), so both sides verify each other.
The worker sends the request to a healthy copy of the app and returns the response through the edge. Eligible responses can be saved in the CDN cache for later requests.
Limits and placement
No. The listed locations are edge ingress points. Application compute and data placement are separate decisions and may run in different regions.
No. The edge can serve eligible fresh cached responses. Other requests continue across the platform network to a healthy app replica.
Use the Ping.pe link on this page to test 206.206.80.80 from multiple locations. Results describe the public endpoint, not the latency of every application and data path.
Start from a template or bring an existing repository, then verify the generated route and current release.