Traffic Served

​

What it tells you

• Total bytes delivered to end users.
• Period-over-period change (today vs yesterday, week vs week).
• Trend lines that surface launches, viral spikes, and outages.

​

How to read the chart

​

Pull via API

curl -sS "https://api.tenbyte.io/cdn/distributions/$DISTRIBUTION_ID/analytics/traffic?from=2026-05-01T00:00:00Z&to=2026-05-09T00:00:00Z&granularity=hour" \
  -H "Authorization: Bearer $TENBYTE_API_TOKEN" | jq

{
  "total_bytes": 1283456789012,
  "series": [
    {"ts": "2026-05-01T00:00:00Z", "bytes": 5012345678},
    {"ts": "2026-05-01T01:00:00Z", "bytes": 5234567890}
  ]
}

​

Common patterns

​

Cost levers

• Raise cache hit ratio. Higher HIT% = same user-facing bytes, less origin egress.
• Compress text. Enable Gzip / Brotli in cache rules.
• Right-size images. Use Image Optimizer with format=auto and capped widths.
• Cap query-string variants. A noisy cache key duplicates the same bytes.

​

Operational tips

• Daily totals to finance. Pipe API totals into your billing spreadsheet or BI tool.
• Per-path breakdowns. Use the path filter to find the top 10 bandwidth consumers; cache or compress them harder.
• Alert on rate, not total. A 5× hourly spike is more actionable than absolute totals.