Constant Abuse Reports / Borderline Spamming from RiskIQ

Thu Apr 16 04:53:23 UTC 2020

We’ve got a 24/7 NOC and respond to abuse reports in either real-time in as close to real-time as we can, I’d send another message if it went 24 hours without a reply too. We also have a ticket system that replies immediately so they know the e-mail went through, and we track it like a real company that does real things.

-Ben

> On Apr 13, 2020, at 10:46 AM, Kushal R. <kushal.r at h4g.co> wrote:
> 
> 
> All abuse reports that we receive are dealt within 48 business hours. As far as that tweet is concerned, it’s pending for 16 days because they have been blocked from sending us any emails due to the sheer amount of emails they started sending and then our live support chats.
> 
> We send our abuse reports to, but we don’t spam them to every publicly available email address for an organisation, it isn’t difficult to lookup the Abuse POC for an IP or network and just because you do not get a response in 24 hours does not mean you forward the same report to 10 other email addresses. Similarly twitter isn’t a place to report abuse either. 
> 
> 
>> On Apr 13, 2020 at 9:37 PM, <Rich Kulawiec> wrote:
>> 
>>       
>>  On Mon, Apr 13, 2020 at 07:55:37PM +0530, Kushal R. wrote:  >  We understand these reports and deal with them as per our policies and timelines but this constant spamming by them from various channels is not appreciated. Quoting from: https://twitter.com/RiskIQ_IRT/status/1249696689985740800 which is dated 9:15 AM 4/13/2020: 5 #phishing URLs on admin12.find-textbook[.]com were reported to @Host4Geeks (Walnut, CA) from as far back as 16 days ago, and they are all STILL active 16 days is unacceptable. If you can't do better than that -- MUCH better -- then shut down your entire operation today as it's unworthy of being any part of the Internet community. ---rsk  
>>      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20200415/1488e126/attachment.html>