These errors / blocks are due to Akamai customers using tools and data provided by Akamai to handle things like geo-restriction and (perceived) DoS attacks. You do have to deal with the Akamai customer for these issues, and some of our NAT addresses have been blocked by Macy's in the past, probably due to a large number of Macy's shoppers being behind a single IPv4 address... Here is the Akamai Client Reputation check: https://www.akamai.com/us/en/clientrep-lookup/ That tool will only check the source IP address from which it is accessed. There is no way to check on another address. Jon On Fri, May 23, 2025 at 11:00 AM Jason Canady via NANOG < nanog@lists.nanog.org> wrote:
I have been told that before, but it's clear that Akamai knows how to fix it because it's across multiple customers of theirs.
On 5/23/25 10:44, Niels Bakker via NANOG wrote:
* nanog@lists.nanog.org (Jason Canady via NANOG) [Fri 23 May 2025, 16:34 CEST]:
Sounds like an Akamai issue blocking Cogent IPs. Jared Mauch might be able to help you here.
Akamai doesn't block Cogent IPs, as a CDN Akamai implements the security policy chosen by the respective customer.
-- Niels.