What Cloudflare's 520, 521, 522, 523, 524, 525, and 526 errors mean, why they happen between Cloudflare and origin, and how to diagnose and fix each one.
Understand 500, 502, 503 and 504 server errors, diagnose application, proxy and upstream causes, and monitor status, body and error-rate patterns.
Monitor Cloudflare Workers, D1, R2, and KV with current limits, native telemetry, consistency checks, and outside-in edge probes.
Detect DDoS traffic, distinguish attacks from legitimate spikes, monitor edge and origin pressure, and verify mitigation without false alerts in production.
Monitor Cloudflare edge delivery and protected origin-dependent paths separately so cache hits do not hide API, TLS, WAF, or backend failures.
3 monitors, 10-minute checks, instant email and Slack alerts — no credit card required.
Start Free Monitoring