Skip to main content -
Letting AI Read Your Site Takes Four Layers
-
Rate Limits and Bot Rules Cut Our Daily Error-Minutes by 91%
-
Why support found nothing when they searched the Ref number from 104.23.x.x
-
Two Weeks of Error Pages Behind One Customer's Short Address
-
Why a green drift check on v27 hid a crawler bypass at v28
-
When the Firewall Log Stopped at v14
-
Why Our Allow Rule Allowed Nothing After the 520 Fix
-
We Assumed We Were Letting AI Crawlers In. We'd Been Blocking Them for Months.
-
Cloudflare Rulesets API and the 2am bot swarm
-
Why Our Own Firewall Could Not Stop the Bot Swarm at 2am
-
The Office Got Banned by Its Own IPFilter After 1,500 Hits
-
When the Bot Filter Blocked the Office's Own IP Address
-
The customer's own scraper IS the bot swarm you've been fighting
-
The Prod Box Was DDoSing Itself: An iCal Calendar Feature Looping Through the Public Edge
-
"The Whole Island Can't Reach Your Site": US Territories Are Separate Countries to Cloudflare
-
GPTBot vs OAI-SearchBot vs ChatGPT-User: blocking the wrong one deindexes you from AI search
-
Cloudflare Pro is a box of levers, not a managed service
-
Operator, not IP: fingerprinting a 40,000-IP proxy swarm by its RIPE maintainer
-
CPU Sat at 100% While Our Log Watcher Reported Nothing Wrong
-
Why Per-IP Bad-Rate Found Nothing While the Origin Hit 100% CPU
-
Zero Images Across 612 Requests Gave the Scrape Away
-
JS Detections: the one Pro-tier Cloudflare lever that actually catches HTTP-replay proxies
-
4,000 requests from 19 sources and a screen that blocked nothing
-
The 80% CPU spike that one user-agent string explained
-
The IIS Log Timestamps That Made a Working Block Look Broken
-
The rate-limiter that banned our power users: 302 to 200 redirects look like an attack