Lots of people are encountering this, yes.
You can try opening a case yourself, and hope it gets to someone with a clue. If you don't have a support contract with them, your chances are almost 0. If you do, your chances are slightly higher, but not by much. most likely they will just tell you to 'contact the owner of the thing you're trying to access and have them customize their WAF rules'.
AWS is doing some REALLY dumb things. For example, if your ASN announces a single prefix that a 3rd party provider classifies as 'hosting provider' , AWS will flag EVERY prefix from that ASN as 'hosting provider', which are all blocked in the default managed WAF rules. They also won't tell you in any circumstance (even if you're a customer who is paying for support) who that 3rd party provider IS.
Expect a lot of hassle to get this fixed, if you ever can.