520 errors on Wordpress

Hi there,

Unfortunately, we appear to be having the same 520 error as many others are getting. The origin web server produces no errors, and refreshing multiple times seems to get rid of the error for a few minutes, and then they’re back. These 520 errors have been plaguing us for a few days now. I have attached a sample of a server with these issues.

uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.63 Safari/537.36 Edg/93.0.961.38
  1    11 ms     5 ms     6 ms
  2     *        *        *     Request timed out.
  3    16 ms    16 ms    17 ms  hers-core-2b-xe-830-0.network.virginmedia.net []
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    17 ms    18 ms    16 ms  tele-ic-7-ae2-0.network.virginmedia.net []
  7    19 ms    18 ms    16 ms  2-14-250-212.static.virginm.net []
  8    20 ms    17 ms    16 ms

I also have a ticket ID: 2248572

Please see Intermittent Error 520, host says nothing in logs, Always Online off - #45 by matteo

Due to the number of 520s being reported in similar circumstances, we are escalating the issue to Cloudflare Support. The original incident should have been resolved and your issue may well be unrelated.

We recommend checking these troubleshooting tips, if you haven’t already.

As you have posted a ticket number, we have added that to the escalation.

To enable efficient troubleshooting by support, please ensure you have included the following on the ticket:

  • example URL(s) where you are seeing the error
  • Ray IDs from the 520 pages
  • output from a traceroute from any impacted user
  • output of example.com/cdn-cgi/trace - replace example.com with the affected domain.
  • Also include two HAR file(s) : one detailing your request with Cloudflare enabled on your website and the other with Cloudflare temporarily disabled - see How do I temporarily deactivate Cloudflare ?

So as part of https://community.cloudflare.com/t/random-520-errors/ we fixed an issue with origins silently ending a keepalive connection that was causing very rare 520 errors.

Thus we recommend testing again - if you still see 520s - make sure you follow the guidance in our community tip here: