This content originally appeared on DEV Community and was authored by Yibnum
Yesterday’s Cloudflare outage wasted a few hours of my time — not because the outage was confusing, but because my monitoring stack gave me zero context about what was actually failing.
Everything lit up red. Every alert fired.
But nothing told me whether the problem was:
my origin
Cloudflare’s edge
DNS
SSL
routing
My servers were completely fine the whole time.
The real issue ended up being Cloudflare’s Bot Management system (a feature file doubled in size and tripped them up).
The bigger discovery:
most monitoring tools cannot tell the difference between an origin outage and a CDN/edge outage.
So I built a simple tool today to diagnose exactly that:
Paste a URL and it checks:
origin health
Cloudflare/Vercel/AWS edge
DNS
SSL expiry
CDN failure patterns
I built this out of frustration, but if you’re interested I’d love to hear how your monitoring handled the outage yesterday.
This content originally appeared on DEV Community and was authored by Yibnum
Yibnum | Sciencx (2025-11-19T21:44:34+00:00) Cloudflare went down yesterday. My monitoring lied. So I built this.. Retrieved from https://www.scien.cx/2025/11/19/cloudflare-went-down-yesterday-my-monitoring-lied-so-i-built-this/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.