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.
Adios global CDN
Fast delivery, built into every deploy.
The Adios CDN serves cached content near your users and routes live requests through 13 edge locations worldwide. Your app loads faster and stays available, with no extra CDN to configure or maintain.
Test on Globalping
206.206.80.8013
Current
15
Planned
Map
Current and planned edge locations
Follow requests from users around the world to a nearby edge and then to an app worker. Green dots are current edges. White dots are planned locations.
Live request path
User to nearest edge to app worker
User Edge WorkerPlanned
Map data: Natural EarthToronto, CanadaNew Jersey, United States edgeNew Jersey, United States workerThis example moves around the world automatically. Your app settings control the real worker.
Current
Edge locations
These locations are live and receive Adios traffic now. The code is the short name we use for each location.
| Location | Area | Code | Status |
|---|---|---|---|
| London, United Kingdom | Europe | uk | Current |
| Paris, France | Europe | fr | Current |
| Amsterdam, Netherlands | Europe | nl | Current |
| Madrid, Spain | Europe | es | Current |
| Frankfurt, Germany | Europe | de | Current |
| Los Angeles, United States | North America | la | Current |
| Miami, United States | North America | mi | Current |
| New Jersey, United States | North America | nj | Current |
| São Paulo, Brazil | South America | br | Current |
| Tokyo, Japan | Asia Pacific | jp | Current |
| Singapore, Singapore | Asia Pacific | sg | Current |
| Silicon Valley, United States | North America | sv | Current |
| Mumbai, India | Asia Pacific | mb | Current |
Coming next
Planned locations
We plan to add these locations. They are not live yet. The list and launch order may change.
| Location | Area | Code | Status |
|---|---|---|---|
| Dallas, United States | North America | TBD | Planned |
| Oslo, Norway | Europe | TBD | Planned |
| Sydney, Australia | Asia Pacific | TBD | Planned |
| Hong Kong, Hong Kong | Asia Pacific | TBD | Planned |
| Chicago, United States | North America | TBD | Planned |
| Phoenix, United States | North America | TBD | Planned |
| Mexico City, Mexico | North America | TBD | Planned |
| Tel Aviv, Israel | Middle East | TBD | Planned |
| Dubai, United Arab Emirates | Middle East | TBD | Planned |
| Dublin, Ireland | Europe | TBD | Planned |
| Honolulu, United States | North America | TBD | Planned |
| Auckland, New Zealand | Asia Pacific | TBD | Planned |
| Kathmandu, Nepal | Asia Pacific | TBD | Planned |
| Istanbul, Turkey | Europe | TBD | Planned |
| Johannesburg, South Africa | Africa | TBD | Planned |
How it works
How the Adios CDN handles a request
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.
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.
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.
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.
Run your app on Adios.
Start from a template or bring an existing repository.