Skip to content
CDN

Performance

Measured by someone else, every minute

PerfOps times real browsers fetching the same file from eight major CDNs. Below is the last hour of that data, unedited, with Edge in green.
Create a deploymentHow it's measured

Live

Median latency, last hour

United Kingdom, one-minute granularity. Hover the chart for exact values.

Current ranking

Median, last 15 min · UK · sample data

  1. 117.9ms
  2. 2Akamai20.5ms
  3. 3Cloudflare21.8ms
  4. 4CDN7722.3ms
  5. 5Amazon CloudFront22.5ms
  6. 6bunny.net22.7ms
  7. 7BlazingCDN24.8ms
  8. 8Google Cloud CDN27.0ms

Last 24 hours

—

Loading…

Last 7 days

—

Loading…

Last 30 days

—

Loading…

Independent real-user monitoring by PerfOps. Chart clipped at 32ms.

Independent real-user monitoring by PerfOps.

Why it's fast

Short trips, hot memory, a lean core

Three things decide how quickly a file arrives: how far it travels, where it's stored when it gets there, and how much work the server does to send it. Edge works on all three across 988 locations.
  • Visitors reach the nearest of 988 locations, so most requests never cross an ocean
  • Popular objects stay in RAM and the long tail sits on local NVMe
  • The serving path is written in Rust, with async I/O and zero-copy sends

Methodology

We don't mark our own homework

The chart comes from PerfOps, an independent real-user monitoring service that benchmarks DNS, CDN and cloud providers. We pass their data through as it arrives.
  • Real User Monitoring from actual browsers, not synthetic probes in data centres
  • A median per minute, so one bad connection can't skew the line
  • Filterable by country and region; this page shows the UK
  • The same eight providers and the same test object, every minute

Check it yourself

Time it from your own laptop

Every response names the node that served it and whether it came from cache. Run this against your deployment, then against your current CDN.
  • x-cache shows HIT or MISS
  • x-edge-location names the node that answered
  • time_starttransfer is your time to first byte
Read about cache headers
terminal
curl -so /dev/null -D - https://cdn.example.com/app.js \
  -w "ttfb: %{time_starttransfer}s\n" | grep -Ei "x-cache|x-edge|ttfb"

x-cache: HIT
x-edge-location: eu-west-1
ttfb: 0.011s

FAQ

About the numbers

Who collects this data?
PerfOps, an independent monitoring company. Browsers visiting sites that carry its beacon time a download from each CDN and report the result. Edge doesn't run the probes or filter the results.
Why the United Kingdom?
It's a dense, well-measured market, which keeps the per-minute median stable. PerfOps publishes data for other countries too, and results differ by region and by hour.
Why median rather than average?
Averages get dragged around by a handful of very slow connections. The median describes what a typical visitor experienced in that minute.
What if the live data doesn't load?
The board falls back to clearly labelled sample data so the page still renders. Live figures return as soon as the PerfOps API responds.
Does a few milliseconds matter?
Time to first byte feeds straight into page load and Core Web Vitals. A page with dozens of assets pays that latency on every one of them.

Put your own traffic through it

Point one hostname at Edge, watch x-cache flip to HIT and compare the numbers with what you have today.

Create a deploymentSee pricing

Free tier: 3 deployments and 500k requests a month, hard-capped. Bandwidth is always $0.