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 - 20080907

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: 104 ASes



Visibility estimation103 (+- 0) out of 104 ASes (99 %)
Filtering ASes (1)2118
Uncertain ASes (part of a filtering as-path segment)0




Visibility estimation103 (+- 0) out of 104 ASes (99 %)
Filtering ASes (1)2118
Uncertain ASes (part of a filtering as-path segment)0




Visibility estimation103 (+- 0) out of 104 ASes (99 %)
Filtering ASes (1)2118
Uncertain ASes (part of a filtering as-path segment)0




Visibility estimation91 (+- 6) out of 104 ASes (87 %)
Filtering ASes (6)1930 2118 3741 6881 7018 9304
Uncertain ASes (part of a filtering as-path segment)13
Filtering segments (at least one filtering AS):[ 3.5 1125 1103 ] [ 4608 1221 4637 ] [ 16186 31283 ] [ 42109 44505 41877 20771 9121 ]




Visibility estimation91 (+- 6) out of 104 ASes (87 %)
Filtering ASes (6)1930 2118 3741 6881 7018 9304
Uncertain ASes (part of a filtering as-path segment)13
Filtering segments (at least one filtering AS):[ 3.5 1125 1103 ] [ 4608 1221 4637 ] [ 16186 31283 ] [ 42109 44505 41877 20771 9121 ]


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
3.5YYYUUUUUUUU
286YYYYYUUUUUU
513YYYYYUUUUUU
1103YYYUUUUUUUU
1125YYYUUUUUUUU
1221YYYUUUUUUUU
1239YYYYYUUUUUU
1280YYYYYUUUUUU
1299YYYYYUUUUUU
1853YYYYYUUUUUU
1930YYYNNUUUUUU
2118NNNNNUUUUUU
2119YYYYYUUUUUU
2497YYYYYUUUUUU
2516YYYYYUUUUUU
2857YYYYYUUUUUU
2895YYYYYUUUUUU
2914YYYYYUUUUUU
3257YYYYYUUUUUU
3269YYYYYUUUUUU
3356YYYYYUUUUUU
3549YYYYYUUUUUU
3741YYYNNUUUUUU
4589YYYYYUUUUUU
4608YYYUUUUUUUU
4637YYYUUUUUUUU
4777YYYYYUUUUUU
5392YYYYYUUUUUU
5413YYYYYNNNNNN
5430YYYYYUUUUUU
6453YYYYYUUUUUU
6461YYYYYUUUUUU
6667YYYYYUUUUUU
6695YYYYYUUUUUU
6762YYYYYNNNNNN
6881YYYNNUUUUUU
6939YYYYYUUUUUU
7018YYYNNUUUUUU
7575YYYYYUUUUUU
8331YYYYYUUUUUU
8359YYYYYNNNNNN
8402YYYYYUUUUUU
8434YYYYYUUUUUU
8447YYYYYUUUUUU
8596YYYYYUUUUUU
8631YYYYYUUUUUU
8763YYYYYUUUUUU
8881YYYYYUUUUUU
9002YYYYYUUUUUU
9121YYYUUUUUUUU
9304YYYNNUUUUUU
12350YYYYYUUUUUU
12637YYYYYUUUUUU
12779YYYYYUUUUUU
12859YYYYYUUUUUU
12956YYYYYUUUUUU
12989YYYYYNNNNNN
13030YYYYYNNNNNN
13237YYYYYUUUUUU
14361YYYYYUUUUUU
16150YYYYYNNNNNN
16186YYYUUUUUUUU
16735YYYYYUUUUUU
19089YYYYYUUUUUU
19151YYYYYUUUUUU
20483YYYYYUUUUUU
20562YYYYYNNNNNN
20640YYYYYUUUUUU
20771YYYUUUUUUUU
20932YYYYYNNNNNN
20965YYYYYUUUUUU
21202YYYYYUUUUUU
22548YYYYYUUUUUU
22691YYYYYUUUUUU
24963YYYYYUUUUUU
25091YYYYYUUUUUU
25560YYYYYUUUUUU
26943YYYYYNNNNNN
27664YYYYYUUUUUU
28895YYYYYUUUUUU
28917YYYYYUUUUUU
28929YYYYYUUUUUU
29222YYYYYUUUUUU
29449YYYYYUUUUUU
30126YYYYYUUUUUU
30132YYYYYNNNNNN
30890YYYYYUUUUUU
31283YYYUUUUUUUU
31323YYYYYUUUUUU
31477YYYYYUUUUUU
34102YYYYYUUUUUU
34245YYYYYUUUUUU
34347YYYYYUUUUUU
34695YYYYYUUUUUU
35054YYYYYUUUUUU
39202YYYYYUUUUUU
39792YYYYYUUUUUU
39821YYYYYUUUUUU
39912YYYYYUUUUUU
41853YYYYYUUUUUU
41877YYYUUUUUUUU
42109YYYUUUUUUUU
44334YYYYYUUUUUU
44505YYYUUUUUUUU

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