bgpreport

Network · data from 2026-11-12

AS266401 CNANET

Registry name: AS266401 - CNA NET, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266401, 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.
2804:3748::/33 No ROA Nonecovered by 2804:3748::/32 333 52% 65
2804:3748:8000::/33 No ROA Nonecovered by 2804:3748::/32 333 52% 65
170.81.60.0/22 No ROA Other IRR onlyRADB, TC 672 100% 66
170.81.61.0/24 No ROA Other IRR onlyRADB, TC 672 100% 66
170.81.62.0/23 No ROA Other IRR onlyRADB, TC 671 100% 67
170.81.60.0/24 No ROA Other IRR onlyRADB, TC 669 99% 67
2804:3748::/32 No ROA Other IRR onlyRADB, TC 634 100% 67
170.81.63.0/24 No ROA Other IRR onlyRADB, TC 208 31% 56
170.81.62.0/24 No ROA Other IRR onlyRADB, TC 205 30% 56

AS-SET

AS266401's PeeringDB record names no 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 19 are in fix.csv.

  • ROA: none9
  • Route object: none2
  • Route object: RIR7
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2804:3748::/33No ROA covers it. Add a ROA for AS266401, maxLength 33.333 of 636
Route object: none2804:3748::/33No route object for it. A route object for 2804:3748::/32 with origin AS266401 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266401 in the RIR database for the space.333 of 636
ROA: none2804:3748:8000::/33No ROA covers it. Add a ROA for AS266401, maxLength 33.333 of 636
Route object: none2804:3748:8000::/33No route object for it. A route object for 2804:3748::/32 with origin AS266401 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266401 in the RIR database for the space.333 of 636
ROA: none170.81.60.0/22No ROA covers it. Add a ROA for AS266401, maxLength 22.672 of 673
Route object: RIR170.81.60.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none170.81.61.0/24No ROA covers it. Add a ROA for AS266401, maxLength 24.672 of 673
Route object: RIR170.81.61.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none170.81.62.0/23No ROA covers it. Add a ROA for AS266401, maxLength 23.671 of 673
Route object: RIR170.81.62.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none170.81.60.0/24No ROA covers it. Add a ROA for AS266401, maxLength 24.669 of 673
Route object: RIR170.81.60.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:3748::/32No ROA covers it. Add a ROA for AS266401, maxLength 32.634 of 636
Route object: RIR2804:3748::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
ROA: none170.81.63.0/24No ROA covers it. Add a ROA for AS266401, maxLength 24.208 of 673
Route object: RIR170.81.63.0/24Route object only in RADB, TC. Add it in the RIR database for the space.208 of 673
ROA: none170.81.62.0/24No ROA covers it. Add a ROA for AS266401, maxLength 24.205 of 673
Route object: RIR170.81.62.0/24Route object only in RADB, TC. Add it in the RIR database for the space.205 of 673

Route objects not announced

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

170.81.60.0/23RADB, TCNo 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.