Cloudflare sits between millions of websites and the people who visit them, filtering out bad traffic and serving copies of pages from servers close to each visitor. That position makes sites faster and safer, and it also means that when Cloudflare fails, a large slice of the web fails with it.
Where Cloudflare sits
Without Cloudflare, a browser looks up a site's domain, gets the IP address of the site's own server (the 'origin'), and connects straight to it. When a site turns on Cloudflare's proxy, the domain's DNS answers with Cloudflare's addresses instead. The browser connects to a nearby Cloudflare data centre, and Cloudflare opens its own connection to the origin only when it needs to.
This arrangement is called a reverse proxy: a server that stands in front of other servers and answers on their behalf. A forward proxy works for the client, like an office proxy that all staff traffic leaves through. A reverse proxy works for the website. Because every request passes through it, the proxy can inspect, block, cache or rewrite traffic before the origin ever sees it.
Here is one visitor's request going through the proxy, then a bot that never gets past it:
A request through Cloudflare: checked, cached, blocked
Step 1 of 10: A visitor asks for a page. DNS points the name at Cloudflare, so the request lands at the nearest edge.
Wondering how this was made? How we make these