Adios

Adios global CDN

See where Adios traffic enters the network.

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.

Test on Ping.pe 206.206.80.80

Network snapshot

Live
16
Live edges
5
Geographic areas

36.4 ms

Observed average ping outside China

159 Ping.pe probes · October 23, 2026 snapshot

Map

Live edge locations

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

01 / 05
Adios request pathA request from Cape Town enters through the Johannesburg edge and travels to the Frankfurt worker.London, United Kingdom · Live edgeParis, France · Live edgeAmsterdam, Netherlands · Live edgeMadrid, Spain · Live edgeFrankfurt, Germany · Live edgeLos Angeles, United States · Live edgeMiami, United States · Live edgeNew Jersey, United States · Live edgeSão Paulo, Brazil · Live edgeTokyo, Japan · Live edgeSingapore, Singapore · Live edgeSilicon Valley, United States · Live edgeMumbai, India · Live edgeChicago, United States · Live edgeSydney, Australia · Live edgeJohannesburg, South Africa · Live edgeUser · Cape Town, South AfricaWorker · Frankfurt, Germany
User Edge Worker
Map data: Natural Earth
Cape Town, South AfricaJohannesburg, South Africa edgeFrankfurt, Germany workerThis path is illustrative. Internet routing can select a different edge, and your app settings control the real worker.

Live

Edge locations

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.

London

United Kingdom

uk
Europe

Paris

France

fr
Europe

Amsterdam

Netherlands

nl
Europe

Madrid

Spain

es
Europe

Frankfurt

Germany

de
Europe

Los Angeles

United States

la
North America

Miami

United States

mi
North America

New Jersey

United States

nj
North America

São Paulo

Brazil

br
South America

Tokyo

Japan

jp
Asia Pacific

Singapore

Singapore

sg
Asia Pacific

Silicon Valley

United States

sv
North America

Mumbai

India

mb
Asia Pacific

Chicago

United States

ord
North America

Sydney

Australia

sy
Asia Pacific

Johannesburg

South Africa

jo
Africa

How it works

How the Adios CDN handles a request

01

Secure at the edge

The request reaches an available Adios edge. The edge ends the secure TLS connection and reads the requested domain and path.

02

Check security rules

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.

03

Check the CDN cache

The edge checks for a fresh cached response. If it finds one, it returns the content to the user without contacting a worker.

04

Cross the private network

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.

05

Run on the worker

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

What the map does—and does not—promise

Does every edge location run my application or store its data?

No. The listed locations are edge ingress points. Application compute and data placement are separate decisions and may run in different regions.

Does every response get cached at the edge?

No. The edge can serve eligible fresh cached responses. Other requests continue across the platform network to a healthy app replica.

How can I test the public network endpoint?

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.

Put your app behind the Adios edge network.

Start from a template or bring an existing repository, then verify the generated route and current release.

Start free, no card