Skip to main content -
The Block Rule That Also Blocked a Paying Customer's Front Door
-
The bot swarms moved faster than my firewall rules
-
It Looked Exactly Like a Bot Swarm. It Was SQL Server Parameter Sniffing.
-
The customer's own scraper IS the bot swarm you've been fighting
-
Cloudflare Pro is a box of levers, not a managed service
-
Geo-blocking everywhere except the US and Canada, and the one clause that saves your SEO
-
GPTBot vs OAI-SearchBot vs ChatGPT-User: blocking the wrong one deindexes you from AI search
-
"The Whole Island Can't Reach Your Site": US Territories Are Separate Countries to Cloudflare
-
Your CDN's default bot protection is blocking Googlebot and quietly bleeding your SEO
-
Five firewall rules beat the proxy swarm, but the real bug was my blind spot
-
Operator, not IP: fingerprinting a 40,000-IP proxy swarm by its RIPE maintainer
-
Whack-a-mole is a real strategy: firewall blocks as a legitimate holding pattern
-
Your IIS Logs Start Lying the Moment Cloudflare Goes Live
-
JS Detections: the one Pro-tier Cloudflare lever that actually catches HTTP-replay proxies
-
Bot Swarm Detection: The Three-Signal Triangle That Catches What IP Reputation Misses
-
The method outlasts the patch
-
The fastest fix was blocking the bot by name
-
The decorative database: when your blocklist table isn't actually on the request path
-
The UA blocklist is the right-sized fix for an identified crawler (and the wrong one for a swarm)
-
The bot-swarm that broke the playbook: URL fan-out beats top-IP-by-volume
-
The attacker was our own redirect logic
-
The rate-limiter that banned our power users: 302 to 200 redirects look like an attack
-
The SSL bug was easy. The bot traffic made it a day-long incident.