bgpreport

Network · data from 2026-11-12

AS28538 AS28538 - Cablemas Telecomunicaciones SA de CV

Registry name: AS28538 - Cablemas Telecomunicaciones SA de CV, MX · not in PeeringDB

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

Announced routes

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

177.236.128.0/22 No ROA None 672 100% 67
177.236.128.0/23 No ROA None 672 100% 67
177.236.130.0/23 No ROA None 672 100% 67
177.236.165.0/24 No ROA None 672 100% 67
177.239.236.0/24 No ROA None 672 100% 67
189.215.129.0/24 Valid RIR databaseLACNIC, RADB 669 99% 67
189.215.130.0/24 Valid RIR databaseLACNIC, RADB 669 99% 67

AS-SET

AS28538 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: none5
  • Route object: none5
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none177.236.128.0/22No ROA covers it. Add a ROA for AS28538, maxLength 22.672 of 673
Route object: none177.236.128.0/22No route object for it. Add a route object with origin AS28538 in the RIR database for the space.672 of 673
ROA: none177.236.128.0/23No ROA covers it. Add a ROA for AS28538, maxLength 23.672 of 673
Route object: none177.236.128.0/23No route object for it. Add a route object with origin AS28538 in the RIR database for the space.672 of 673
ROA: none177.236.130.0/23No ROA covers it. Add a ROA for AS28538, maxLength 23.672 of 673
Route object: none177.236.130.0/23No route object for it. Add a route object with origin AS28538 in the RIR database for the space.672 of 673
ROA: none177.236.165.0/24No ROA covers it. Add a ROA for AS28538, maxLength 24.672 of 673
Route object: none177.236.165.0/24No route object for it. Add a route object with origin AS28538 in the RIR database for the space.672 of 673
ROA: none177.239.236.0/24No ROA covers it. Add a ROA for AS28538, maxLength 24.672 of 673
Route object: none177.239.236.0/24No route object for it. Add a route object with origin AS28538 in the RIR database for the space.672 of 673

Route objects not announced

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

177.237.32.0/20RADBNo ROA
177.238.224.0/21RADBNo ROA
177.239.104.0/22RADBNo ROA
177.239.168.0/24RADBNo ROA
177.239.238.0/23RADBNo ROA
187.252.2.0/24RADBNo ROA
187.252.3.0/24RADBNo ROA
187.253.24.0/24RADBNo ROA
187.253.26.0/23RADBNo ROA
187.253.152.0/22RADBNo ROA
189.215.133.0/24RADBNo ROA
201.160.191.0/24RADBNo 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.