bgpreport

Network · data from 2026-11-12

AS264261 AS264261 - Agencia Brasileira de Desenvolvimento Industrial

Registry name: AS264261 - Agencia Brasileira de Desenvolvimento Industrial, 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
0Route objects not announced registered with origin AS264261, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS264261, 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.
200.0.134.0/23 No ROA Other IRR onlyRADB 669 99% 66
2801:80:f80::/44 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

AS264261 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 4 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none200.0.134.0/23No ROA covers it. Add a ROA for AS264261, maxLength 23.669 of 673
Route object: RIR200.0.134.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2801:80:f80::/44No ROA covers it. Add a ROA for AS264261, maxLength 44.636 of 636
Route object: RIR2801:80:f80::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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