Cloudflare + LinkRivers

Your CDN is serving
yesterday's site

You updated your site. Cloudflare is still serving the old version from cache. Your DNS change hasn't propagated to Asia. Your WAF is blocking real customers. LinkRivers detects all of this and Autopilot purges, fixes, and alerts automatically.

Unlimited sites. No credit card required.

CDN Health Check
Stale Cache Detected
DNS (US-East) Propagated
DNS (AP-Southeast) Stale (old IP)
Cache (/pricing) Serving v2.3 (current: v2.4)
SSL Certificate Valid (47 days)
Autopilot: Purging stale cache for /pricing. DNS propagation alert sent.

Common Cloudflare Problems

The invisible layer between you and your visitors

Stale Cache After Updates

You deploy a new version of your site but Cloudflare keeps serving the old one from edge cache. Some visitors see the update, others don't. LinkRivers checks content freshness from multiple global locations and Autopilot purges stale URLs automatically.

DNS Propagation Gaps

You change a DNS record but it takes hours to propagate globally. Users in some regions hit the old server, see errors, or get timeouts. LinkRivers monitors DNS resolution from 6 global locations and alerts when propagation is incomplete.

WAF Blocking Real Customers

Cloudflare's WAF rules are aggressive by default. Legitimate form submissions, API calls, or checkout flows get blocked with 403 errors. LinkRivers tracks real user block rates and identifies which WAF rules are causing false positives.

SSL Certificate Expiry

Cloudflare manages your SSL but the origin certificate can expire silently. Or your universal certificate fails to renew. LinkRivers monitors SSL status daily and warns you weeks before expiry.

Origin Server Unreachable

Cloudflare shows a 522 or 524 error when it can't reach your origin. But by the time you see it, customers have already left. LinkRivers monitors origin connectivity independently and alerts within 60 seconds of an origin failure.

Page Rules Gone Wrong

A misconfigured page rule caches your admin panel, disables HTTPS on a section of your site, or creates a redirect loop. LinkRivers detects the functional impact through real user monitoring before you notice the misconfiguration.

Simple Setup

Connected in under two minutes

1

Add Your API Token

Generate a Cloudflare API token with Zone:Read and Cache:Purge permissions. Paste it into LinkRivers.

2

Select Your Zones

Choose which Cloudflare zones to monitor. LinkRivers starts tracking DNS, cache, and SSL immediately.

3

Autopilot Protects

Stale caches get purged. DNS issues get flagged. SSL expiry warnings sent weeks in advance.

FAQ

Common questions

How does LinkRivers work with Cloudflare?

LinkRivers connects via API token to monitor your DNS records, cache status, SSL certificates, and WAF rules. When issues are detected, Autopilot can automatically purge stale cache or alert your team.

Can LinkRivers automatically purge Cloudflare cache?

Yes. When LinkRivers detects stale content after a deployment or content update, Autopilot can automatically trigger a cache purge for affected URLs or the entire zone.

Does LinkRivers detect WAF false positives?

LinkRivers tracks real user error rates including 403 and 1020 Cloudflare block pages. When legitimate visitors start getting blocked at higher rates, LinkRivers alerts you with the specific WAF rule causing the issue.

How does DNS monitoring work?

LinkRivers checks your DNS records from multiple global locations every minute. It detects propagation delays, record mismatches between resolvers, and alerts when DNS changes haven't propagated to all regions.

Your CDN should help,
not hide problems.

Connect Cloudflare and let LinkRivers watch the layer between you and your visitors. Free forever for unlimited sites.

Connect Cloudflare Free