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

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



Visibility estimation114 (+- 0) out of 115 ASes (99 %)
Filtering ASes (1)6730
Uncertain ASes (part of a filtering as-path segment)0




Visibility estimation86 (+- 2) out of 115 ASes (74 %)
Filtering ASes (26)2852 2895 5392 5511 6067 8331 8402 8419 8468 12637 12779 20483 21202 28895 28917 28929 29636 30844 31323 31477 34245 34695 39202 39792 39821 44505
Uncertain ASes (part of a filtering as-path segment)5
Filtering segments (at least one filtering AS):[ 20483 2118 ] [ 29449 3269 ] [ 29449 5392 ] [ 34102 3216 ]




Visibility estimation110 (+- 0) out of 115 ASes (95 %)
Filtering ASes (5)6730 8331 8402 28917 39821
Uncertain ASes (part of a filtering as-path segment)0




Visibility estimation110 (+- 0) out of 115 ASes (95 %)
Filtering ASes (5)8331 8402 28917 31323 39821
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
3.5YYUYYUUUUUU
174YYUYYUUUUUU
286YYYYYUUUUUU
513YYYYYUUUUUU
1103YYUYYUUUUUU
1125YYUYYUUUUUU
1221YYUYYUUUUUU
1239YYUYYUUUUUU
1280YYUYYUUUUUU
1299YYUYYUUUUUU
1853YYNYYUUUUUU
1930YYUYYUUUUUU
2118YUUYYUUUUUU
2119YYUYYUUUUUU
2497YYUYYUUUUUU
2852YNUYYUUUUUU
2857YYNYYUUUUUU
2895YNUYYUUUUUU
2914YYNYYUUUUUU
3216YUUYYUUUUUU
3257YYNYYUUUUUU
3269YUUYYUUUUUU
3333YYUYYUUUUUU
3356YYUYYUUUUUU
3549YYNYYUUUUUU
3741YYUYYUUUUUU
4589YYUYYUUUUUU
4608YYUYYUUUUUU
4637YYUYYUUUUUU
4777YYUYYUUUUUU
5392YNUYYUUUUUU
5413YYNYYNNNNNN
5511YNUYYUUUUUU
6067YNUYYUUUUUU
6453YYUYYUUUUUU
6461YYUYYUUUUUU
6667YYUYYUUUUUU
6695YYNYYUUUUUU
6730NYNNYUUUUUU
6762YYNYYNNNNNN
6881YYUYYUUUUUU
6939YYUYYUUUUUU
7018YYUYYUUUUUU
7575YYUYYUUUUUU
8331YNUNNUUUUUU
8359YYNYYNNNNNN
8402YNUNNUUUUUU
8419YNNYYUUUUUU
8434YYUYYUUUUUU
8447YYNYYUUUUUU
8468YNUYYUUUUUU
8596YYNYYUUUUUU
8763YYUYYUUUUUU
8881YYUYYUUUUUU
8928YYUYYUUUUUU
9002YYUYYUUUUUU
9121YYUYYUUUUUU
9304YYUYYUUUUUU
12350YYYYYUUUUUU
12389YYUYYUUUUUU
12637YNUYYUUUUUU
12779YNUYYUUUUUU
12859YYYYYUUUUUU
12956YYUYYUUUUUU
12989YYNYYNNNNNN
13030YYNYYNNNNNN
13237YYUYYUUUUUU
14361YYUYYUUUUUU
16150YYNYYNNNNNN
16186YYUYYUUUUUU
16735YYUYYUUUUUU
19089YYUYYUUUUUU
19151YYNYYUUUUUU
20483YNUYYUUUUUU
20562YYNYYNNNNNN
20640YYUYYUUUUUU
20771YYUYYUUUUUU
20932YYNYYNNNNNN
20965YYUYYUUUUUU
21202YNUYYUUUUUU
22548YYUYYUUUUUU
22691YYUYYUUUUUU
25091YYYYYUUUUUU
25512YYUYYUUUUUU
25560YYUYYUUUUUU
26943YYNYYNNNNNN
27664YYUYYUUUUUU
28895YNUYYUUUUUU
28917YNUNNUUUUUU
28929YNUYYUUUUUU
29208YYUYYUUUUUU
29222YYYYYUUUUUU
29449YUUYYUUUUUU
29636YNNYYUUUUUU
29686YYUYYUUUUUU
30132YYNYYNNNNNN
30844YNUYYUUUUUU
30890YYNYYUUUUUU
31283YYUYYUUUUUU
31323YNUYNUUUUUU
31477YNNYYUUUUUU
34102YUUYYUUUUUU
34245YNNYYUUUUUU
34347YYUYYUUUUUU
34695YNNYYUUUUUU
35054YYUYYUUUUUU
39202YNNYYUUUUUU
39792YNUYYUUUUUU
39821YNUNNUUUUUU
39912YYNYYUUUUUU
41853YYNYYUUUUUU
41877YYUYYUUUUUU
41965YYUYYUUUUUU
42109YYUYYUUUUUU
44505YNUYYUUUUUU

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