Uptime Monitoring
Zero False Positives

Integrated alerts via Email, Slack, JIRA, Linear, and Teams.

Cloudflare custom offline page — auto-deployed when your site goes down

vultr.com HEAD · 1 min
UP
/
362ms
SSL 216d | Checked 2s ago Security Scans
Apr 12, 1:00 PM Healthy 6 nodes avg 726ms
Santiago, Chile OK –200 653ms
Tokyo, Japan OK –200 1274ms
London, UK OK –200 540ms
Chicago, US OK –200 339ms
Los Angeles, US OK –200 377ms
Johannesburg, ZA OK –200 1173ms
1 min
Check Interval
6 Locations
3-Node Consensus
Zero
False Positives
~5s
Alert Delivery
100%
Engineer Built & Run
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

Incident Timeline

Every incident gets a detailed timeline showing exactly what happened, when, and how it was resolved.

INC-42 Resolved

example.com

Started

Feb 27, 11:18:54 AM

Duration

3m 21s

Cause

HTTP 500

Affected Servers

6 nodes

Last Successful Check · Feb 27, 2026 11:18:36 AM

Los Angeles, US · HTTP 200 · 14ms

18s

Failure Detected · Feb 27, 2026 11:18:54 AM

London, UK · HTTP 500 · 396ms

“HTTP 500 Internal Server Error”

2s

Outage Confirmed (5 servers) · Feb 27, 2026 11:18:56 AM

Chicago, US · HTTP 500 · 168ms

Los Angeles, US · HTTP 500 · 14ms

Tokyo, Japan · HTTP 500 · 320ms

Santiago, Chile · HTTP 500 · 441ms

Johannesburg, South Africa · HTTP 500 · 387ms

6 of 6 nodes agreed · threshold: 4

1s

Offline Page Activated · Feb 27, 2026 11:18:57 AM

Cloudflare Worker route enabled · visitors see maintenance page

JIRA Ticket Created · Feb 27, 2026 11:18:57 AM

IUJ-5

Slack Alert Sent · Feb 27, 2026 11:18:57 AM

Slack webhook

Email Alert Sent · Feb 27, 2026 11:18:57 AM

[email protected]

3m 18s

Recovered · Feb 27, 2026 11:22:15 AM

London, UK · HTTP 200 · 392ms

1s

Recovery Confirmed (different server) · Feb 27, 2026 11:22:16 AM

Chicago, US · HTTP 200 · 13ms

1s

Recovery Confirmed (different server) · Feb 27, 2026 11:22:17 AM

Los Angeles, US · HTTP 200 · 14ms

4 of 6 nodes agreed · threshold: 4

1s

Recovery Confirmed (3 servers) · Feb 27, 2026 11:22:18 AM

Tokyo, Japan · HTTP 200 · 320ms

Santiago, Chile · HTTP 200 · 441ms

Johannesburg, South Africa · HTTP 200 · 392ms

1s

Offline Page Deactivated · Feb 27, 2026 11:22:19 AM

Cloudflare Worker route removed · normal traffic restored

JIRA Recovery Updated · Feb 27, 2026 11:22:19 AM

IUJ-5

Slack Recovery Sent · Feb 27, 2026 11:22:19 AM

Slack webhook

Email Recovery Sent · Feb 27, 2026 11:22:19 AM

[email protected]

Not All Outages Are Created Equal

Detection speed depends on how your site fails. A hard crash is caught in seconds. A slow timeout takes longer to confirm — but we still catch it.

Hard Error 500 / Connection Refused
~5s
alert sent
0s 5s 10s 15s 20s 25s 30s 35s 40s 45s 50s 55s 60s 65s 70s 75s 80s 85s 90s
Detection ~1s Peer verification ~2s each
Slow Response 10s timeout
~25s
alert sent
0s 5s 10s 15s 20s 25s 30s 35s 40s 45s 50s 55s 60s 65s 70s 75s 80s 85s 90s
Detection ~10s Peer verification ~10s each
Complete Timeout 30s max-time
~75s
alert sent
0s 5s 10s 15s 20s 25s 30s 35s 40s 45s 50s 55s 60s 65s 70s 75s 80s 85s 90s
Detection ~30s Peer verification ~30s each

Why the range? Every check requires consensus — multiple nodes must independently confirm the outage before an alert fires. This eliminates false positives but means detection time scales with how long your server takes to fail.

You can configure per-domain timeouts to fine-tune detection speed for critical services.

3AM. Your Site Goes Down.

Without Monitoring

Nobody knows for hours
Customers see error pages
Found out from a customer tweet
Scramble to create tickets manually
No incident record

With InternetSecure

Team alerted in under 10s
Visitors see a branded offline page
Slack, Email, Teams — simultaneously
JIRA & Linear tickets auto-created
Full timeline for post-mortem

What We Check

Every check, every minute, from every node.

HTTP / HTTPS
Content Matching
Response Time
SSL Expiry
DNS Resolution
Status Codes
Redirect Chains
Multi-Node Consensus

Everything You Need

Multi-Node Consensus

No more false alerts from a single node's network hiccup. 2+ servers must agree before an incident is confirmed.

Response Time Tracking

Track response times from each location. Get degraded alerts when your site is up but slow, with configurable thresholds.

Content Matching

Verify your page returns the expected content, not just a 200 status. Catch silent failures like error pages or blank responses.

Cloudflare Offline Pages

Automatically deploy a branded maintenance page via Cloudflare Workers when your origin goes down. Deactivates on recovery.

Maintenance Windows

Schedule maintenance windows to suppress alerts during planned downtime. Set specific days and time ranges.

Repeat Alerts

Optionally re-send alerts every 30 minutes during extended outages so incidents don't slip through the cracks.

Start Monitoring in 30 Seconds

Free plan includes uptime monitoring with 1-minute intervals. Upgrade for more domains and advanced features.