Requests / sec
142k
Cache Hit Ratio
98.7%
Avg Response
8ms
Active Nodes
22
Edge Nodes
22 / 22 operationalNew Yorkus-east-1
Ashburnus-east-2
Chicagous-central-1
Dallasus-south-1
Los Angelesus-west-1
San Joseus-west-2
Seattleus-west-3
Torontoca-east-1
São Paulosa-east-1
Londoneu-west-1
Amsterdameu-west-2
Frankfurteu-central-1
Pariseu-central-2
Stockholmeu-north-1
Warsaweu-east-1
Mumbaiap-south-1
Singaporeap-southeast-1
Hong Kongap-east-1
Tokyoap-northeast-1
Osakaap-northeast-2
Sydneyap-southeast-2
Johannesburgaf-south-1
Uptime — 30 days
Global CDN
99.98%
30 days agoToday
API
100.00%
30 days agoToday
DNS
99.99%
30 days agoToday
Recent Incidents
Resolved
Elevated latency — eu-central-1
2026-03-13 14:22 UTC — Resolved 2026-03-13 15:08 UTC
Frankfurt node experienced elevated p99 latency (45ms) due to upstream transit provider congestion. Traffic was rerouted via Amsterdam. No data loss.
Resolved
DNS resolution delay — af-south-1
2026-02-28 09:41 UTC — Resolved 2026-02-28 10:12 UTC
Johannesburg node showed intermittent DNS timeouts during scheduled BGP peer maintenance. Failover to secondary resolver activated. Resolution within 31 minutes.
Resolved
Cache invalidation propagation delay
2026-02-15 03:17 UTC — Resolved 2026-02-15 03:44 UTC
POST /purge requests experienced 8-12 second propagation delays across APAC nodes. Root cause: queue backlog during high-volume purge batch. Capacity adjusted.