Cloudflare is up and responding in 622 ms.
Checked 3 minutes ago · monitored around the clock · cloudflare.com
24-hour uptime: 100%
Is it Cloudflare, or is it you? Test your own connection against Cloudflare — one verdict in 10 seconds.Cloudflare is up and responding in 622 ms. That reading is from itsnotyou's monitoring servers, 3 minutes ago.
It can be either — that's the hard part. The status on this page is measured from itsnotyou's monitoring servers, so Cloudflare can look healthy here while your own connection is the real problem. The itsnotyou test checks both at once and returns a single verdict in about 10 seconds.
A slow Cloudflare usually comes down to one of two things: Cloudflare's own servers are responding slowly — itsnotyou measures time to first byte, and anything over 1500 ms is flagged as slow — or your local connection is the bottleneck. Running the test tells the two apart.
Cloudflare is probed every few minutes, around the clock, from itsnotyou's monitoring servers. The verdict and the 24-hour response-time history on this page update automatically.
No. Error 522 means Cloudflare reached its edge fine but the website's own origin server did not answer in time. Cloudflare is working; the site behind it is not. The same goes for 521 (origin refused) and 523 (origin unreachable).