VERIZON-CZ
BGP inherited
Cluster stats
| Netblocks | 5 |
| All fragments | 6 blocks across 2 clusters |
| Cluster ID | 210615026 |
| Registry | RIPE |
| Customers | find customers using 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 | |
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 62.209.222.16/28 | VERIZON-CZ | RIPE | ASSIGNED PA | ● low |
| 193.85.215.48/30 | VERIZON-CZ | RIPE | ASSIGNED PA | ● low |
| 193.86.226.128/29 | VERIZON-CZ | RIPE | ASSIGNED PA | ● low |
| 195.39.4.200/29 | VERIZON-CZ | RIPE | ASSIGNED PA | ● low |
| 2001:af0:800f::/48 | VERIZON-CZ | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(5 of 5)
Possible discrepancies (1)
These blocks are registered to VERIZON-CZ but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2001:af0:800f::/48 /48 | authorized for AS13036 — T-Mobile Czech Republic a.s. |
NIC Handles
DUMY-RIPE
DUMY-RIPE
GTSCZ-MNT