bgpreport

Network · data from 2026-11-12

AS39286 NITROSERV ASCANIO SASAU

Registry name: NITROSERV ASCANIO SASAU, FR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS39286, 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.

109.239.144.0/21 Valid Nonecovered by 109.239.144.0/20 673 100% 67
109.239.152.0/21 Valid Nonecovered by 109.239.144.0/20 673 100% 67
193.169.230.0/24 Valid Nonecovered by 193.169.230.0/23 673 100% 67
193.169.231.0/24 Valid Nonecovered by 193.169.230.0/23 673 100% 67
194.60.64.0/23 Valid Nonecovered by 194.60.64.0/22 673 100% 67
194.60.66.0/23 Valid Nonecovered by 194.60.64.0/22 673 100% 67
195.72.152.0/23 Valid Nonecovered by 195.72.152.0/22 673 100% 67
195.72.154.0/23 Valid Nonecovered by 195.72.152.0/22 673 100% 67
2a11:a3c0::/29 Valid None 632 99% 67
109.239.144.0/20 Valid RIR databaseRIPE 673 100% 67
193.169.230.0/23 Valid RIR databaseRIPE 673 100% 67
194.60.64.0/22 Valid RIR databaseRIPE 673 100% 67
195.72.152.0/22 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS39286 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 9 are in fix.csv.

  • Route object: none9
ChangePrefix or setDetailFull-table peers
Route object: none109.239.144.0/21No route object for it. A route object for 109.239.144.0/20 with origin AS39286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39286 in the RIR database for the space.673 of 673
Route object: none109.239.152.0/21No route object for it. A route object for 109.239.144.0/20 with origin AS39286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39286 in the RIR database for the space.673 of 673
Route object: none193.169.230.0/24No route object for it. A route object for 193.169.230.0/23 with origin AS39286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39286 in the RIR database for the space.673 of 673
Route object: none193.169.231.0/24No route object for it. A route object for 193.169.230.0/23 with origin AS39286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39286 in the RIR database for the space.673 of 673
Route object: none194.60.64.0/23No route object for it. A route object for 194.60.64.0/22 with origin AS39286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39286 in the RIR database for the space.673 of 673
Route object: none194.60.66.0/23No route object for it. A route object for 194.60.64.0/22 with origin AS39286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39286 in the RIR database for the space.673 of 673
Route object: none195.72.152.0/23No route object for it. A route object for 195.72.152.0/22 with origin AS39286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39286 in the RIR database for the space.673 of 673
Route object: none195.72.154.0/23No route object for it. A route object for 195.72.152.0/22 with origin AS39286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39286 in the RIR database for the space.673 of 673
Route object: none2a11:a3c0::/29No route object for it. Add a route object with origin AS39286 in the RIR database for the space.632 of 636

Route objects not announced

Every route object with origin AS39286 is announced.

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.