I am encountering 503 errors on my Cloudflare protected site.
The error names Cloudflare in the html and all the tips I can find suggest contacting them via support ticket to fix, but this is for one of my free account clients so I can’t.
Any ideas on how to fix?
I ran a trace (another forum suggestion) with these results:
Tracing route to [my url] [172.67.174.63]
over a maximum of 30 hops:
1 62 ms 62 ms 61 ms 10.28.18.1
2 62 ms 62 ms 62 ms 154.6.151.1
3 62 ms 63 ms 64 ms 100.64.130.129
4 63 ms 63 ms 63 ms superloop156970.me1.as9280 .net .au [202.60.93.57]
5 74 ms 74 ms 75 ms bundle-ether32.bdr02-ipt-530colli-mel.au.superloop .net .co [103.200.13.142]
6 75 ms 74 ms 75 ms bundle-ether34-106.bdr02-ipt-47bourke-syd.au.superloop .net .co [103.200.13.112]
7 75 ms 75 ms 75 ms bundle-ether32.bdr02-ipt-639garde-syd.au.superloop .net .co [103.200.13.70]
8 75 ms 80 ms 75 ms 27.122.122.15
9 75 ms 75 ms 75 ms 172.68.208.3
10 75 ms 74 ms 74 ms 172.67.174.63
Added info:
I ran a status check on httpstatus.io/ and the url earthsports.club showed too many redirects. It is hosted on elementor and then redirects through Cloudflare. Nothing else, it’s a very early site.
For those experiencing issues, can you share any more information about your location (hit example.com/cdn-cgi/trace replacing example.com with your domain)? Are you all using APO?
Started getting this today too not long ago on my free plan for the first time. Webserver has almost no load at all, and the 503 page is tagged with Cloudflare. Happening a lot now. Here’s partial output from /cdn-cgi/trace.
Sorry for the issues, the team is aware and investigating. cloudflarestatus.com is being updated and will reflect progress as the team addresses the issue.