Thanks for this, it shows as apnic|ZZ|ipv4|103.***.***.0|1024|20160927|reserved||e-stats I expect this still stands with it being reserved? William, it's 100% an apnic range and shows no org and is registered to the APNIC Hostmaster. This applies for both the ASN and the address space. On 28 September 2016 at 01:28, William Herrin <bill@herrin.us> wrote:
On Tue, Sep 27, 2016 at 8:18 PM, Alistair Mackenzie <magicsata@gmail.com> wrote:
I've come across a network which seem to be getting transit yet both the ASN and IP space is not allocated by the RIR.
Hi Alistair,
There is still unicast address space that isn't allocated by any RIR?
Seriously though, check all your bases. Is not the space unallocated by all RIRs or just the one you expect to hold it? If you have a transit provider that's not playing by the rules, contact their transit providers to complain and if you still don't get satisfaction, I'd name and shame the lot of them. Failure to filter bad actors is how prefix hijacking happens.
Regards, Bill Herrin
-- William Herrin ................ herrin@dirtside.com bill@herrin.us Owner, Dirtside Systems ......... Web: <http://www.dirtside.com/>
On 28 September 2016 at 01:36, George Michaelson <ggm@algebras.org> wrote:
check if the block is in this file.
http://labs.apnic.net/delegated-nro-extended
If not, then the block is hijacked or being abused.
the file format is a bit obscure: the ipv4 record is base-ip|hostcount but converting that to prefix length is pretty simple.
-G
Hi,
I've come across a network which seem to be getting transit yet both the ASN and IP space is not allocated by the RIR. It does appear at some
On Wed, Sep 28, 2016 at 10:18 AM, Alistair Mackenzie <magicsata@gmail.com> wrote: point
that it was valid however this is no longer the case.
The network is single homed and I tried asking the transit provider what their policy was on this but got no answer.
Has anyone seen anything like this? What has happened in the past with things like this?
Thanks, Alistair