Network · data from 2026-11-12
AS28414 AS28414 - TOTAL PLAY TELECOMUNICACIONES, S.A.P.I. DE C.V.
Registry name: AS28414 - TOTAL PLAY TELECOMUNICACIONES, S.A.P.I. DE C.V., MX · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28414, 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.23.114.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 200.23.188.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 200.33.240.0/24 | No ROA | Other IRR onlyRADB | 666 99% |
| 200.33.241.0/24 | No ROA | Other IRR onlyRADB | 666 99% |
| 200.33.244.0/24 | No ROA | Other IRR onlyRADB | 666 99% |
| 200.23.6.0/24 | No ROA | Other IRR onlyRADB | 607 90% |
| 189.203.240.0/24 | No ROA | Other IRR onlyRADB | 48 7%low visibility |
| 192.100.188.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 187.251.236.0/24 | Valid | RIR databaseLACNIC | 46 7%low visibility |
| 189.203.24.0/24 | Valid | RIR databaseLACNIC | 44 7%low visibility |
| 187.251.197.0/24 | Valid | RIR databaseLACNIC | 43 6%low visibility |
AS-SET
AS28414 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 17 are in fix.csv.
- ROA: none7
- Route object: RIR8
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 200.23.114.0/24 | No ROA covers it. Add a ROA for AS28414, maxLength 24. |
| Route object: RIR | 200.23.114.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 200.23.188.0/24 | No ROA covers it. Add a ROA for AS28414, maxLength 24. |
| Route object: RIR | 200.23.188.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 200.33.240.0/24 | No ROA covers it. Add a ROA for AS28414, maxLength 24. |
| Route object: RIR | 200.33.240.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 200.33.241.0/24 | No ROA covers it. Add a ROA for AS28414, maxLength 24. |
| Route object: RIR | 200.33.241.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 200.33.244.0/24 | No ROA covers it. Add a ROA for AS28414, maxLength 24. |
| Route object: RIR | 200.33.244.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 200.23.6.0/24 | No ROA covers it. Add a ROA for AS28414, maxLength 24. |
| Route object: RIR | 200.23.6.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 189.203.240.0/24 | No ROA covers it. Add a ROA for AS28414, maxLength 24. |
| Route object: RIR | 189.203.240.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.100.188.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS28414 whose prefix no peer sees AS28414 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 187.188.110.0/24 | LACNIC | Valid |
| 207.248.118.0/23 | RADB | No 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.