Answering right now
Running on an unrecognized host
linux/x64 · node v22.19.0 · pid 1 · up 0s
Every value below is marked with the moment it was decided. That is the only reliable way to tell a fresh deploy from a cached copy of the last one.
- Build
- Request
- Browser
Built
18:39:50
2026-08-20 UTC
Frozen into the bundle
This request
19:49:44
2026-08-20 UTC
Produced by the server
Build
Baked in when the bundle was compiled
- Commit
- 13f606f
- Branch
- cloudflare
- Message
- Measure data-cache age instead of inferring it from latency
- Built with
- node v24.11.1
- Snapshot from
- next build
Machine
Read from this process on this request
- Host
- no platform signature in the environment
- Region
- —
- Hostname
- localhost
- NODE_ENV
- production
- Port
- 3000 (default)
- Memory
- 0 MB resident of 0 MB · 0 cpu
- Time zone
- UTC
How each page renders
Open each one, reload a few times, and watch its timestamp. Platforms disagree about caching more than anything else, and this is the fastest way to find out what yours actually did.
Static
Timestamp never moves until you rebuild
Prerendered once at build time and served as a file.
ISR
Timestamp moves at most once every 20 seconds
Cached, then regenerated in the background after it goes stale.
Dynamic
Timestamp moves on every reload
Rendered from scratch for each request.
Caching pages and caching the data inside them are separate systems. The data cache runs the same experiment against a public API.
What reached the app
9 of 11 watched headers
- host
- dp.0foq.com
- x-forwarded-proto
- https
- x-forwarded-host
- dp.0foq.com
- x-real-ip
- 216.73.216.41
- cf-ray
- a2e3ec4738c1e9de
- cf-ipcountry
- US
- x-vercel-ip-country
- US
- accept-encoding
- gzip, br
- user-agent
- Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
Environment
Anything key-shaped is masked before it renders
- NEXT_BUILD_ID
- Mt5s6dlYe9wZ_vqFF7wVx
- NEXT_DEPLOYMENT_ID
- set, but empty
- NEXT_PREVIEW_MODE_ID
- 4b72219c1e051b276b3aa12cc5965597
- NODE_ENV
- production
Endpoints
Timed from your browser, so this includes the network between you and the deployment.
- GET
/api/health—What a load balancer probes
- GET
/api/info—Build and runtime facts as JSON
- GET
/api/echo?region=test&cache=bust—Headers your proxy added on the way in
- POST
/api/echo—Whether POST bodies survive the hop
- GET
/api/upstreams—Server-side egress, on demand