Skip to main content
Quick answers grouped by topic. For deeper guidance, follow the linked pages or the API reference.

General

What is Tenbyte CDN?

A global content delivery network with anycast routing, edge caching, image optimization, signed URLs, and a REST API. Edge nodes serve cached responses close to the user; origin only sees cache misses.

How does it speed up my site?

Three levers: shorter network distance (edge PoP near user), cached responses (no origin round-trip on hits), and HTTP/2 + HTTP/3 multiplexing.

What protocols are supported?

HTTP/1.1, HTTP/2, and HTTP/3 (QUIC) on the client side. Origin pulls support HTTP/1.1 and HTTP/2.

Caching

What is the default cache TTL?

The edge respects your origin’s Cache-Control: max-age and Expires headers. To override, configure a cache rule.

Why do I keep seeing x-cache: MISS?

Common causes:
  • Origin sends Cache-Control: no-store, private, or max-age=0.
  • Each request has a unique query string and cache-key includes the query.
  • Different Vary headers fragment the cache.
  • Object exceeds the max cacheable size.
Inspect the response with curl -I and check the cache rule for the path.

How do I bust the cache after a deploy?

Use Purge by Pattern for a path or wildcard, or Purge All. Both are available via the API:
curl -X POST "https://api.tenbyte.io/cdn/distributions/$DISTRIBUTION_ID/purge" \
  -H "Authorization: Bearer $TENBYTE_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"paths": ["/static/*"]}'

Security

Is my content secure?

TLS 1.2/1.3, optional WAF, token-authenticated signed URLs, and IP / referrer / country rules. DDoS mitigation runs at the edge.

How do I protect a private path?

Layer it: token authentication for time-limited URLs, plus referrer or IP rules so a leaked URL still can’t be replayed from arbitrary networks. See Access rules.

Where do I rotate the signing secret?

Per access rule, in the console. Walk through the rotation runbook before swapping in production.

Operations

How do I monitor traffic?

Analytics — bandwidth, request count, cache-hit ratio, and response-class breakdown. Pull the same metrics from the API for your dashboards.

Can I run multi-region or multi-CDN?

Yes. Tenbyte CDN routes to the healthiest edge automatically. For multi-CDN setups, point one CNAME per provider and use a steering DNS (Route 53, NS1) for failover.

What happens during a regional outage?

Traffic shifts to the next-best PoP via anycast and health checks. Origin is only contacted on cache miss, so cached content keeps serving.

API and automation

Where is the API reference?

CDN API reference. The OpenAPI spec is published at https://raw.githubusercontent.com/vidinfra/open-api-docs/refs/heads/main/cdn-openapi.json.

How do I authenticate API calls?

Bearer token in the Authorization header. Generate one in Organization → API Keys:
curl -H "Authorization: Bearer $TENBYTE_API_TOKEN" https://api.tenbyte.io/cdn/distributions

Are there rate limits?

Yes. Standard accounts get a generous per-minute quota that’s enough for normal automation. Bulk imports or large purge fan-outs should batch and back off on 429.

Are webhooks supported?

Yes — for purge completion, certificate events, and traffic alerts. Configure in the distribution settings.

Billing

How is Tenbyte CDN billed?

Pay-as-you-go on bandwidth and requests. No minimums, no long-term commitment. See Billing.

Does cache miss traffic cost more?

Egress from origin to edge is metered separately. Tuning cache rules to raise hit ratio is the cheapest way to lower bills.

Are purges billed?

Purges themselves are free. The next request after a purge is a cache miss and counts as origin egress.

Support

24/7 support via console chat and email. Critical incidents get priority routing.