TMCZ_GPON
Data as of 2026-09-06
BGP inherited
This organisation
| Netblocks | 18 · 26,624 IPv4 addresses |
| Also registered under this name | 19 netblocks across 2 separate records |
| Record ID | 238457804 |
| Registry | RIPE |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (18)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 78.80.32.0/21 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
| 78.80.40.0/21 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
| 78.80.80.0/20 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
| 78.80.144.0/20 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
| 78.80.160.0/21 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
| 78.80.168.0/22 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
| 78.80.172.0/22 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
| 78.80.176.0/20 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
| 193.179.32.0/21 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
| 193.179.48.0/21 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
| 193.179.60.0/24 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
| 193.179.61.0/24 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
| 193.179.66.0/24 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
| 193.179.67.0/24 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
| 194.212.224.0/24 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
| 194.212.225.0/24 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
| 194.212.226.0/24 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
| 194.212.227.0/24 | TMCZ_GPON | RIPE | ASSIGNED PA | ● low |
Footprint over time
11 weekly snapshots · JSON
18
0 netblocks since 2026-07-05
2026-07-05
peak 18
2026-09-06
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(18 of 18)
RPKI-inferred operator
T-Mobile Czech Republic a.s.
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
AS13036-MNT
DUMY-RIPE
DUMY-RIPE