Skip to main content
Requests Served counts every HTTP request the CDN processed — cache hits, cache misses, errors, and OPTIONS preflights all included.
Requests Served Statistics

What it tells you

  • Total request volume in the selected window.
  • How that compares to the previous period.
  • Hourly / daily distribution — peaks, troughs, anomalies.

How to read the chart

ElementMeaning
Main numberTotal requests (M / B suffix).
PercentageDelta vs the prior identical window.
SparklineTime-series — find spikes and dips.

Pull via API

curl -sS "https://api.tenbyte.io/cdn/distributions/$DISTRIBUTION_ID/analytics/requests?from=2026-05-01T00:00:00Z&to=2026-05-09T00:00:00Z&granularity=hour" \
  -H "Authorization: Bearer $TENBYTE_API_TOKEN" | jq
Response (truncated):
{
  "total_requests": 45012345,
  "series": [
    {"ts": "2026-05-01T00:00:00Z", "requests": 1923456},
    {"ts": "2026-05-01T01:00:00Z", "requests": 1876543}
  ]
}

Requests vs traffic

A high request count with low traffic means tiny payloads (API JSON, manifests). A high traffic with low requests means big objects (video, downloads). Watch both ratios.
RatioWorkload
Many requests, low bytes/reqAPI-style or HLS manifest.
Few requests, high bytes/reqVideo / downloads / large images.
Both highMixed-purpose distribution — scope per-path metrics.

Spot abuse

Sudden request spikes without a corresponding traffic spike usually mean:
  • Bot scraping — same small object hit thousands of times.
  • Cache busting — random query strings forcing every request to be unique.
  • Probing404 flood from a vulnerability scanner.
Drill into response classes and consider an IP or country access rule.

Operational tips

  • Group by path. The top 10 paths by request count usually drive the bulk of origin traffic.
  • Watch off-hours. Sustained traffic at 03:00 local is rarely human.
  • Combine with cache-hit ratio. High request count + low HIT% = origin pain. Tune cache rules.
  • Alert on rate change, not raw totals — easier to write portable thresholds.