bgpreport

Network · data from 2026-11-12

AS200217 DataLake CloudFerro S.A

Registry name: DataLake CloudFerro S.A, PL · not in PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
17IPv6 routes 100.0% RPKI valid · 41.2% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 10 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
10Route objects not announced registered with origin AS200217, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS200217, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

2a13:7bc0:9::/48 Valid Nonecovered by 2a13:7bc0::/29 635 100% 69
2a13:7bc0:b::/48 Valid Nonecovered by 2a13:7bc0::/29 635 100% 69
2a13:7bc0:c::/48 Valid Nonecovered by 2a13:7bc0::/29 635 100% 69
2a13:7bc0:d::/48 Valid Nonecovered by 2a13:7bc0::/29 635 100% 69
2a13:7bc0:e::/48 Valid Nonecovered by 2a13:7bc0::/29 635 100% 69
2a13:7bc0:f::/48 Valid Nonecovered by 2a13:7bc0::/29 635 100% 69
2a13:7bc0:10::/48 Valid Nonecovered by 2a13:7bc0::/29 635 100% 69
2a13:7bc0:7::/48 Valid Nonecovered by 2a13:7bc0::/29 633 100% 67
2a13:7bc0:8::/48 Valid Nonecovered by 2a13:7bc0::/29 632 99% 67
2a13:7bc0:a::/48 Valid Nonecovered by 2a13:7bc0::/29 632 99% 67
194.153.72.0/23 Valid RIR databaseRIPE 673 100% 67
217.71.196.0/23 Valid RIR databaseRIPE 673 100% 67
91.212.149.0/24 Valid RIR databaseRIPE 671 100% 68
193.142.60.0/24 Valid RIR databaseRIPE 671 100% 68
217.71.192.0/23 Valid RIR databaseRIPE 671 100% 68
217.71.194.0/23 Valid RIR databaseRIPE 671 100% 68
217.71.198.0/23 Valid RIR databaseRIPE 671 100% 68
2a13:7bc0::/48 Valid RIR databaseRIPE 635 100% 69
2a13:7bc0:1::/48 Valid RIR databaseRIPE 635 100% 69
2a13:7bc0:2::/48 Valid RIR databaseRIPE 635 100% 69
2a13:7bc0:3::/48 Valid RIR databaseRIPE 635 100% 69
2a13:7bc0:4::/48 Valid RIR databaseRIPE 635 100% 69
2a13:7bc0:5::/48 Valid RIR databaseRIPE 635 100% 69
2a13:7bc0:6::/48 Valid RIR databaseRIPE 635 100% 69

AS-SET

AS200217 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 20 are in fix.csv.

  • Route object: none10
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
Route object: none2a13:7bc0:9::/48No route object for it. A route object for 2a13:7bc0::/29 with origin AS200217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200217 in the RIR database for the space.635 of 636
Route object: none2a13:7bc0:b::/48No route object for it. A route object for 2a13:7bc0::/29 with origin AS200217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200217 in the RIR database for the space.635 of 636
Route object: none2a13:7bc0:c::/48No route object for it. A route object for 2a13:7bc0::/29 with origin AS200217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200217 in the RIR database for the space.635 of 636
Route object: none2a13:7bc0:d::/48No route object for it. A route object for 2a13:7bc0::/29 with origin AS200217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200217 in the RIR database for the space.635 of 636
Route object: none2a13:7bc0:e::/48No route object for it. A route object for 2a13:7bc0::/29 with origin AS200217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200217 in the RIR database for the space.635 of 636
Route object: none2a13:7bc0:f::/48No route object for it. A route object for 2a13:7bc0::/29 with origin AS200217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200217 in the RIR database for the space.635 of 636
Route object: none2a13:7bc0:10::/48No route object for it. A route object for 2a13:7bc0::/29 with origin AS200217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200217 in the RIR database for the space.635 of 636
Route object: none2a13:7bc0:7::/48No route object for it. A route object for 2a13:7bc0::/29 with origin AS200217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200217 in the RIR database for the space.633 of 636
Route object: none2a13:7bc0:8::/48No route object for it. A route object for 2a13:7bc0::/29 with origin AS200217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200217 in the RIR database for the space.632 of 636
Route object: none2a13:7bc0:a::/48No route object for it. A route object for 2a13:7bc0::/29 with origin AS200217 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200217 in the RIR database for the space.632 of 636

Route objects not announced

Route objects with origin AS200217 whose prefix no peer sees AS200217 announce. Many are kept on purpose (backup routes, space announced only in some places).

91.212.135.0/24RIPEValid
217.71.192.0/24RIPEValid
217.71.193.0/24RIPEValid
217.71.194.0/24RIPEValid
217.71.195.0/24RIPEValid
217.71.196.0/24RIPEValid
217.71.197.0/24RIPEValid
217.71.198.0/24RIPEValid
217.71.199.0/24RIPEValid
2a13:7bc0::/29RIPENo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.