bgpreport

Network · data from 2026-11-12

AS269050 AS269050 - JOAO ROGERIO LEONARDO EIRELIME

Registry name: AS269050 - JOAO ROGERIO LEONARDO EIRELIME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269050, 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.177.240.0/22 No ROA Other IRR onlyTC 670 100% 67
2804:5eb0::/32 No ROA Other IRR onlyTC 635 100% 67

AS-SET

AS269050 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 40 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced36
ChangePrefix or setDetailFull-table peers
ROA: none45.177.240.0/22No ROA covers it. Add a ROA for AS269050, maxLength 22.670 of 673
Route object: RIR45.177.240.0/22Route object only in TC. Add it in the RIR database for the space.670 of 673
ROA: none2804:5eb0::/32No ROA covers it. Add a ROA for AS269050, maxLength 32.635 of 636
Route object: RIR2804:5eb0::/32Route object only in TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

45.177.240.0/23RADBNo ROA
45.177.240.0/24RADBNo ROA
45.177.241.0/24RADBNo ROA
45.177.242.0/23RADBNo ROA
45.177.242.0/24RADBNo ROA
45.177.243.0/24RADBNo ROA
2804:5eb0::/33RADBNo ROA
2804:5eb0::/34RADBNo ROA
2804:5eb0::/35RADBNo ROA
2804:5eb0::/36RADBNo ROA
2804:5eb0:1000::/36RADBNo ROA
2804:5eb0:2000::/35RADBNo ROA
2804:5eb0:2000::/36RADBNo ROA
2804:5eb0:3000::/36RADBNo ROA
2804:5eb0:4000::/34RADBNo ROA
2804:5eb0:4000::/35RADBNo ROA
2804:5eb0:4000::/36RADBNo ROA
2804:5eb0:5000::/36RADBNo ROA
2804:5eb0:6000::/35RADBNo ROA
2804:5eb0:6000::/36RADBNo ROA
2804:5eb0:7000::/36RADBNo ROA
2804:5eb0:8000::/33RADBNo ROA
2804:5eb0:8000::/34RADBNo ROA
2804:5eb0:8000::/35RADBNo ROA
2804:5eb0:8000::/36RADBNo ROA
2804:5eb0:9000::/36RADBNo ROA
2804:5eb0:a000::/35RADBNo ROA
2804:5eb0:a000::/36RADBNo ROA
2804:5eb0:b000::/36RADBNo ROA
2804:5eb0:c000::/34RADBNo ROA
2804:5eb0:c000::/35RADBNo ROA
2804:5eb0:c000::/36RADBNo ROA
2804:5eb0:d000::/36RADBNo ROA
2804:5eb0:e000::/35RADBNo ROA
2804:5eb0:e000::/36RADBNo ROA
2804:5eb0: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.