bgpreport

Network · data from 2026-11-12

AS61921 AS61921 - blucomptec informatica ltda me

Registry name: AS61921 - blucomptec informatica ltda me, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61921, 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.9.70.0/23 No ROA Nonecovered by 200.9.68.0/22 669 99% 67
200.9.68.0/23 No ROA Nonecovered by 200.9.68.0/22 2 0%low visibility 2
200.9.68.0/22 No ROA Other IRR onlyRADB 670 100% 67
2804:1828::/32 No ROA Other IRR onlyRADB 634 100% 67

AS-SET

AS61921 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 9 are in fix.csv.

  • ROA: none4
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none200.9.70.0/23No ROA covers it. Add a ROA for AS61921, maxLength 23.669 of 673
Route object: none200.9.70.0/23No route object for it. A route object for 200.9.68.0/22 with origin AS61921 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61921 in the RIR database for the space.669 of 673
ROA: none200.9.68.0/23No ROA covers it. Add a ROA for AS61921, maxLength 23.2 of 673
Route object: none200.9.68.0/23No route object for it. A route object for 200.9.68.0/22 with origin AS61921 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61921 in the RIR database for the space.2 of 673
ROA: none200.9.68.0/22No ROA covers it. Add a ROA for AS61921, maxLength 22.670 of 673
Route object: RIR200.9.68.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:1828::/32No ROA covers it. Add a ROA for AS61921, maxLength 32.634 of 636
Route object: RIR2804:1828::/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 AS61921 whose prefix no peer sees AS61921 announce. Many are kept on purpose (backup routes, space announced only in some places).

2804:1829::/32RADBNo 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.