bgpreport

Network · data from 2026-11-12

AS269277 AS269277 - A.A.B.I. COMERCIO DE PRODUTOS PARA INFORMATICA E C

Registry name: AS269277 - A.A.B.I. COMERCIO DE PRODUTOS PARA INFORMATICA E C, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269277, 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.183.128.0/23 No ROA Other IRR onlyRADB 672 100% 66
45.183.128.0/24 No ROA Other IRR onlyRADB 672 100% 66
45.183.129.0/24 No ROA Other IRR onlyRADB 672 100% 66
2804:6220::/32 No ROA Other IRR onlyRADB 635 100% 67
2804:6220::/33 No ROA Other IRR onlyRADB 635 100% 67
2804:6220::/34 No ROA Other IRR onlyRADB 635 100% 67
2804:6220:4000::/34 No ROA Other IRR onlyRADB 635 100% 67
2804:6220:8000::/33 No ROA Other IRR onlyRADB 635 100% 67
2804:6220:8000::/34 No ROA Other IRR onlyRADB 635 100% 67
2804:6220:c000::/34 No ROA Other IRR onlyRADB 635 100% 67

AS-SET

AS269277 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 44 are in fix.csv.

  • ROA: none10
  • Route object: RIR10
  • Route object: not announced24
ChangePrefix or setDetailFull-table peers
ROA: none45.183.128.0/23No ROA covers it. Add a ROA for AS269277, maxLength 23.672 of 673
Route object: RIR45.183.128.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.183.128.0/24No ROA covers it. Add a ROA for AS269277, maxLength 24.672 of 673
Route object: RIR45.183.128.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.183.129.0/24No ROA covers it. Add a ROA for AS269277, maxLength 24.672 of 673
Route object: RIR45.183.129.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2804:6220::/32No ROA covers it. Add a ROA for AS269277, maxLength 32.635 of 636
Route object: RIR2804:6220::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:6220::/33No ROA covers it. Add a ROA for AS269277, maxLength 33.635 of 636
Route object: RIR2804:6220::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:6220::/34No ROA covers it. Add a ROA for AS269277, maxLength 34.635 of 636
Route object: RIR2804:6220::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:6220:4000::/34No ROA covers it. Add a ROA for AS269277, maxLength 34.635 of 636
Route object: RIR2804:6220:4000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:6220:8000::/33No ROA covers it. Add a ROA for AS269277, maxLength 33.635 of 636
Route object: RIR2804:6220:8000::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:6220:8000::/34No ROA covers it. Add a ROA for AS269277, maxLength 34.635 of 636
Route object: RIR2804:6220:8000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:6220:c000::/34No ROA covers it. Add a ROA for AS269277, maxLength 34.635 of 636
Route object: RIR2804:6220:c000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

2804:6220::/35RADBNo ROA
2804:6220::/36RADBNo ROA
2804:6220:1000::/36RADBNo ROA
2804:6220:2000::/35RADBNo ROA
2804:6220:2000::/36RADBNo ROA
2804:6220:3000::/36RADBNo ROA
2804:6220:4000::/35RADBNo ROA
2804:6220:4000::/36RADBNo ROA
2804:6220:5000::/36RADBNo ROA
2804:6220:6000::/35RADBNo ROA
2804:6220:6000::/36RADBNo ROA
2804:6220:7000::/36RADBNo ROA
2804:6220:8000::/35RADBNo ROA
2804:6220:8000::/36RADBNo ROA
2804:6220:9000::/36RADBNo ROA
2804:6220:a000::/35RADBNo ROA
2804:6220:a000::/36RADBNo ROA
2804:6220:b000::/36RADBNo ROA
2804:6220:c000::/35RADBNo ROA
2804:6220:c000::/36RADBNo ROA
2804:6220:d000::/36RADBNo ROA
2804:6220:e000::/35RADBNo ROA
2804:6220:e000::/36RADBNo ROA
2804:6220:f000::/36RADBNo 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.