But Cloudflare has already been treating Newsblur as a Verified Bot for a long time, at least since the spring: https://radar.cloudflare.com/traffic/verified-bots
Could the 403s be triggered by a misbehaving fetcher?
Or could it be that Hetzner suffers from ongoing reputational issues so great they take precedence over Verified Bots?
Having established that 403s are impacting only Newsblur should make it easier for @samuelclay and the team to root cause it.