About RIPE NCC | Contact  | Search | Sitemap    
Homepage RIPE NCC  
Routing Information Service
     
RIS:
RIPE NCC Navigation Ends
RIS Home Page
RIS Raw Data
Documentation
Analysis using RIS
Contact Us
Send Feedback
RIPE NCC Navigation Ends
Next Section

All comments and suggestions to improve our tools are welcome, please let us know.

De-Bogonising New Address Blocks Report - 20080926

Previous day's report | Next day's report | Monthly view

Note: The results presented in this report are based on a few assumptions. Therefore, please keep in mind that the list of filtering ASes shown here might not be absolutely accurate or complete. For more information on the assumptions and how the report is compiled, please read below.

Summary

IPv4

Anchor Prefix: 84.205.83.0/24      
Size of set: 98 ASes



Visibility estimation96 (+- 0) out of 98 ASes (97 %)
Filtering ASes (2)1273 6730
Uncertain ASes (part of a filtering as-path segment)0




Visibility estimation73 (+- 4) out of 98 ASes (74 %)
Filtering ASes (21)2895 6730 7018 8331 8359 8402 8419 10429 16150 20483 20562 24963 28917 29636 30126 30890 31323 34245 39792 39821 44334
Uncertain ASes (part of a filtering as-path segment)8
Filtering segments (at least one filtering AS):[ 24963 20562 ] [ 30126 2200 ] [ 30126 2200 1273 ] [ 34102 3216 20562 ] [ 42109 41965 41877 12389 ]




Visibility estimation93 (+- 0) out of 98 ASes (94 %)
Filtering ASes (5)1273 6730 8419 29636 34245
Uncertain ASes (part of a filtering as-path segment)0




Visibility estimation96 (+- 0) out of 98 ASes (97 %)
Filtering ASes (2)1273 6730
Uncertain ASes (part of a filtering as-path segment)0




Visibility estimation98 (+- 0) out of 98 ASes (100 %)
Filtering ASes (0)
Uncertain ASes (part of a filtering as-path segment)0


Details

Y - Non-filtering
N - Filtering
U - Uncertain (part of a filtering AS-path segment)

IPv4

AS Number41.223.236.0 /2295.192.0.0 /1695.255.248.0 /21186.128.0.0 /16186.127.248.0 /21112.0.0.0 /24112.50.0.0 /21112.255.0.0 /16113.0.0.0 /24113.50.0.0 /21113.255.0.0 /16
174YYYYYUUUUUU
286YYYYYUUUUUU
513YYYYYUUUUUU
701YYYYYUUUUUU
1239YYYYYUUUUUU
1273NUNNYUUUUUU
1280YYYYYUUUUUU
1299YYYYYUUUUUU
1853YYYYYUUUUUU
2119YYYYYUUUUUU
2200YUYYYUUUUUU
2497YYYYYUUUUUU
2516YYYYYUUUUUU
2857YYYYYUUUUUU
2895YNYYYUUUUUU
2914YYYYYUUUUUU
3216YUYYYUUUUUU
3257YYYYYUUUUUU
3269YYYYYUUUUUU
3320YYYYYUUUUUU
3356YYYYYUUUUUU
3549YYYYYUUUUUU
4589YYYYYUUUUUU
4777YYYYYUUUUUU
5392YYYYYUUUUUU
5413YYYYYNNNNNN
6453YYYYYUUUUUU
6461YYYYYUUUUUU
6667YYYYYUUUUUU
6695YYYYYUUUUUU
6730NNNNYUUUUUU
6762YYYYYNNNNNN
6939YYYYYUUUUUU
7018YNYYYUUUUUU
7575YYYYYUUUUUU
8167YYYYYUUUUUU
8331YNYYYUUUUUU
8359YNYYYNNNNNN
8402YNYYYUUUUUU
8419YNNYYUUUUUU
8434YYYYYUUUUUU
8447YYYYYUUUUUU
8596YYYYYUUUUUU
8763YYYYYUUUUUU
8881YYYYYUUUUUU
8928YYYYYUUUUUU
9002YYYYYUUUUUU
10429YNYYYUUUUUU
12350YYYYYUUUUUU
12389YUYYYUUUUUU
12637YYYYYUUUUUU
12779YYYYYUUUUUU
12859YYYYYUUUUUU
12956YYYYYUUUUUU
12989YYYYYNNNNNN
13030YYYYYNNNNNN
13237YYYYYUUUUUU
14361YYYYYUUUUUU
16150YNYYYUUUUUU
16735YYYYYUUUUUU
17379YYYYYUUUUUU
19089YYYYYUUUUUU
19151YYYYYUUUUUU
20483YNYYYUUUUUU
20562YNYYYNNNNNN
20640YYYYYUUUUUU
20932YYYYYNNNNNN
21202YYYYYUUUUUU
22548YYYYYUUUUUU
22691YYYYYUUUUUU
24963YNYYYUUUUUU
25091YYYYYUUUUUU
25560YYYYYUUUUUU
26943YYYYYNNNNNN
27664YYYYYUUUUUU
28895YYYYYUUUUUU
28917YNYYYUUUUUU
28929YYYYYUUUUUU
29222YYYYYUUUUUU
29449YYYYYUUUUUU
29636YNNYYUUUUUU
30126YNYYYUUUUUU
30132YYYYYNNNNNN
30890YNYYYUUUUUU
31323YNYYYUUUUUU
31477YYYYYUUUUUU
34102YUYYYUUUUUU
34245YNNYYUUUUUU
34695YYYYYUUUUUU
35054YYYYYUUUUUU
39792YNYYYUUUUUU
39821YNYYYUUUUUU
39912YYYYYUUUUUU
41853YYYYYUUUUUU
41877YUYYYUUUUUU
41965YUYYYUUUUUU
42109YUYYYUUUUUU
44334YNYYYUUUUUU

Methodology

The anchor and debogon prefixes are announced by the same router (RRC3) and AS number (AS12654). The AS-path from any point on the Internet towards the announcing router should therefore be the same for both prefixes. If this is not the case, it is assumed that debogon prefix filtering is being applied somewhere on the path.

The collection points of the AS-paths used in this report are all the RIS RRCs. Therefore, ASes covered in this report are only those seen in the AS-paths between the collection points and the anchor prefix.

To perform this report, all the AS-paths towards the anchor and the debogon prefixes are compared:

  • ASes appearing on matching anchor and debogon paths are labelled non-filtering.
  • From the unmatching AS-paths, all ASes labeled as non-filtering are removed, generating a list of AS-path segments.
  • If a segment consists of only one AS, the AS is labelled filtering.
  • All remaining ASes are labelled uncertain.

If an AS is labelled uncertain, it means that it is part of an AS-path segment in which at least one AS is considered to be filtering, but it is unconclusive which one(s).

The visibility plots show the percentage of how many ASes are estimated to be non-filtering. The grey area represents the indeterminacy caused by the ASes considered uncertain.

 

Next Section
     About RIPE NCC | Site Map | LIR Portal | About RIPE | Contact | © RIPE NCC. All rights reserved.
RIPE NCC Homepage LIRPortal RIPE Community