Network · data from 2026-11-12
AS28556 AS28556 - Cablemas Telecomunicaciones SA de CV
Registry name: AS28556 - Cablemas Telecomunicaciones SA de CV, MX · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28556, 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.252.166.0/24 | No ROA | Other origin only | 672 100% |
| 187.252.167.0/24 | No ROA | Other origin only | 672 100% |
| 187.252.9.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 187.252.248.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 187.252.248.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 187.252.250.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 189.220.61.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 2806:250:1800::/44 | Valid | Other IRR onlyRADB | 635 100% |
| 187.185.154.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 189.220.60.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 189.221.153.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 2806:250:16::/48 | Valid | RIR databaseLACNIC | 633 100% |
AS-SET
AS28556 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 32 are in fix.csv.
- ROA: none7
- Route object: none2
- Route object: RIR6
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 187.252.166.0/24 | No ROA covers it. Add a ROA for AS28556, maxLength 24. |
| Route object: none | 187.252.166.0/24 | Route objects for it name AS28545. Add a route object with origin AS28556 in the RIR database for the space. |
| ROA: none | 187.252.167.0/24 | No ROA covers it. Add a ROA for AS28556, maxLength 24. |
| Route object: none | 187.252.167.0/24 | Route objects for it name AS28545. Add a route object with origin AS28556 in the RIR database for the space. |
| ROA: none | 187.252.9.0/24 | No ROA covers it. Add a ROA for AS28556, maxLength 24. |
| Route object: RIR | 187.252.9.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 187.252.248.0/22 | No ROA covers it. Add a ROA for AS28556, maxLength 22. |
| Route object: RIR | 187.252.248.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 187.252.248.0/23 | No ROA covers it. Add a ROA for AS28556, maxLength 23. |
| Route object: RIR | 187.252.248.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 187.252.250.0/23 | No ROA covers it. Add a ROA for AS28556, maxLength 23. |
| Route object: RIR | 187.252.250.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 189.220.61.0/24 | No ROA covers it. Add a ROA for AS28556, maxLength 24. |
| Route object: RIR | 189.220.61.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2806:250:1800::/44 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS28556 whose prefix no peer sees AS28556 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2806:250:1800::/40 | LACNIC, RADB | Valid |
| 2806:250:1800::/48 | RADB | Valid |
| 2806:250:1801::/48 | RADB | Valid |
| 2806:250:1802::/48 | RADB | Valid |
| 2806:250:1803::/48 | RADB | Valid |
| 2806:250:1804::/48 | RADB | Valid |
| 2806:250:1805::/48 | RADB | Valid |
| 2806:250:1806::/48 | RADB | Valid |
| 2806:250:1807::/48 | RADB | Valid |
| 2806:250:1808::/48 | RADB | Valid |
| 2806:250:1809::/48 | RADB | Valid |
| 2806:250:180a::/48 | RADB | Valid |
| 2806:250:180b::/48 | RADB | Valid |
| 2806:250:180c::/48 | RADB | Valid |
| 2806:250:180d::/48 | RADB | Valid |
| 2806:250:180e::/48 | RADB | Valid |
| 2806:250:180f::/48 | RADB | Valid |
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.