- Home
- Anycast network
Anycast network
65 PoPs, one set of addresses
ShieldNS name servers share the same anycast IP addresses at every point of presence. Internet routing delivers each query to the nearest healthy location, so answers come back fast and outages stay local.
Select a region to list its locations.
Locations
Where we answer from
65 points of presence in 52 cities. Cities marked ×2 or ×3 run more than one PoP. Median response times are measured from probes inside each region to the nearest ShieldNS location.
North America24 PoPs
- MontrealYUL · 6 ms
- TorontoYYZ ×2 · 6 ms
- BuffaloBUF · 11 ms
- New JerseyEWR · 7 ms
- AshburnIAD ×2 · 8 ms
- AtlantaATL · 10 ms
- MiamiMIA · 7 ms
- ChicagoORD ×2 · 7 ms
- Kansas CityMCI · 9 ms
- DallasDFW ×2 · 8 ms
- DenverDEN · 10 ms
- Salt Lake CitySLC · 6 ms
- PhoenixPHX · 11 ms
- Los AngelesLAX ×2 · 10 ms
- Silicon ValleySJC ×2 · 10 ms
- BendRDM · 8 ms
- SeattleSEA ×2 · 9 ms
South America3 PoPs
- São PauloGRU · 18 ms
- Buenos AiresEZE · 16 ms
- SantiagoSCL · 13 ms
Europe23 PoPs
- LondonLHR · 9 ms
- LisbonLIS · 5 ms
- MadridMAD · 6 ms
- ParisCDG · 6 ms
- AmsterdamAMS ×3 · 8 ms
- FrankfurtFRA ×2 · 7 ms
- ZurichZRH · 9 ms
- MilanMXP · 4 ms
- SandefjordTRF · 7 ms
- StockholmARN · 8 ms
- ViennaVIE · 9 ms
- WrocławWRO · 4 ms
- WyszkówWYS · 9 ms
- HelsinkiHEL · 6 ms
- TallinnTLL · 7 ms
- BucharestOTP · 7 ms
- SofiaSOF · 4 ms
- KyivKBP · 7 ms
- IstanbulIST · 9 ms
- MoscowSVO · 8 ms
Middle East2 PoPs
- Tel AvivTLV · 10 ms
- RiyadhRUH · 11 ms
Africa1 PoP
- JohannesburgJNB · 15 ms
Asia-Pacific12 PoPs
- MumbaiBOM · 10 ms
- Delhi NCRDEL · 12 ms
- SingaporeSIN ×2 · 12 ms
- Hong KongHKG ×3 · 13 ms
- TaipeiTPE · 10 ms
- TokyoNRT · 15 ms
- SydneySYD · 12 ms
- MelbourneMEL · 12 ms
- AucklandAKL · 11 ms
Network status
All systems operational
The state of resolution in every region. During an incident, this page and our status feed show what is affected and what we are doing about it.
| Region | PoPs | Median | Status |
|---|---|---|---|
| North America | 24 | 9 ms | Operational |
| South America | 3 | 16 ms | Operational |
| Europe | 23 | 7 ms | Operational |
| Middle East | 2 | 12 ms | Operational |
| Africa | 1 | 17 ms | Operational |
| Asia-Pacific | 12 | 13 ms | Operational |
How anycast helps
Shorter paths, smaller blast radius
With unicast DNS, every resolver in the world talks to the same few servers. With anycast, each region talks to its own location.
- Lower latency, because the nearest location answers.
- Local failures stay local: a location that goes down withdraws its route and its traffic moves to the next one.
- Attacks get diluted across many locations instead of hitting one.

Inside a location
What happens to every query
- Legitimate query
- Signed answer
- Attack traffic
Move your DNS to an answer you can trust
Import a zone in minutes, check every answer before you switch, and only then change your name servers.