About

More about Action-Delay-API.

Overview

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

Job Types

For various delay jobs, such as updating a DNS Record, or updating a Worker, we perform the update via the Cloudflare API and then rapidly check via 35 locations when the change is visible on edge. When at least half see the change, we mark the job complete.

Workers AI Performance is also measured from a more limited subset of locations, mostly focused on performance comparsion 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 propogation 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.

Stats

9 Million+ DNS and HTTP Requests from all nodes per day to perform jobs, with over 400k unique per location delay job results daily.

All results stored in ClickHouse with no sampling, and status live updated, leveraging Postgres as well.