Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tenbyte.io/llms.txt

Use this file to discover all available pages before exploring further.

Traffic Served measures the bytes the CDN sent to clients in a given window. It drives your bandwidth bill and signals whether traffic patterns are shifting under you.
Traffic Served Statistics

​
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

ElementMeaning
Main numberTotal bytes (KB / MB / GB / TB) for the selected window.
PercentageChange vs the prior identical window. Positive = growth.
SparklineDistribution over time — find spikes and dips.

​
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
Response (truncated): 
{
  "total_bytes": 1283456789012,
  "series": [
    {"ts": "2026-05-01T00:00:00Z", "bytes": 5012345678},
    {"ts": "2026-05-01T01:00:00Z", "bytes": 5234567890}
  ]
}
See the CDN API reference for filters (granularity, per-PoP breakdown).

​
Common patterns

PatternWhat it usually means
Steady daytime peaksHealthy — track week-over-week ratio.
Sudden spike with low cache-hit ratioOrigin will feel it. Check cache hit ratio and rule TTLs.
Spike with stable hit ratioReal traffic growth. Capacity-plan origin.
Sustained dropDNS issue, broken deploy, or upstream redirect bypassing the CDN.

​
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.