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

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



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




Visibility estimation103 (+- 0) out of 107 ASes (96 %)
Filtering ASes (3)2914 20483 21202
Uncertain ASes (part of a filtering as-path segment)1
Filtering segments (at least one filtering AS):[ 20483 2118 ]




Visibility estimation98 (+- 4) out of 107 ASes (91 %)
Filtering ASes (5)1930 3741 6881 7018 9304
Uncertain ASes (part of a filtering as-path segment)8
Filtering segments (at least one filtering AS):[ 3.5 1125 1103 ] [ 4608 1221 4637 ] [ 16186 31283 ]




Visibility estimation98 (+- 4) out of 107 ASes (91 %)
Filtering ASes (5)1930 3741 6881 7018 9304
Uncertain ASes (part of a filtering as-path segment)8
Filtering segments (at least one filtering AS):[ 3.5 1125 1103 ] [ 4608 1221 4637 ] [ 16186 31283 ]


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.5YUYUUUUUUUU
174YUYYYUUUUUU
286YYYYYUUUUUU
513YYYYYUUUUUU
1103YUYUUUUUUUU
1125YUYUUUUUUUU
1221YYYUUUUUUUU
1239YUYYYUUUUUU
1280YUYYYUUUUUU
1299YUYYYUUUUUU
1853YNYYYUUUUUU
1930YUYNNUUUUUU
2118YUUYYUUUUUU
2119YUYYYUUUUUU
2497YNYYYUUUUUU
2857YNYYYUUUUUU
2895YNYYYUUUUUU
2914YNNYYUUUUUU
3216YUYYYUUUUUU
3257YNYYYUUUUUU
3269YUYYYUUUUUU
3356YNYYYUUUUUU
3549YYYYYUUUUUU
3741YNYNNUUUUUU
4589YNYYYUUUUUU
4608YYYUUUUUUUU
4637YYYUUUUUUUU
4777YUYYYUUUUUU
5392YNYYYUUUUUU
5413YNYYYNNNNNN
5511YUYYYUUUUUU
6067YNYYYUUUUUU
6453YUYYYUUUUUU
6461YNYYYUUUUUU
6667YUYYYUUUUUU
6695YNYYYUUUUUU
6762YNYYYNNNNNN
6881YNYNNUUUUUU
6939YUYYYUUUUUU
7018YUYNNUUUUUU
7575YNYYYUUUUUU
8331YNYYYUUUUUU
8359YNYYYNNNNNN
8402YUYYYUUUUUU
8419YNYYYUUUUUU
8434YUYYYUUUUUU
8447YNYYYUUUUUU
8468YNYYYUUUUUU
8596YNYYYUUUUUU
8763YNYYYUUUUUU
8881YNYYYUUUUUU
9002YYYYYUUUUUU
9304YNYNNUUUUUU
12350YYYYYUUUUUU
12389YUYYYUUUUUU
12637YUYYYUUUUUU
12779YUYYYUUUUUU
12859YYYYYUUUUUU
12956YUYYYUUUUUU
12989YNYYYNNNNNN
13030YNYYYNNNNNN
13237YNYYYUUUUUU
14361YNYYYUUUUUU
16150YUYYYUUUUUU
16186YUYUUUUUUUU
16735YUYYYUUUUUU
19089YUYYYUUUUUU
19151YNYYYUUUUUU
20483YNNYYUUUUUU
20562YNYYYNNNNNN
20640YNYYYUUUUUU
20932YNYYYNNNNNN
20965YUYYYUUUUUU
21202YNNYYUUUUUU
22548YUYYYUUUUUU
22691YNYYYUUUUUU
24963YNYYYUUUUUU
25091YYYYYUUUUUU
25560YNYYYUUUUUU
26943YNYYYNNNNNN
27664YNYYYUUUUUU
28895YNYYYUUUUUU
28917YNYYYUUUUUU
28929YUYYYUUUUUU
29222YYYYYUUUUUU
29449YUYYYUUUUUU
29636YNYYYUUUUUU
29686YUYYYUUUUUU
30126YUYYYUUUUUU
30132YNYYYNNNNNN
30844YNYYYUUUUUU
30890YNYYYUUUUUU
31283YUYUUUUUUUU
31323YNYYYUUUUUU
34102YUYYYUUUUUU
34245YNYYYUUUUUU
34695YNYYYUUUUUU
35054YNYYYUUUUUU
39202YNYYYUUUUUU
39792YNYYYUUUUUU
39821YNYYYUUUUUU
39912YNYYYUUUUUU
41853YNYYYUUUUUU
41877YUYYYUUUUUU
41965YUYYYUUUUUU
42109YUYYYUUUUUU
44334YUYYYUUUUUU

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