Custom Offline Page
Auto-deployed via Cloudflare
When your origin goes down, visitors see a broken page. With Cloudflare Offline Pages, a branded maintenance page is deployed automatically via Cloudflare Workers — and removed the moment your site recovers.
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.
503 — Service Down
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
Every incident gets a detailed timeline showing exactly what happened, when, and how it was resolved.
Last Successful Check · Feb 27, 2026 11:18:36 AM
Los Angeles, US · HTTP 200 · 14ms
Failure Detected · Feb 27, 2026 11:18:54 AM
London, UK · HTTP 500 · 396ms
Outage Confirmed (4 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
5 of 5 nodes agreed · threshold: 3
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
Recovered · Feb 27, 2026 11:22:15 AM
London, UK · HTTP 200 · 392ms
Recovery Confirmed (different server) · Feb 27, 2026 11:22:16 AM
Chicago, US · HTTP 200 · 13ms
Recovery Confirmed (different server) · Feb 27, 2026 11:22:17 AM
Los Angeles, US · HTTP 200 · 14ms
3 of 5 nodes agreed · threshold: 3
Recovery Confirmed (2 servers) · Feb 27, 2026 11:22:18 AM
Tokyo, Japan · HTTP 200 · 320ms
Santiago, Chile · HTTP 200 · 441ms
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
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.
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.
Without Monitoring
With InternetSecure
Every check, every minute, from every node.
Get notified instantly via email, Slack, JIRA, Linear, and Microsoft Teams. Clear, actionable alerts with all the context you need.
DOWN: example.com is down
Domain
example.com
| Status | HTTP 500 |
| Error | Internal Server Error |
| Down Since | 2026-02-27 11:18:54 |
| Offline Page | ⚡ Activated — visitors see maintenance page |
InternetSecure.org — Domain Security Monitoring
InternetSecure APP
example.com — DOWN
HTTP 500 — Internal Server Error
View IncidentJIRA Ticket — IUJ-5
🌐 Confirmed down from: California, Illinois, Europe
Offline page activated — visitors see maintenance page
InternetSecure APP
example.com — UP
Recovered after 3m 21s
View IncidentJIRA Ticket — IUJ-5
Offline page deactivated — normal traffic restored
IUJ-5
Open[INC-42] DOWN: example.com
| Domain | example.com |
| Status | DOWN |
| Cause | HTTP 500 — Internal Server Error |
| Detected By | London, United Kingdom |
| Down Since | Feb 27, 2026 11:18:54 AM |
| Cloudflare | Offline page activated |
Timeline
Last Successful Check — Illinois · HTTP 200 · 167ms
Failure Detected — Europe · HTTP 500 · 396ms
Confirmed — Illinois · HTTP 500
Alert Sent — Jira, Linear, Slack, Teams, Email
CF Offline Page Activated
Incident in progress — this ticket will be updated on resolution.
Created by InternetSecure.org Uptime Monitoring
SEC-12
Urgent[INC-42] DOWN: example.com
| Domain | example.com |
| Status | DOWN |
| Cause | HTTP 500 — Internal Server Error |
| Detected By | London, United Kingdom |
| Down Since | Feb 27, 2026 11:18:54 AM |
| Cloudflare | Offline page activated |
Timeline
Last Successful Check — Illinois · HTTP 200 · 167ms
Failure Detected — Europe · HTTP 500 · 396ms
Confirmed — Illinois · HTTP 500
Alert Sent — Linear, Slack, Teams, Email
CF Offline Page Activated
Incident in progress — this issue will be updated on resolution.
Created by InternetSecure.org Uptime Monitoring
No more false alerts from a single node's network hiccup. 2+ servers must agree before an incident is confirmed.
Track response times from each location. Get degraded alerts when your site is up but slow, with configurable thresholds.
Verify your page returns the expected content, not just a 200 status. Catch silent failures like error pages or blank responses.
Automatically deploy a branded maintenance page via Cloudflare Workers when your origin goes down. Deactivates on recovery.
Schedule maintenance windows to suppress alerts during planned downtime. Set specific days and time ranges.
Optionally re-send alerts every 30 minutes during extended outages so incidents don't slip through the cracks.
Free plan includes uptime monitoring with 1-minute intervals. Upgrade for more domains and advanced features.
