Security alerts WordPress 7.1.4 · no-login code execution in the updater 117 critical WordPress plugin CVEs · in October, most need no login

Is it up? Is it safe? Can you prove it?

1Add a domain · 30 seconds, no agent, no DNS change.

https://

2We watch it two ways · Up or down every 10 seconds. Safe or exposed all day.

Uptime History

30-day monitoring windowlive
LOCATIONNOWRESULT
LOS ANGELES  UP     176MS
CHICAGO      UP     188MS
LONDON       UP     241MS
TOKYO        UP     264MS
SANTIAGO     UP     312MS
JOHANNESBURG UP     395MS

Last 30 days

99.98%

uptime · 263ms average right now

Online Degraded Down
Oct 2Oct 10Oct 17Oct 25 Now

Up from all 6 locations.

A

Security 94/100

TLS, headers, DNS, email

A−

Exposure

versions shown, no known CVEs

SSL
74 days left
Headers
6 of 6
Last scan
2h ago

3You get the message

Slack · #ops · 10:37

example.com is down · HTTP 502 from 3 of 6 locations

Email · [email protected] · 10:37

DOWN: example.com, confirmed by 3 locations

JIRA · OPS-118 · 10:37

example.com down: HTTP 502 (3 of 6 nodes)

Linear · OPS-42 · 10:37

Incident opened for example.com

Teams · Ops channel · 10:41

example.com recovered after 4m 12s

Cloudflare offline page went up for visitors at 10:37, came down at 10:41.

~10 sec
Check Interval
6 Locations
3-Node Consensus
Zero
False Positives
~5s
Alert Delivery
100%
Engineer Built & Run

More than up or down

Every monitor is also a security record

Uptime tells you the site answered. The same monitor also records what it answered with: the software it discloses, the headers it sends, the certificate it presents. When any of that changes you hear about it, and the change is kept.

External exposure

The server, framework and CMS versions your site discloses, matched against end-of-life dates and known CVEs, with actively exploited ones escalated. New, resolved and escalated findings go out on the same channels as outages: email, Slack, JIRA, Linear, Teams.

Security timeline

A timeline per domain with incidents and security changes side by side: a header dropped, a certificate swapped, a grade that moved, an outage. Kept 12 months on Free, 2 years on Pro, forever on Enterprise. Evidence, not just a dashboard.

Framework mapping Enterprise

Every check mapped to SOC 2, ISO 27001, NIST CSF, NIST 800-53, PCI DSS and HITRUST, with evidence export for your auditor.

Cloudflare Integration

Your domain is your status page.

When downtime hits, visitors stay on your URL and see a branded offline page instead of an error. When you recover, they're redirected automatically. No third-party status page to maintain. No manual updates. No forgotten "we're back!" posts.

Outage confirmed

Consensus reached — your origin is genuinely down

Worker route activated instantly

Cloudflare intercepts requests and serves your offline page

Recovery detected — route removed

Traffic flows back to your origin automatically

Works on Cloudflare's Free plan

Cloudflare Workers includes 100,000 free requests per day — more than enough to serve your offline page during any outage. No paid Cloudflare plan required.

Use the default page or provide your own custom HTML. Just needs a Cloudflare API token with Worker Scripts and Workers Routes permissions.

example.com

503 — Service Down

We're on it.

Something went wrong and our monitoring caught it. Engineers are investigating.

Auto-reloads when back up

"Night Rain" offline page — served via Cloudflare's edge network · auto-reloads when back up

One timeline for everything that happens to your site

Downtime, security changes, new CVEs and certificate renewals land on one timeline, with an alert the moment each one happens. How fast we detect outages

Pricing

Free for one domain. From $5 a month for a team.

Plus $5 · Pro $20 · Enterprise $149 a month. 30-day Pro trial, nothing charged today, cancel anytime.

Start Monitoring Free Compare plans →