AbuseIO Users

Even though our project is fairly new, a lot of internet service providers and hosting companies have shown their interest in using AbuseIO to handle their abuse reports. Want to share your experience with AbuseIO? Send over your use case by Contacting us!

Although many larger international webhosts/ISPs already have custom build infrastructure in place to automate their abuse report handling, we still find a lot of companies that handle such reports manually. It’s great to finally see a free opensource tool consolidating these reports, so any webhost/ISP both small and large can get immediate insight in the abuse they cause. Being able to pro-actively shutdown abuse sources before they can escalate has significant benefits both for the service provider and the internet in general. With abuse.io, there is virtually no investment in time and resources required, resulting in direct and indirect cost savings

With AbuseIO we have the ability to notify customers automatically within one hour after receipt of a abuse report. We noticed that the the time that abuse took place was drastically reduced and is useally solved within 1 to 2 business days. Having historical data will make it possible to get a better picture of the usage of that internet connection so we can act on it accourdingly. Last but not least the proactive side of AbuseIO will help our endusers close down vulnerable servers before they are actually abused with the reporting of known problems.

Abuse handling is a labor intensive and boring process, so we started thinking about a way to automate this process so abuse reports could be sent to the corresponding customers automatically in order to reduce the load on our support desk. Unfortunately we quickly found out that good quality open-source solutions are non-existent and commercial offerings are simply too expensive.

Since we are unable to invest the amount of hours required to develop such a system on our own we thought the best way forward is to combine our efforts with others. At around the same time we first heard about this project and realised it was just what we needed. So we started to contribute code to accelerate its development and add the features and feeds we thought were missing. The result is what we’ve called AbuseIO and we are committed to improving AbuseIO even further in the future.