Hi.
Our experience from last month was quite similar to what others have
already described. Based on our tests all the allocations associated
with our ASN were added to "HostingProviderIPList". At first we tried
to reach the AWS by e-mail, but received no response. Once we opened a
ticket(we are
Endured a similar problem last year. The company I was with migrated
prod to Global Accelerator, ALBs, and WAF with Shield Advanced on an
accelerated timeline. Several of our customer networks were blocked in
AWS's default blocklists.
The path to resolution was meeting with our AWS account
Yes.
our network is a mix of content and eyeballs and they listed the whole
thing. This has prevented the local school district from using their
text to speech application (for their deaf students) as well as others.
This has also affected the local library and residences.
It's a PITA.
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
Hi All,
I just became aware that AWS has a list of hosting IP providers and that list
is blocked by their WAF? (!?!?). None of my VM or colo customers can reach
anything in AWS, such as Docker, Twilio, etc. I confirmed through source
routing that when I access it using one of my peering
5 matches
Mail list logo
