Network · data from 2026-11-12
AS48574 ASN-CZ-PLANET-A-48574 T-Mobile Czech Republic a.s.
Registry name: ASN-CZ-PLANET-A-48574 T-Mobile Czech Republic a.s., CZ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48574, 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.
| 109.238.208.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 185.248.176.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 217.30.64.0/20 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS48574 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 39 are in fix.csv.
- ROA: none3
- Route object: not announced36
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 109.238.208.0/20 | No ROA covers it. Add a ROA for AS48574, maxLength 20. |
| ROA: none | 185.248.176.0/22 | No ROA covers it. Add a ROA for AS48574, maxLength 22. |
| ROA: none | 217.30.64.0/20 | No ROA covers it. Add a ROA for AS48574, maxLength 20. |
Route objects not announced
Route objects with origin AS48574 whose prefix no peer sees AS48574 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.238.208.0/24 | RIPE | No ROA |
| 109.238.209.0/24 | RIPE | No ROA |
| 109.238.210.0/24 | RIPE | No ROA |
| 109.238.211.0/24 | RIPE | No ROA |
| 109.238.212.0/24 | RIPE | No ROA |
| 109.238.213.0/24 | RIPE | No ROA |
| 109.238.214.0/24 | RIPE | No ROA |
| 109.238.215.0/24 | RIPE | No ROA |
| 109.238.216.0/24 | RIPE | No ROA |
| 109.238.217.0/24 | RIPE | No ROA |
| 109.238.218.0/24 | RIPE | No ROA |
| 109.238.219.0/24 | RIPE | No ROA |
| 109.238.220.0/24 | RIPE | No ROA |
| 109.238.221.0/24 | RIPE | No ROA |
| 109.238.222.0/24 | RIPE | No ROA |
| 109.238.223.0/24 | RIPE | No ROA |
| 185.248.176.0/24 | RIPE | No ROA |
| 185.248.177.0/24 | RIPE | No ROA |
| 185.248.178.0/24 | RIPE | No ROA |
| 185.248.179.0/24 | RIPE | No ROA |
| 217.30.64.0/24 | RIPE | No ROA |
| 217.30.65.0/24 | RIPE | No ROA |
| 217.30.66.0/24 | RIPE | No ROA |
| 217.30.67.0/24 | RIPE | No ROA |
| 217.30.68.0/24 | RIPE | No ROA |
| 217.30.69.0/24 | RIPE | No ROA |
| 217.30.70.0/24 | RIPE | No ROA |
| 217.30.71.0/24 | RIPE | No ROA |
| 217.30.72.0/24 | RIPE | No ROA |
| 217.30.73.0/24 | RIPE | No ROA |
| 217.30.74.0/24 | RIPE | No ROA |
| 217.30.75.0/24 | RIPE | No ROA |
| 217.30.76.0/24 | RIPE | No ROA |
| 217.30.77.0/24 | RIPE | No ROA |
| 217.30.78.0/24 | RIPE | No ROA |
| 217.30.79.0/24 | RIPE | 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.