bgpreport

Network · data from 2026-11-12

AS28535 AS28535 - Mexico Red de Telecomunicaciones, S. de R.L. de C.V.

Registry name: AS28535 - Mexico Red de Telecomunicaciones, S. de R.L. de C.V., MX · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28535, 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.233.143.0/24 No ROA None 672 100% 67
177.233.135.0/24 No ROA None 671 100% 67
177.233.160.0/24 No ROA None 670 100% 67
177.233.161.0/24 No ROA None 670 100% 67
2001:1260:4::/48 No ROA Other origin only 634 100% 69
2001:1260:4::/64 No ROA None 1 0%low visibility 1
187.187.53.0/24 No ROA Other IRR onlyRADB 667 99% 67
187.187.196.0/22 No ROA Other IRR onlyRADB 667 99% 67
187.187.196.0/23 No ROA Other IRR onlyRADB 667 99% 67
187.187.198.0/23 No ROA Other IRR onlyRADB 664 99% 67
2001:1260:12::/48 No ROA Other IRR onlyRADB 634 100% 69

AS-SET

AS28535 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: none6
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none177.233.143.0/24No ROA covers it. Add a ROA for AS28535, maxLength 24.672 of 673
Route object: none177.233.143.0/24No route object for it. Add a route object with origin AS28535 in the RIR database for the space.672 of 673
ROA: none177.233.135.0/24No ROA covers it. Add a ROA for AS28535, maxLength 24.671 of 673
Route object: none177.233.135.0/24No route object for it. Add a route object with origin AS28535 in the RIR database for the space.671 of 673
ROA: none177.233.160.0/24No ROA covers it. Add a ROA for AS28535, maxLength 24.670 of 673
Route object: none177.233.160.0/24No route object for it. Add a route object with origin AS28535 in the RIR database for the space.670 of 673
ROA: none177.233.161.0/24No ROA covers it. Add a ROA for AS28535, maxLength 24.670 of 673
Route object: none177.233.161.0/24No route object for it. Add a route object with origin AS28535 in the RIR database for the space.670 of 673
ROA: none2001:1260:4::/48No ROA covers it. Add a ROA for AS28535, maxLength 48.634 of 636
Route object: none2001:1260:4::/48Route objects for it name AS18734. Add a route object with origin AS28535 in the RIR database for the space.634 of 636
ROA: none2001:1260:4::/64No ROA covers it. Add a ROA for AS28535, maxLength 64.1 of 636
Route object: none2001:1260:4::/64No route object for it. Add a route object with origin AS28535 in the RIR database for the space.1 of 636
ROA: none187.187.53.0/24No ROA covers it. Add a ROA for AS28535, maxLength 24.667 of 673
Route object: RIR187.187.53.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none187.187.196.0/22No ROA covers it. Add a ROA for AS28535, maxLength 22.667 of 673
Route object: RIR187.187.196.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none187.187.196.0/23No ROA covers it. Add a ROA for AS28535, maxLength 23.667 of 673
Route object: RIR187.187.196.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none187.187.198.0/23No ROA covers it. Add a ROA for AS28535, maxLength 23.664 of 673
Route object: RIR187.187.198.0/23Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none2001:1260:12::/48No ROA covers it. Add a ROA for AS28535, maxLength 48.634 of 636
Route object: RIR2001:1260:12::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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