Gaming & Real-time Video & Streaming E-commerce & Retail Network Pricing Developers FAQ Start free Sign in
Home / Network
Global network

312 points of presence, one anycast address

No traffic-steering DNS games, no regional endpoints for your clients to choose between. You publish one hostname; BGP puts every request into the nearest healthy PoP, and every PoP can cache, compute, package and scrub.

312
Points of presence
18
Regional shield clusters
1,400+
Peering sessions
180 Tbps
Edge capacity
Topology

Two tiers between a player and your origin

Most requests stop at tier one. The design exists so that the rare miss still costs your origin almost nothing.

Client anycast, HTTP/3 Tier 1 · Edge PoP 312 locations · TLS, WAF, cache, edge functions, scrubbing Tier 2 · Regional shield 18 clusters · large NVMe cache, request collapsing Your origin cloud or on-prem 98.7% of requests end here 1.2% 0.1% Measured across all customer traffic, trailing 30 days. Illustrative figures for this design.
Coverage

Where the capacity actually is

PoP counts are easy to inflate by counting cabinets. These are locations with independent transit, local peering and full product capability — cache, compute, media and scrubbing in each one.

North America

74 PoPs

Ashburn, Atlanta, Chicago, Dallas, Denver, Los Angeles, Miami, Montréal, New York, Phoenix, San José, Seattle, Toronto, Querétaro & 60 more.

p95 TTFB 18 ms42 Tbps

Europe

81 PoPs

Amsterdam, Frankfurt, London, Madrid, Marseille, Milan, Paris, Stockholm, Vienna, Warsaw, Zürich & 70 more.

p95 TTFB 21 ms48 Tbps

Asia-Pacific

88 PoPs

Hong Kong, Jakarta, Mumbai, Osaka, Seoul, Singapore, Sydney, Taipei, Tokyo & 79 more, plus licensed mainland China capacity.

p95 TTFB 29 ms54 Tbps

Latin America

34 PoPs

Bogotá, Buenos Aires, Fortaleza, Lima, Rio de Janeiro, Santiago, São Paulo & 27 more.

p95 TTFB 34 ms18 Tbps

Middle East

21 PoPs

Doha, Dubai, Istanbul, Jeddah, Kuwait City, Manama, Muscat, Riyadh, Tel Aviv & 12 more.

p95 TTFB 31 ms11 Tbps

Africa

14 PoPs

Accra, Cairo, Cape Town, Johannesburg, Lagos, Mombasa, Nairobi & 7 more.

p95 TTFB 38 ms7 Tbps

Counts and figures on this page are illustrative placeholders for this design.

Interconnection

Short paths beat fast servers

A PoP in the right city is worth nothing if traffic leaves it through three transit hops to reach the subscriber. We peer directly with the eyeball networks your users are actually on, and we embed caches inside the largest of them.

1,400+ peering sessions across 92 internet exchanges
Embedded caches inside 60+ ISP and mobile networks
Private interconnects into AWS, GCP, Azure, OCI to cut your egress
RPKI origin validation and MANRS-conformant routing
Median AS-path length to subscriber
Embedded cache inside the ISP0 hops
Direct peer or public IX1 hop
Transit fallback2–3 hops

78% of delivered bytes leave the network over a direct peer or an embedded cache.

Failure is routine, not an incident

Health checks drain a PoP out of anycast in seconds. Neighbouring PoPs absorb the traffic with the cache already warm from the shared regional shield, so a drain looks like a small latency bump rather than an outage.

Capacity headroom by policy

Every region is provisioned to carry its own peak plus the largest single neighbouring region's peak. That headroom is what makes unmetered DDoS mitigation an honest promise rather than a marketing one.

Data residency you can configure

Pin caching, logging and edge-function state to the EU, UK, US, or a specific region. Certified for SOC 2 Type II, ISO 27001/27018 and PCI DSS Level 1 on the delivery path.

Want the city-by-city list and our peering policy?

We will send the full PoP inventory, PeeringDB record and the current RUM dataset for your top markets.