Cloudflare Edge Node
This endpoint is served from a Cloudflare edge node, not from the origin server.
You are at the edge. Requests to this host are answered by the nearest Cloudflare data center. Cached content is delivered from there; anything else is fetched from origin on your behalf.
Nothing here is authoritative. The origin remains the single source of truth.
Status
All systems operational Updated 30 Oct 2026 · 21:12 UTC
99.99%Uptime, 30 days
12.4MRequests, 24 hours
94.2%Cache hit ratio
41 msp95 time to first byte
Edge routingOperational
Origin fetchOperational
Cache purgeOperational
TLS terminationOperational
Node
| Network | Cloudflare edge network |
|---|---|
| Serving node | Nearest available data center |
| Tracing | Responses carry a CF-Ray header |
| Caching | Standard edge cache, purge within 30 seconds |
| Protocols | HTTPS, HTTP/2 and HTTP/3 |
| Origin | Never exposed directly |
What this means
- Latency follows the distance to the nearest Cloudflare data center.
- Cached objects are copies of origin files, kept for speed rather than durability.
- Purges and cache expiry never delete anything at origin.
- Full request
details, including the serving node, are in the
cf-rayresponse header.