According to Newsblur UI, the Cloudflare Blog (https://blog.cloudflare.com/rss/) returns HTTP 503 only. If I try it with curl from my machine, I get a proper 200 with content that validates on validator.w3.org. Also, direct fetching from validator.w3.org works as well.
I have no idea what Newsblur could be doing differently to cause the 503. Maybe some blocking on Cloudflare side? @samuelclay, can you see some more helpful details in the response directly on your servers?
I worked with a couple folks at Cloudflare about a year ago to get NewsBlur placed on the allow list. That seems to have regressed, so I reached out to my contacts and will let you know when I hear back. Also, please let me know if it starts working again.
Just a short status update: at 2021-11-24 04:01:02, Newsblur once got a 301 redirect (can’t see the destination in the UI). Maybe somebody at Cloudflare is working on it?
A week or so ago I filed a support ticket from my paid account – they did not understand that I was describing an issue between their marketing blog and a third-party service I don’t control (NewsBlur).
I wonder what is triggering it? Cloudflare has a “known bots” thing that should apply to requests to feeds, and I have a few sites that have feeds that load through Cloudflare that work fine.
Individual sites might have configured challenges or other protection without exempting calls to their feed, but this would tend to hit all feed readers equally and most sites (at least, those with analytics and anyone that knows how to read 'em) would notice the loss of traffic.