On 9/27/16 5:46 PM, Alistair Mackenzie wrote:
> 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?
I'm not sure why you would bother obscuring it. What purpose does that
serve in furthering the discus
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
I've seen this with increasing frequency in the last 8-12 months, more with
ASNs that were either expired/unallocated. Spammers seem to be snatching
them up and hijacking IPs via bilateral peering to make it harder to
notice.
I've found it very difficult in some cases to get traction from IXes or
On Tue, Sep 27, 2016 at 8:18 PM, Alistair Mackenzie 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 yo
On Tue, Sep 27, 2016 at 8:18 PM, Alistair Mackenzie wrote:
> 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 point
> that it was valid however this is no longer the case.
>
> The network is sing
5 matches
Mail list logo
