bgpreport

Network · data from 2026-11-12

AS4387 AS4387 - Secretaria de Ciencia y Tecnologia - Red Cientific

Registry name: AS4387 - Secretaria de Ciencia y Tecnologia - Red Cientific, AR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS4387, 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.

168.83.128.0/20 No ROA None 668 99% 67
168.83.0.0/20 No ROA Other IRR onlyRADB 670 100% 67
168.83.1.0/24 No ROA Other IRR onlyRADB 670 100% 67
168.83.26.0/24 No ROA Other IRR onlyRADB 670 100% 67
168.83.30.0/24 No ROA Other IRR onlyRADB 670 100% 67
168.83.31.0/24 No ROA Other IRR onlyRADB 670 100% 67
168.83.32.0/23 No ROA Other IRR onlyRADB 670 100% 67
168.83.64.0/22 No ROA Other IRR onlyRADB 670 100% 67
200.1.224.0/19 No ROA Other IRR onlyRADB 670 100% 67
200.9.242.0/23 No ROA Other IRR onlyRADB 670 100% 67
200.9.244.0/23 No ROA Other IRR onlyRADB 667 99% 67

AS-SET

AS4387 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 22 are in fix.csv.

  • ROA: none11
  • Route object: none1
  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
ROA: none168.83.128.0/20No ROA covers it. Add a ROA for AS4387, maxLength 20.668 of 673
Route object: none168.83.128.0/20No route object for it. Add a route object with origin AS4387 in the RIR database for the space.668 of 673
ROA: none168.83.0.0/20No ROA covers it. Add a ROA for AS4387, maxLength 20.670 of 673
Route object: RIR168.83.0.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none168.83.1.0/24No ROA covers it. Add a ROA for AS4387, maxLength 24.670 of 673
Route object: RIR168.83.1.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none168.83.26.0/24No ROA covers it. Add a ROA for AS4387, maxLength 24.670 of 673
Route object: RIR168.83.26.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none168.83.30.0/24No ROA covers it. Add a ROA for AS4387, maxLength 24.670 of 673
Route object: RIR168.83.30.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none168.83.31.0/24No ROA covers it. Add a ROA for AS4387, maxLength 24.670 of 673
Route object: RIR168.83.31.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none168.83.32.0/23No ROA covers it. Add a ROA for AS4387, maxLength 23.670 of 673
Route object: RIR168.83.32.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none168.83.64.0/22No ROA covers it. Add a ROA for AS4387, maxLength 22.670 of 673
Route object: RIR168.83.64.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.1.224.0/19No ROA covers it. Add a ROA for AS4387, maxLength 19.670 of 673
Route object: RIR200.1.224.0/19Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.9.242.0/23No ROA covers it. Add a ROA for AS4387, maxLength 23.670 of 673
Route object: RIR200.9.242.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none200.9.244.0/23No ROA covers it. Add a ROA for AS4387, maxLength 23.667 of 673
Route object: RIR200.9.244.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

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