bgpreport

Network · data from 2026-11-12

AS28516 AS28516 - Cablemas Telecomunicaciones SA de CV

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28516, 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.
187.253.204.0/24 No ROA Other IRR onlyRADB 673 100% 67
187.253.205.0/24 No ROA Other IRR onlyRADB 673 100% 67
187.253.206.0/24 No ROA Other IRR onlyRADB 673 100% 67
2806:250:b00::/48 Valid Other IRR onlyRADB 635 100% 70
2806:250:b01::/48 Valid Other IRR onlyRADB 635 100% 70
2806:250:b02::/48 Valid Other IRR onlyRADB 635 100% 70
2806:250:b03::/48 Valid Other IRR onlyRADB 635 100% 70
2806:250:b0f::/48 Valid Other IRR onlyRADB 635 100% 70

AS-SET

AS28516 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: none3
  • Route object: RIR8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none187.253.204.0/24No ROA covers it. Add a ROA for AS28516, maxLength 24.673 of 673
Route object: RIR187.253.204.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none187.253.205.0/24No ROA covers it. Add a ROA for AS28516, maxLength 24.673 of 673
Route object: RIR187.253.205.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none187.253.206.0/24No ROA covers it. Add a ROA for AS28516, maxLength 24.673 of 673
Route object: RIR187.253.206.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2806:250:b00::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2806:250:b01::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2806:250:b02::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2806:250:b03::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2806:250:b0f::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

201.161.128.0/18RADBNo ROA
2806:250:b00::/40LACNIC, RADBValid

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.