bgpreport

Network · data from 2026-11-12

AS269312 AS269312 - NETFLY LTDA ME

Registry name: AS269312 - NETFLY LTDA ME, BR · not in PeeringDB

3IPv4 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
6No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS269312, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269312, 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:62b0::/33 No ROA Nonecovered by 2804:62b0::/32 635 100% 67
2804:62b0:8000::/33 No ROA Nonecovered by 2804:62b0::/32 634 100% 67
45.183.224.0/23 No ROA Other IRR onlyRADB 671 100% 67
45.183.226.0/24 No ROA Other IRR onlyRADB 671 100% 67
45.183.227.0/24 No ROA Other IRR onlyRADB 671 100% 67
2804:62b0::/32 No ROA Other IRR onlyRADB 634 100% 69

AS-SET

AS269312 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 15 are in fix.csv.

  • ROA: none6
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2804:62b0::/33No ROA covers it. Add a ROA for AS269312, maxLength 33.635 of 636
Route object: none2804:62b0::/33No route object for it. A route object for 2804:62b0::/32 with origin AS269312 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269312 in the RIR database for the space.635 of 636
ROA: none2804:62b0:8000::/33No ROA covers it. Add a ROA for AS269312, maxLength 33.634 of 636
Route object: none2804:62b0:8000::/33No route object for it. A route object for 2804:62b0::/32 with origin AS269312 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269312 in the RIR database for the space.634 of 636
ROA: none45.183.224.0/23No ROA covers it. Add a ROA for AS269312, maxLength 23.671 of 673
Route object: RIR45.183.224.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.183.226.0/24No ROA covers it. Add a ROA for AS269312, maxLength 24.671 of 673
Route object: RIR45.183.226.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.183.227.0/24No ROA covers it. Add a ROA for AS269312, maxLength 24.671 of 673
Route object: RIR45.183.227.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:62b0::/32No ROA covers it. Add a ROA for AS269312, maxLength 32.634 of 636
Route object: RIR2804:62b0::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

45.183.224.0/22RADBNo ROA
45.183.224.0/24RADBNo ROA
45.183.225.0/24RADBNo 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.