What if the internet were a patient in an ICU? InternetVitals monitors 41 backbone services - Cloudflare, AWS, Azure, GCP, GitHub, Stripe, major DNS providers and turns their combined status into actual vital signs: pulse (BPM), temperature (°C), blood pressure, and SpO2. Plus one overall Internet Health. There's also a Console theme — green-on-black terminal style with a live syslog feed of real incidents. For the devops crowd. Built entirely on Cloudflare Workers, D1, KV, Cron Triggers etc.
No reviews yetBe the first to leave a review for Monitor the internet like a patient
Maker
📌
Hey PH 👋 Maker here.
Built this over two evenings of my sabbatical after watching yet another major outage hit and thinking - why does monitoring infrastructure have to be so boring?
The medical framing was the whole point: instead of a wall of green/red badges, you get pulse, temperature, blood pressure. When Cloudflare degrades, the internet "runs a fever." When AWS goes down, the pulse spikes.
Happy to answer anything about the architecture, the weighting methodology, or why exactly I decided the internet deserves a blood pressure reading 😄
Report
Does the vital signs math actually correlate to real outages, or is it more of a visual novelty on top of the raw status feeds? Curious how you tuned the BPM/temp mappings so they mean something useful during a real Cloudflare incident.
Report
Maker
@azizkayoluhx6g
Honest answer: it’s mostly visual novelty right now, with some real signal underneath.
The health score itself does correlate its a weighted average across 41 services, so when Cloudflare degrades (16% weight), you see a meaningful drop. That part is real.
The BPM/temperature mappings are derived from the same data but are more metaphor than measurement. BPM rises with active incident count, temperature rises as health score drops the formulas are simple and the thresholds were tuned by feel, not by backtesting against historical outages.
So: the underlying data is legit, the vital signs framing is intentionally metaphorical. I didn’t want to oversell it as a precision diagnostic tool it’s more “at a glance, is the internet having a bad day” than “exactly how bad is this Cloudflare incident.”
That said backtesting the mappings against real incidents is on the list. Would make it meaningfully more useful.
Does the vital signs math actually correlate to real outages, or is it more of a visual novelty on top of the raw status feeds? Curious how you tuned the BPM/temp mappings so they mean something useful during a real Cloudflare incident.