PHZ
BGP inherited
Cluster stats
| Netblocks | 17 |
| All fragments | 24 blocks across 3 clusters |
| Cluster ID | 205304653 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
4 weekly snapshots · JSON
17
0 netblocks since 2026-07-05
2026-07-05
peak 17
2026-07-13
IP Ranges (17)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 83.167.195.32/32 | PHZ | RIPE | ASSIGNED PA | ● low |
| 83.167.195.33/32 | PHZ | RIPE | ASSIGNED PA | ● low |
| 83.167.195.34/32 | PHZ | RIPE | ASSIGNED PA | ● low |
| 83.167.195.35/32 | PHZ | RIPE | ASSIGNED PA | ● low |
| 85.146.194.34/32 | PHZ | RIPE | ASSIGNED PA | ● low |
| 85.146.195.133/32 | PHZ | RIPE | ASSIGNED PA | ● low |
| 85.146.195.164/32 | PHZ | RIPE | ASSIGNED PA | ● low |
| 85.146.195.165/32 | PHZ | RIPE | ASSIGNED PA | ● low |
| 93.117.226.43/32 | PHZ | RIPE | ASSIGNED PA | ● low |
| 93.117.231.16/32 | PHZ | RIPE | ASSIGNED PA | ● low |
| 159.100.77.1/32 | PHZ | RIPE | LEGACY | ● low |
| 159.100.91.9/32 | PHZ | RIPE | LEGACY | ● low |
| 159.100.109.73/32 | PHZ | RIPE | LEGACY | ● low |
| 159.100.109.123/32 | PHZ | RIPE | LEGACY | ● low |
| 159.100.112.30/32 | PHZ | RIPE | LEGACY | ● low |
| 213.34.135.23/32 | PHZ | RIPE | ASSIGNED PA | ● low |
| 2a0e:b107:19b1::/48 | PHZ | RIPE | ASSIGNED | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “PHZ” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- PHZ-VIPOL 4 blocks
- PHZ-Baltona 3 blocks
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(17 of 17)
Possible discrepancies (1)
These blocks are registered to PHZ 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.
| 2a0e:b107:19b1::/48 /48 | authorized for AS206569 — Paul-Henri Zimmerlin |
NIC Handles
DUMY-RIPE
DUMY-RIPE
PHZ-MNT
TNF-MNT