Claim the Cloudflare page

Claiming is free. You prove you work at Cloudflare with an email address at cloudflare.com; Friction sends a link there.

27 recent reports from users of Cloudflare
45 separate source threads
2012–2026 the years they cover
Most recurring theme: Challenges falsely block legitimate users, 10 threads

These are public today, under your product's name. A reply from Cloudflare sits under the report, on the record, marked as verified at cloudflare.com: the next person who reads it sees you answered.

What Cloudflare would post on the top report

Built on the report people repeat most on this page. Nothing appears until you post it.

A first reply, under the report

A board post, with a public status

Cloudflare challenges affect privacy-conscious browser users Planned

Planned: Scoped for the next release.

A changelog entry, linked to the report

Fixed: Cloudflare challenges affect privacy-conscious browser users

Resolves: Cloudflare challenges affect privacy-conscious browser users

Show your users where to give feedback

Put a Friction badge in your README, docs site or footer. It takes one pasted line, it is free, and it sends people straight to where they can report a problem or ask for a feature on Cloudflare.

Docs or README footer: sends readers to give feedback on Cloudflare

Show the code

[![Report a problem or request a feature for Cloudflare](https://friction.grain64.com/badge/cloudflare.svg?form=cta)](https://friction.grain64.com/p/cloudflare/submit/?utm_source=badge&utm_medium=embed&utm_content=cta)

<a href="https://friction.grain64.com/p/cloudflare/submit/?utm_source=badge&utm_medium=embed&utm_content=cta"><img src="https://friction.grain64.com/badge/cloudflare.svg?form=cta" alt="Report a problem or request a feature for Cloudflare" height="20"></a>

For researchers and write-ups: the live count for Cloudflare