Cloudflare blog broken with 503, only on Newsblur

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?

4 Likes

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.

1 Like

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?

Unfortunately, afterwards only 503 again :frowning:

Hopefully. I have a few feeds that are served on Cloudflare that are 503ing. I was going to wait a bit before complaining again.

As mentioned before, I can escalate within Cloudflare if you don’t get anywhere.

1 Like

no improvement yet. maybe it’s a good time to accept @thedaveCA 's offer to escalate and speed things up?

We’ll it’s Monday after thanksgiving weekend so I’d give them until EOW

@thedaveCA I think it’s probably time, if you haven’t already. Thanks!

I reached out again today, so let’s hope that helps

1 Like

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).

Hey @samuelclay, I’m seeing 503 too.
Have you heard anything from Cloudflare?

This looks to be fixed!

2022-01-10 17:46:00 OK (200)
2022-01-10 17:13:00 OK (200)
2022-01-10 16:41:14 OK (200)
2022-01-10 16:08:05 OK (200)
2022-01-09 14:47:35 HTTP Error (503)
2022-01-09 14:41:47 HTTP Error (503)
2022-01-09 14:41:35 HTTP Error (503)
2022-01-09 14:41:16 HTTP Error (503)

Nice, I saw somebody tweeted at them earlier today. Wonder if that did it?