bgpreport

Network · data from 2026-11-12

AS61920 AS61920 - Link Explorer

Registry name: AS61920 - Link Explorer, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61920, 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.
170.233.247.0/24 No ROA Nonecovered by 170.233.244.0/22 671 100% 67
190.2.79.0/24 No ROA Nonecovered by 190.2.72.0/21 670 100% 66
170.233.244.0/22 No ROA Other IRR onlyRADB, TC 671 100% 66
190.2.72.0/21 No ROA Other IRR onlyRADB, TC 670 100% 66
2804:1820::/32 No ROA Other IRR onlyRADB, TC 634 100% 67

AS-SET

AS61920 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 10 are in fix.csv.

  • ROA: none5
  • Route object: none2
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none170.233.247.0/24No ROA covers it. Add a ROA for AS61920, maxLength 24.671 of 673
Route object: none170.233.247.0/24No route object for it. A route object for 170.233.244.0/22 with origin AS61920 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61920 in the RIR database for the space.671 of 673
ROA: none190.2.79.0/24No ROA covers it. Add a ROA for AS61920, maxLength 24.670 of 673
Route object: none190.2.79.0/24No route object for it. A route object for 190.2.72.0/21 with origin AS61920 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61920 in the RIR database for the space.670 of 673
ROA: none170.233.244.0/22No ROA covers it. Add a ROA for AS61920, maxLength 22.671 of 673
Route object: RIR170.233.244.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none190.2.72.0/21No ROA covers it. Add a ROA for AS61920, maxLength 21.670 of 673
Route object: RIR190.2.72.0/21Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none2804:1820::/32No ROA covers it. Add a ROA for AS61920, maxLength 32.634 of 636
Route object: RIR2804:1820::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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