bgpreport

Network · data from 2026-11-12

AS10560 AS10560 - Instituto Tecnologico y de Estudios Superiores de Monterrey

Registry name: AS10560 - Instituto Tecnologico y de Estudios Superiores de Monterrey, MX · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10560, 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.
132.254.80.0/20 No ROA Other origin only 672 100% 67
132.254.56.0/21 No ROA Other IRR onlyRADB 672 100% 67
132.254.104.0/21 No ROA Other IRR onlyRADB 672 100% 67
132.254.112.0/21 No ROA Other IRR onlyRADB 672 100% 67
132.254.120.0/21 No ROA Other IRR onlyRADB 672 100% 67
132.254.128.0/21 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS10560 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 13 are in fix.csv.

  • ROA: none6
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none132.254.80.0/20No ROA covers it. Add a ROA for AS10560, maxLength 20.672 of 673
Route object: none132.254.80.0/20Route objects for it name AS10436, AS11172. Add a route object with origin AS10560 in the RIR database for the space.672 of 673
ROA: none132.254.56.0/21No ROA covers it. Add a ROA for AS10560, maxLength 21.672 of 673
Route object: RIR132.254.56.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none132.254.104.0/21No ROA covers it. Add a ROA for AS10560, maxLength 21.672 of 673
Route object: RIR132.254.104.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none132.254.112.0/21No ROA covers it. Add a ROA for AS10560, maxLength 21.672 of 673
Route object: RIR132.254.112.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none132.254.120.0/21No ROA covers it. Add a ROA for AS10560, maxLength 21.672 of 673
Route object: RIR132.254.120.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none132.254.128.0/21No ROA covers it. Add a ROA for AS10560, maxLength 21.672 of 673
Route object: RIR132.254.128.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

132.254.112.0/22RADBNo 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.