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
-
A Cloudflare 530 at 10:59 PM and a tunnel that never restarted
-
Why off-edge went quiet while stalled kept paging
-
Two Weeks of Error Pages Behind One Customer's Short Address
-
Why a green drift check on v27 hid a crawler bypass at v28
-
Why a 200 OK Killed Our Certificate Root Theory
-
Why ScheduleWizard accounted for 7 of 24 timeouts in one window
-
When the Firewall Log Stopped at v14
-
Why Our Allow Rule Allowed Nothing After the 520 Fix
-
A 92% drop in error-minutes stalled at 670 failed requests a day
-
Why 44 Stuck Certificates Were Fine and 11 Were an Outage
-
114 Domains Marked for Shutdown and the Number Nobody Expected
-
Why TXT Validation Left 956 Customer Hostnames Waiting on Someone Else's DNS
-
What a repair script cannot see in a 90-day certificate renewal cycle
-
Three Customers Out of 134 Acted on the Migration Email
-
Replaying 385 recorded builds against a monitor that paged on one HTTP read
-
We Assumed We Were Letting AI Crawlers In. We'd Been Blocking Them for Months.
-
Moving the Apex and www Records Left One Awkward Dependency
-
What an August 7 Cutover Audit Turned Up in Our Cloudflare Registrations
-
A 530 from the archive MCP that pointed at the wrong component
-
Why a 2500 ms Threshold Still Wasn't Enough to Stop the Pages
-
We Picked 150,000 Password Hash Iterations and the Platform Said No
-
Why a Forced Server Migration Did Not Become a Rewrite for Us
-
Moving Zones in Days While Customer DNS Takes Months
-
Cloudflare Rulesets API and the 2am bot swarm
-
Groups of 50 Domains and a Fallback Path With a Restored Backup
-
Why Our Own Firewall Could Not Stop the Bot Swarm at 2am
-
Why 1,282 Custom Hostnames Did Not All Get Retried
-
What We Learned Clearing 65 Expired Domains From the Backlog
-
Two alerts, 25 domains, and a monitor watching the wrong sites
-
Why Our Cloudflare Verify Tool Never Queried Public DNS for www
-
Four of 25 domains stalled in pending_validation with no error to read
-
Pinning the connection to the old server returned a catch-all certificate and a 404
-
Three to Six Months of Clicking Versus 19 Domains in a Loop
-
Cloudflare error 1001 on a site whose CNAME was correct
-
Ten Custom Hostnames Pending, Eight Active, and One Stub Worker
-
We Deleted One IIS Binding and www.customer.example.com Went to 404
-
Cloudflare Error 1014: The Cert Issued. The Page Didn't Load.
-
Why Cloudflare Full Mode Never Raised a 526 for Our Custom Domains
-
A Skip Rule on cf.client.bot and 8.44k Skips a Day
-
Why Our Custom Cert Worked on www and Failed on the Root
-
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
-
Why Per-IP Bad-Rate Found Nothing While the Origin Hit 100% CPU
-
A second #Fields line appeared mid-file with 15 columns instead of 14
-
JS Detections: the one Pro-tier Cloudflare lever that actually catches HTTP-replay proxies
-
What Silently Dropped When dxdev-blog Folded Into dxdev-landing