CDN-aware uptime monitoring

Stop false uptime alerts from Cloudflare and other CDNs

CDNs can return HTTP 200 even when your origin is down. Most monitors will happily call that “up”.
StatusPage.me helps you detect real outages with multi-region checks, response validation, and clear incident updates.

Start monitoring free How to fix CDN false positives
Privacy-first. No creepy tracking. No sales calls.
The problem

Uptime monitoring lies when a CDN sits in front

If your monitor checks a URL that is served by a CDN edge, it might never hit your origin. When the origin fails, the CDN can still serve cached pages or friendly error pages with a 200 status. Your monitor says “up” while customers see “down”.

HTTP 200, but broken

Edge returns 200 for a cached page while API/origin is failing. Your users cannot login, but your monitor stays green.

Friendly CDN error pages

Some CDNs return branded error pages, sometimes with success codes. A naive “status code only” check will miss it.

Regional failures

One region cannot reach your origin, another can. Single-probe monitoring cannot reflect real-world impact.

What helps

Accurate checks plus fast incident communication

The win is simple: validate the response, not just the status code, and monitor from the regions your users actually use. When something breaks, publish an incident and keep customers informed.

Multi-region checks

See failures where they happen, not where your single probe lives.

Response validation

Use content and patterns to detect CDN error pages, broken app shells, and “fake OK” responses.

Smart failover

If a probe/region misbehaves, checks can fail over so you do not wake up for noise.

Incidents that look real

Turn detection into a clear incident timeline with updates your customers can trust.

Notify the right channels

Email, Slack, Discord, Telegram, and webhooks so teams react fast and customers stay informed.

Privacy-first by default

No invasive trackers. Your monitoring and status pages should not spy on your users.

Fix it

How to avoid CDN false positives

You do not need a PhD in cache headers. You need one reliable “truth” endpoint and a check that verifies the response.

1) Expose a non-cached health endpoint

Create a simple endpoint (example: /healthz) that returns a small response and is explicitly not cached by your CDN.

Tip: set CDN rules to bypass cache for that path and include Cache-Control: no-store.
2) Validate the response body

Do not trust status codes alone. Check for a known string or pattern so a CDN error page cannot pretend everything is fine.

Example: expect OK or a JSON key like "status":"ok".
3) Monitor from the right regions

If your users are in the US and EU, monitor from the US and EU. Regional routing, DNS, and peering can fail in weird ways.

4) Communicate fast when it breaks

Even with perfect monitoring, failures happen. A clean status page and consistent incident updates reduce tickets and panic.

Read monitoring guides Start monitoring free
Pricing

Start free and upgrade when you need more signal

No credit card. No sales calls. Monitor behind a CDN with confidence.

See plans and limits Create account
FAQ

CDN monitoring without the usual confusion

Clear answers about CDNs, response validation, incidents, and status pages.

CDNs can serve cached content or friendly error pages from the edge. Some responses still return HTTP 200, so basic uptime checks report “up” even when users cannot reach the real app.

Add a small non-cached health endpoint (like /healthz) and validate the response body. That gives you a reliable “truth” signal that the CDN cannot fake.

Monitoring tells you what broke. A status page tells customers what is happening. Clear incident updates reduce support load and protect trust during outages.

Yes. You can route alerts via email, Slack, Discord, Telegram, and webhooks so response is fast and consistent.

Yes. Status pages and monitoring should not track end users. We keep things privacy-first and avoid invasive third-party scripts.
Get alerted for real outages, not CDN illusions

Start free. Set up multi-region monitoring and publish your first public status page in minutes.

Start monitoring free See plans and limits