bgpreport

Network · data from 2026-11-12

AS269622 AS269622 - LUCIANA ARAUJO NUNES DE JESUS ME

Registry name: AS269622 - LUCIANA ARAUJO NUNES DE JESUS ME, BR · not in PeeringDB

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

Announced routes

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

45.190.32.0/23 Valid Nonecovered by 45.190.32.0/22 667 99% 67
45.190.34.0/23 Valid Nonecovered by 45.190.32.0/22 667 99% 67
2804:6758::/33 Valid Nonecovered by 2804:6758::/32 635 100% 68
2804:6758:8000::/33 Valid Nonecovered by 2804:6758::/32 635 100% 68
45.190.32.0/22 Valid Other IRR onlyRADB 673 100% 67
2804:6758::/32 Valid Other IRR onlyRADB 635 100% 67

AS-SET

AS269622 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 6 are in fix.csv.

  • Route object: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none45.190.32.0/23No route object for it. A route object for 45.190.32.0/22 with origin AS269622 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269622 in the RIR database for the space.667 of 673
Route object: none45.190.34.0/23No route object for it. A route object for 45.190.32.0/22 with origin AS269622 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269622 in the RIR database for the space.667 of 673
Route object: none2804:6758::/33No route object for it. A route object for 2804:6758::/32 with origin AS269622 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269622 in the RIR database for the space.635 of 636
Route object: none2804:6758:8000::/33No route object for it. A route object for 2804:6758::/32 with origin AS269622 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269622 in the RIR database for the space.635 of 636
Route object: RIR45.190.32.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2804:6758::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS269622 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.