Statistics
A zone's statistics page shows what it delivered, how much of that came from the cache, what was fetched from your origin, and where the viewers were. Every figure is in UTC, and most of them are available from the API.
A period is any range up to 366 days that does not end in the future, measured in UTC; hourly detail covers up to 31 days, and a longer period is shown by day. Hourly figures are kept for 90 days and older traffic is kept by day, so a period that starts more than 90 days ago is shown by day whichever detail is chosen. Figures reach the page within a few minutes of the traffic, so the current hour is always still filling.
The tiles#
| Tile | What it counts |
|---|---|
| Bandwidth delivered | Bytes sent to viewers, from the cache or from your origin. This is what the invoice is based on, so the traffic of event streams and WebSockets, which is not charged, is not in it |
| Requests | Viewer requests answered, whether from the cache or from your origin. The line beneath says how many were fetched from your origin |
| Cache hit ratio | Requests served from the cache as a share of all requests. The line beneath is the number |
| Blocked | Requests your blocking rules refused, by rule. Shown only when something was refused, and never billed |
| Origin bandwidth | Bytes fetched from your origin, and how much less that is than what was delivered |
A request is one viewer request answered: a hit, or a fetch. A request that had to be passed through to your origin, because of a cookie, an Authorization header or a method other than GET and HEAD, counts as fetched from your origin. A HEAD and a 304 count as requests with no bytes delivered (a HEAD for a file not yet cached still fetches it from your origin), and so does each server-sent event stream and each WebSocket, however long it stays open: see Server-sent events and WebSockets. What a viewer uploads is not counted as either. Served from cache and fetched from origin add up to Requests exactly.
Not counted at all: requests the edge refused (a signed link that failed, a method a bucket does not accept; a blocked visitor is counted under Blocked instead), the maintenance page, the background refresh of expired files, and the edge's own error pages, with one exception: a large file whose next piece could not be fetched is counted as a request fetched from your origin, with whatever was fetched before it failed. The pieces the edge reads ahead when serving a large file count as origin bandwidth, since your origin sent them.
A zone that has used an origin shield also gets an Origin Shield chart of the bytes the Home PoP sent to the other locations, with the requests it answered for them above it; that is traffic between our own locations and neither viewer traffic nor billed. See Origin shield.
Where visitors came from#
The Where visitors came from box lists the countries your requests came from, with requests, bytes delivered and each country's share. Under them, the Network type rows (VPN networks, Hosting and datacenter networks, Tor exit nodes) count how many of the requests you served came from each, which is the number to read before switching one of those blocking rules on: it is how many real requests the rule would have refused. A request can come from more than one network type, so those rows are not parts of a whole. When more than twelve countries sent traffic, the ten busiest are shown and Show all lists the rest.
Once something has been refused, a Served / Blocked switch in the header turns the whole box to what your rules turned away: the countries refused, how many requests the VPN, hosting and Tor rules each refused, and every AS number the zone blocks, with the name it is registered under and how many requests from it were refused. An AS number that sent nothing reads 0, and its name is how you check it is the network you meant. Every share in the Blocked view is of all the requests refused in the period.
Countries and AS numbers are counted per day, so they cover whole UTC days and can reach a little either side of a period that starts or ends mid-day. A country the data cannot place appears as Unknown. Country data comes from DB-IP, network data and AS names from iptoasn. See Blocking visitors.
Units and the zone list#
Bytes here and on the invoice are decimal: a kilobyte is 1,000 bytes, a gigabyte 1,000,000,000 and a terabyte 1,000 gigabytes. The file size limits elsewhere in these articles (10 MB, 5 MB, 20 GB) are binary, so 10 MB there is 10,485,760 bytes. The zone list on the CDN page shows each zone's bandwidth for the current calendar month and its cache hit rate, both in UTC.
What is not shown#
There is no breakdown by URL or by status code, and no per-hostname figure. The statistics describe traffic, not the machines that carried it: which server answered and how a file was stored are not published. Requests, cache hits and misses, bandwidth, origin bandwidth and the Blocked total, with the countries and the fifty busiest networks by AS number, are available from the API; the Origin Shield chart, the Blocked breakdown by rule, the served-from-VPN, hosting and Tor counts and the names of the AS numbers you block are only on this page.