Hi Brad, We have been experiencing the same issue over the past week, with all our ranges seemingly affected. I reached out to AWS through abuse@amazonaws.com and peering-to@amazon.com. Below is the response I received: Thank you for your e-mail. This could have a multitude of root causes, the 403 is quite general. One cause is of course the AWS WAF either from customer specific settings or source reputation classification. I would advice to contact the site admin to see what the cause is, we do not have access to check the application level. For the reputation classification I would advice to contact for instance Neustar to confirm the current status, and work from there. However, I find it impossible to contact all the individual sites that are no longer functioning for us. If anyone has a better solution, I would appreciate your input. Thanks, Quentin. Le mer. 11 sept. 2024 à 04:50, Brad Bendy <brad.bendy@gmail.com> a écrit :
Does anyone know the best way to get a hold of Amazon and get out off the naughty list on Cloudfront? I've got some ranges that appear to be blocked totally by Cloudfront.
Thanks in advance