Network · data from 2026-11-12
AS13036 T-Mobile CZ AS13036
Registry name: TMOBILE-CZ T-Mobile Czech Republic a.s., CZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS13036, 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.
| 46.13.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 62.77.64.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 62.84.128.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 62.141.0.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 62.168.0.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 62.209.192.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 78.80.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 80.95.240.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 89.24.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 89.233.128.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 91.139.0.0/17 | Valid | RIR databaseRIPE | 673 100% |
| 93.153.0.0/17 | Valid | RIR databaseRIPE | 673 100% |
| 109.75.144.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 109.183.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 185.14.188.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.85.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 193.86.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 193.179.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 194.108.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 194.149.96.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 194.212.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 194.213.32.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 194.213.192.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 195.22.32.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 195.39.0.0/17 | Valid | RIR databaseRIPE | 673 100% |
| 195.47.0.0/17 | Valid | RIR databaseRIPE | 673 100% |
| 195.70.128.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 195.144.96.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 212.47.0.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 212.65.192.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 212.67.64.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 213.29.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 213.210.128.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 37.48.0.0/18 | Valid | RIR databaseRIPE | 670 100% |
| 2001:af0::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2001:1ae8::/29 | Valid | RIR databaseRIPE | 635 100% |
| 2001:b80::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS13036's PeeringDB record names no AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS13036 is announced.
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.