Network · data from 2026-11-12
AS28557 AS28557 - Cablemas Telecomunicaciones SA de CV
Registry name: AS28557 - Cablemas Telecomunicaciones SA de CV, MX · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28557, 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.
| 200.56.221.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 189.215.10.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 189.215.11.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 2806:250:a00::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2806:250:a01::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2806:250:a02::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2806:250:a03::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2806:250:a04::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2806:250:a05::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2806:250:a06::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2806:250:a07::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2806:250:a09::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2806:250:a0a::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2806:250:a0b::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 2806:250:a0f::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 189.215.9.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 2806:250:a08::/48 | Valid | RIR databaseLACNIC, RADB | 635 100% |
AS-SET
AS28557 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 18 are in fix.csv.
- ROA: none1
- Route object: RIR15
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 200.56.221.0/24 | No ROA covers it. Add a ROA for AS28557, maxLength 24. |
| Route object: RIR | 200.56.221.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 189.215.10.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 189.215.11.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2806:250:a00::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2806:250:a01::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2806:250:a02::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2806:250:a03::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2806:250:a04::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2806:250:a05::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2806:250:a06::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2806:250:a07::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2806:250:a09::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2806:250:a0a::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2806:250:a0b::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2806:250:a0f::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS28557 whose prefix no peer sees AS28557 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 189.215.10.0/23 | LACNIC | Valid |
| 2806:250:a00::/40 | LACNIC, 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.