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

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



Visibility estimation86 (+- 0) out of 89 ASes (96 %)
Filtering ASes (3)1930 16150 27750
Uncertain ASes (part of a filtering as-path segment)0




Visibility estimation83 (+- 1) out of 89 ASes (93 %)
Filtering ASes (4)1930 16150 27750 44505
Uncertain ASes (part of a filtering as-path segment)3
Filtering segments (at least one filtering AS):[ 20771 9121 20562 ]




Visibility estimation86 (+- 0) out of 89 ASes (96 %)
Filtering ASes (3)1930 16150 27750
Uncertain ASes (part of a filtering as-path segment)0




Visibility estimation80 (+- 1) out of 89 ASes (89 %)
Filtering ASes (7)1930 2516 12793 16150 27750 34695 44505
Uncertain ASes (part of a filtering as-path segment)3
Filtering segments (at least one filtering AS):[ 20771 9121 20562 ]




Visibility estimation82 (+- 0) out of 89 ASes (92 %)
Filtering ASes (7)1930 2516 3303 12793 16150 27750 34695
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 /21114.0.0.0 /24114.50.0.0 /21114.200.0.0 /19114.255.0.0 /16115.0.0.0 /24115.50.0.0 /21115.200.0.0 /19115.255.0.0 /16
286YYYYYUUUUUUUU
513YYYYYUUUUUUUU
1103YYYYYUUUUUUUU
1221YYYYYUUUUUUUU
1273YYYYYUUUUUUUU
1280YYYYYUUUUUUUU
1299YYYYYUUUUUUUU
1853YYYYYUUUUUUUU
1916YYYYYUUUUUUUU
1930NNNNNUUUUUUUU
2119YYYYYUUUUUUUU
2497YYYYYUUUUUUUU
2516YYYNNUUUUUUUU
2914YYYYYUUUUUUUU
3257YYYYYUUUUUUUU
3303YYYYNUUUUUUUU
3356YYYYYUUUUUUUU
3549YYYYYUUUUUUUU
3741YYYYYUUUUUUUU
4608YYYYYUUUUUUUU
4637YYYYYUUUUUUUU
4777YYYYYUUUUUUUU
5392YYYYYUUUUUUUU
5413YYYYYNNNNNNNN
5511YYYYYUUUUUUUU
6067YYYYYUUUUUUUU
6453YYYYYUUUUUUUU
6461YYYYYUUUUUUUU
6667YYYYYUUUUUUUU
6762YYYYYUUUUUUUU
6881YYYYYUUUUUUUU
6939YYYYYUUUUUUUU
7018YYYYYUUUUUUUU
7575YYYYYUUUUUUUU
8419YYYYYUUUUUUUU
8434YYYYYUUUUUUUU
8447YYYYYUUUUUUUU
8468YYYYYUUUUUUUU
8596YYYYYUUUUUUUU
8607YYYYYUUUUUUUU
8928YYYYYUUUUUUUU
9121YUYUYUUUUUUUU
10429YYYYYUUUUUUUU
11537YYYYYUUUUUUUU
12350YYYYYUUUUUUUU
12637YYYYYUUUUUUUU
12779YYYYYUUUUUUUU
12793YYYNNUUUUUUUU
12859YYYYYUUUUUUUU
12956YYYYYUUUUUUUU
13237YYYYYUUUUUUUU
13645YYYYYUUUUUUUU
14361YYYYYUUUUUUUU
16150NNNNNUUUUUUUU
16186YYYYYUUUUUUUU
16467YYYYYUUUUUUUU
19089YYYYYUUUUUUUU
20485YYYYYUUUUUUUU
20562YUYUYUUUUUUUU
20771YUYUYUUUUUUUU
20932YYYYYNNNNNNNN
20965YYYYYUUUUUUUU
21202YYYYYUUUUUUUU
22548YYYYYUUUUUUUU
22691YYYYYUUUUUUUU
24963YYYYYUUUUUUUU
25091YYYYYUUUUUUUU
25462YYYYYUUUUUUUU
27664YYYYYUUUUUUUU
27750NNNNNUUUUUUUU
28929YYYYYUUUUUUUU
29208YYYYYUUUUUUUU
29222YYYYYUUUUUUUU
29449YYYYYUUUUUUUU
29636YYYYYUUUUUUUU
30126YYYYYUUUUUUUU
30132YYYYYUUUUUUUU
30844YYYYYUUUUUUUU
31283YYYYYUUUUUUUU
34245YYYYYUUUUUUUU
34347YYYYYUUUUUUUU
34695YYYNNUUUUUUUU
35054YYYYYUUUUUUUU
39196YYYYYUUUUUUUU
39202YYYYYUUUUUUUU
39912YYYYYUUUUUUUU
41877YYYYYUUUUUUUU
42109YYYYYUUUUUUUU
44505YNYNYUUUUUUUU

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