De-Bogonising New Address Blocks
Report - 20040615

Previous day's report | Next day's report

Summary

Details

Column Descriptions: AS Number - autonomous system numbers seen anywhere in a path to any of the prefixes; Sees ... - a tick (or 'Y' if viewing this without graphics) indicates that we see the specified prefix with this AS somewhere in the AS Path; Peers ... - a tick here indicates that this AS is seen as an immediate neighbour of the AS announcing the specified prefix.

AS Number	Sees 85.192.0.0 /16	Sees 85.255.248.0 /21	Sees 86.192.0.0 /16	Sees 86.255.248.0 /21	Sees 87.192.0.0 /16	Sees 87.255.248.0 /21	Sees 88.192.0.0 /16	Sees 88.255.248.0 /21	Sees 195.80.239.0 /24	Sees 193.0.0.0 /21	|	Peers 85.192.0.0 /16	Peers 85.255.248.0 /21	Peers 86.192.0.0 /16	Peers 86.255.248.0 /21	Peers 87.192.0.0 /16	Peers 87.255.248.0 /21	Peers 88.192.0.0 /16	Peers 88.255.248.0 /21	Peers 195.80.239.0 /24	Peers 193.0.0.0 /21
174											|
286											|
297											|
513											|
559											|
702											|
1103											|
1221											|
1299											|
1853											|
2516											|
2914											|
3291											|
3320											|
3333											|
3344											|
3356											|
3549											|
3741											|
4608											|
4637											|
4777											|
5400											|
5511											|
7018											|
8210											|
8289											|
8333											|
8434											|
8447											|
8468											|
8928											|
9177											|
12654											|
12793											|
12859											|
13030											|
13129											|
13237											|
13285											|
15703											|
20562											|
20965											|
25232											|
25396											|

Some Explanations...

Not seeing the RIPE NCC's prefix 193.0.0.0/21 is probably caused by seeing one of the other prefixes from a peer which does not provide the RIS with a full feed.

Seeing the /16 but not the /21 in the new allocations is probably caused by incorrect prefix length based filtering somewhere along the line.

Seeing the newly allocated prefixes but not the 195.80.239.0/24 prefix is probably caused by filtering based on the RIR's minimum allocation size somewhere.

How these statistics were gathered

For each of the prefixes (85.192.0.0/16 85.255.248.0/21 86.192.0.0/16 86.255.248.0/21 87.192.0.0/16 87.255.248.0/21 88.192.0.0/16 88.255.248.0/21 195.80.239.0/24 193.0.0.0/21), all RIB entries and Updates for a single day were extracted from the RIS database and from this a list of all AS Paths seen for each prefix was generated. We class an AS as "seeing" one of the prefixes if that AS appears anywhere in an AS Path to that prefix. That an AS is shown as not seeing a particular prefix only indicates that this doesn't appear in the RIS.

All AS Paths...