Cloudflare SWR Edge Cache Dashboard

Use Start to begin the SWR test session.

SESSION_ID: 4c034bea-9fca-4652-a134-e6f799cd16a8 Waiting for data state: warming up

No polls yet. Start collecting responses to evaluate SWR behavior.

Browser cache is disabled with Cache-Control: no-store, no-cache, max-age=0, must-revalidate.

CDN cache uses CDN-Cache-Control: public, s-maxage=10, stale-while-revalidate=86400.

s-maxage controls when revalidation starts, while stale-while-revalidate controls how long stale content can still be served.

Polling runs every 2-4s (jittered), using /api/time.json?session=<SESSION_ID>.

The endpoint has an artificial response delay jitter of 2-6s.

Expected behavior: most polls are fast from edge, and payload updates usually land around 12-20s after the previous change.

Observed change interval

avg

min · max

Purpose: time between payload timestamp updates to verify background revalidation cadence.

Recent checks (last 10)

slow polls (≥4.2s): 0

confirmed SWR polls: 0

MISS while running: 0

Headers (latest poll)

CF-Cache-Status

Age

CDN-Cache-Control

X-Debug-Cache-Policy

Audit log (latest 100 checks)

#SessionDurationServer nowRecvAgeΔ payloadCF-Cache-StatusAge hdrPolicy debugFlags
No log rows in this filter.

How to read this

  • state: warming up means cache is still being populated.
  • state: running means warm-up signals were seen and steady-state checks apply.
  • confirmed SWR poll means payload changed and no slow poll happened since the previous payload change.
  • slow poll means request duration ≥4.2s.
  • suspicious row means this poll matched one or more warning rules (shown in-row).
  • MISS is expected during warm-up only; MISS while running should be treated as a cache issue.

Expected policy: no browser cache + public, s-maxage=10, stale-while-revalidate=86400