Prefix hijacking, how to prevent and fix currently

Suresh Ramasubramanian ops.lists at gmail.com
Fri Aug 29 03:27:35 UTC 2014


In this case.. Google that ASN name. Then go upstream.
 On 29-Aug-2014 8:56 am, "Faisal Imtiaz" <faisal at snappytelecom.net> wrote:

> I would say, start off with the NOC Contact
>
> http://bgp.he.net/AS43239#_whois
>
> It is most likely that someone has fat-fingered the IP space..
>
>
> Faisal Imtiaz
> Snappy Internet & Telecom
>
> ----- Original Message -----
> > From: "Tarun Dua" <lists at tarundua.net>
> > To: nanog at nanog.org
> > Sent: Thursday, August 28, 2014 12:55:25 PM
> > Subject: Prefix hijacking, how to prevent and fix currently
> >
> > AS Number 43239
> > AS Name SPETSENERGO-AS SpetsEnergo Ltd.
> >
> > Has started hijacking our IPv4 prefix, while this prefix was NOT in
> > production, it worries us that it was this easy for someone to hijack
> > it.
> >
> > http://bgp.he.net/AS43239#_prefixes
> >
> > 103.20.212.0/22 <- This belongs to us.
> >
> > 103.238.232.0/22 KNS Techno Integrators Pvt. Ltd.
> > 193.43.33.0/24 hydrocontrol S.C.R.L.
> > 193.56.146.0/24 TRAPIL - Societe des Transports Petroliers par Pipeline
> >
> > Where do we complain to get this fixed.
> >
> > -Tarun
> > AS132420
> >
>


More information about the NANOG mailing list