Akamai/HollisterCo

Wed Dec 18 21:57:40 UTC 2019

I thank you for your efforts. 

----- 
Mike Hammett 
Intelligent Computing Solutions 
http://www.ics-il.com 

Midwest-IX 
http://www.midwest-ix.com 

----- Original Message -----

From: "Jared Mauch" <jared at puck.nether.net> 
To: "Mike Hammett" <nanog at ics-il.net> 
Cc: nanog at nanog.org 
Sent: Wednesday, December 18, 2019 3:56:17 PM 
Subject: Re: Akamai/HollisterCo 

I’ve had a hard time internally getting people to answer questions around this or how to properly escalate what appears to be blocking related issues. I’m honestly at wits end with them. 

I’ll give you these links: 

https://community.akamai.com/customers/s/article/Why-is-Akamai-Blocking-Me-Part-3-Partners-Performing-Web-Scraping-Activity?language=en_US 
https://www.akamai.com/us/en/clientrep-lookup/ 

The reality is when you end up behind a NAT pool or shared IP set, this is entirely possible someone (or thing) is doing malicious activity. I’ve asked the teams to improve the errors presented to users in this case, so perhaps it will get better. 

If you have a specific reference ID you get back, you can send it to me in e-mail (text, no images please) and I’ll look it up to see what can be found. 

But this also falls into the category - we are performing the action based on our customer request/configuration. 

- Jared 

> On Dec 18, 2019, at 4:29 PM, Mike Hammett <nanog at ics-il.net> wrote: 
> 
> That is a common issue eyeball ISPs have with CDNs and security companies. 
> 
> The obvious technical contact is the CDN or security company, but they always redirect you to their client because they're "just doing what their client asked". Yes, please, reach out to Hollister's customer service department with a request to fix their web site (or tell you why they won't). See how far that gets you. Meanwhile, go buy some of their tacky apparel. 
> 
> On the "just doing what their client asked", what *IS* it that the client asked? Surely Hollister didn't develop some personal spite for Dmitriy's client and bock their IP address. No, more likely is that some algorithm (rightly or wrongly) lumped Dmitriy's client's IP in a list of bad actors for some reason and Hollister has chosen to block that category of bad actor. Hollister would be equally clueless as to what is actually happening. 
> 
> What the CDNs and security companies should respond with is something to the effect of, "We see 123.456.789.123 doing XYZ bad activity and it needs to stop before being allowed in." Ya know... the same way nearly every SPAM RBL works. You can then kill two birds with one stone: Dmitriy's client can now buy bad shirts and Dmitriy's client fixes whatever exploits are happening from their network. 
> 
> 
> 
> ----- 
> Mike Hammett 
> Intelligent Computing Solutions 
> http://www.ics-il.com 
> 
> Midwest-IX 
> http://www.midwest-ix.com 
> 
> See More from Dmitriy Vaynshteyn [infiniwiz] 
> 
>  
> 
> See More from Dmitriy Vaynshteyn [infiniwiz] 
> 
> or making a referral. 
>  
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20191218/b9c8cfbf/attachment.html>