About

This project monitors delay of various Cloudflare updates/operations, and has also expanded into AI and generic performance monitoring, using distributed monitoring locations.

For various delay jobs, such as updating a DNS Record, or updating a Worker, we perform the update via the Cloudflare API and then check from the configured probe locations to measure when the change becomes visible at the edge.

Workers AI Performance is also measured from a more limited subset of locations, mostly focused on performance comparison and errors.

Lastly, there is various performance jobs comparing different cloud platforms and services.

Please note that none of these are designed to be perfect benchmarks. Delay Jobs focus on showing issues with update propagation and relative delay if you had done the same action at the same time, how long it'd take for you to see the update on edge.

For performance jobs, a greater care is taken in accuracy but is still hard to guarantee perfect routing in all cases. Most of these locations were handpicked for low latency to Cloudflare (only a few ms max) and all are in data centers.

DNS and HTTP probes collect results throughout the day. Location coverage and run frequency vary by experiment.

Charts use aggregated results stored in ClickHouse. Current job status updates live.

I'm Tyler O'Brien, pseudonym "Chaika". I'm a software engineer and cloud enthusiast. I have a passion for building cool systems, gathering data, and connecting people with data.

You can find me on my website, bsky, and at tyler @ this site via email.

Find this useful? Find more tools of mine at https://tylerobrien.dev/tools/.

Disclaimer: This site is independently operated and not an official product or service of any monitored provider. All trademarks belong to their respective owners.

Explore Performance for service comparisons, WebSocket connection lifetimes and CI runner benchmarks. Cloudflare Delay covers propagation and cron timing; Routing shows which Cloudflare locations the probes reach.