# How to Monitor Cloudflare Uptime

> Cloudflare provides CDN, DDoS protection, DNS, and edge computing services for websites and applications.

*Source: https://monitoristic.com/monitor/cloudflare*

---

## Why Monitor Cloudflare?

Cloudflare sits between your users and your origin server. If Cloudflare has issues, your site becomes unreachable even if your server is perfectly healthy. DNS failures are especially impactful — your domain simply stops resolving.

## What to Monitor

- `your-domain.com` — Your public domain (routed through Cloudflare)
- `your-origin-server-ip` — Your origin server directly (to distinguish Cloudflare issues from origin issues)
- `your-workers-endpoint.com` — Cloudflare Workers endpoints (if applicable)

## What You Should Actually Do

1. Monitor your domain through Cloudflare — the URL your users actually visit
2. Monitor your origin server directly — bypassing Cloudflare to distinguish edge issues from origin issues
3. Use a monitoring service that doesn't depend on Cloudflare — if your monitor also uses Cloudflare DNS, you might miss the outage
4. Create a status page hosted independently — not behind the same Cloudflare zone as your app
5. Bookmark cloudflarestatus.com — Cloudflare's official status page for global edge health

## Cloudflare's Official Status Page

Cloudflare publishes real-time status at https://www.cloudflarestatus.com. Your own monitor complements it by catching connection-level issues, often before the status page updates.

## Takeaway

Cloudflare outages create a uniquely disorienting situation: your server is healthy, your code is correct, your database is responsive — but your users can't reach you. The fix isn't on your side. The only thing you control is how quickly you detect it, communicate it, and wait it out. Two monitors — one through Cloudflare, one direct to origin — tell you which layer failed in seconds instead of minutes.

## Frequently Asked Questions

### How do I get notified when Cloudflare affects my site?

Set up two monitors on Monitoristic: one for your public domain (goes through Cloudflare) and one for your origin IP or a non-Cloudflare domain. When the first is down and the second is up, it's a Cloudflare issue.

### Should I monitor cloudflare.com?

No — monitor YOUR domain that routes through Cloudflare. Cloudflare's website can be up while their edge network has regional issues affecting your site.

### Why would my site be down if my server is healthy?

Cloudflare sits between your users and your server. If Cloudflare's edge can't connect to your origin (522 errors), or if their DNS is slow, users can't reach you even though your server is responding normally.

### How is this different from cloudflarestatus.com?

Cloudflare's status page shows global edge health by region. Your monitor checks whether YOUR specific site is reachable through Cloudflare. A regional issue might affect you without appearing on the global page.