bgpreport

Network · data from 2026-11-12

AS10277 AS10277 - Ministerio de Cultura y Educacion

Registry name: AS10277 - Ministerio de Cultura y Educacion, AR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10277, 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.21.0/24 No ROA Nonecovered by 168.83.20.0/23 670 100% 67
168.83.74.0/24 No ROA Nonecovered by 168.83.72.0/21 670 100% 67
168.83.78.0/24 No ROA Nonecovered by 168.83.72.0/21 670 100% 67
168.83.81.0/24 No ROA Nonecovered by 168.83.80.0/20 670 100% 67
168.83.82.0/24 No ROA Nonecovered by 168.83.80.0/20 670 100% 67
168.83.83.0/24 No ROA Nonecovered by 168.83.80.0/20 670 100% 67
168.83.80.0/20 No ROA Other IRR onlyALTDB 668 99% 67

AS-SET

AS10277 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 19 are in fix.csv.

  • ROA: none7
  • Route object: none6
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none168.83.21.0/24No ROA covers it. Add a ROA for AS10277, maxLength 24.670 of 673
Route object: none168.83.21.0/24No route object for it. A route object for 168.83.20.0/23 with origin AS10277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10277 in the RIR database for the space.670 of 673
ROA: none168.83.74.0/24No ROA covers it. Add a ROA for AS10277, maxLength 24.670 of 673
Route object: none168.83.74.0/24No route object for it. A route object for 168.83.72.0/21 with origin AS10277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10277 in the RIR database for the space.670 of 673
ROA: none168.83.78.0/24No ROA covers it. Add a ROA for AS10277, maxLength 24.670 of 673
Route object: none168.83.78.0/24No route object for it. A route object for 168.83.72.0/21 with origin AS10277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10277 in the RIR database for the space.670 of 673
ROA: none168.83.81.0/24No ROA covers it. Add a ROA for AS10277, maxLength 24.670 of 673
Route object: none168.83.81.0/24No route object for it. A route object for 168.83.80.0/20 with origin AS10277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10277 in the RIR database for the space.670 of 673
ROA: none168.83.82.0/24No ROA covers it. Add a ROA for AS10277, maxLength 24.670 of 673
Route object: none168.83.82.0/24No route object for it. A route object for 168.83.80.0/20 with origin AS10277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10277 in the RIR database for the space.670 of 673
ROA: none168.83.83.0/24No ROA covers it. Add a ROA for AS10277, maxLength 24.670 of 673
Route object: none168.83.83.0/24No route object for it. A route object for 168.83.80.0/20 with origin AS10277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10277 in the RIR database for the space.670 of 673
ROA: none168.83.80.0/20No ROA covers it. Add a ROA for AS10277, maxLength 20.668 of 673
Route object: RIR168.83.80.0/20Route object only in ALTDB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

168.83.20.0/23ALTDBNo ROA
168.83.61.0/24ALTDBNo ROA
168.83.62.0/23ALTDBNo ROA
168.83.68.0/22ALTDBNo ROA
168.83.72.0/21ALTDBNo 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.