PON-HOLDING
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 207 blocks across 19 clusters |
| Cluster ID | 208032953 |
| 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 | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 62.177.224.240/29 | Pon-Holding | RIPE | ASSIGNED PA | ● low |
| 193.172.138.0/24 | PON-HOLDING | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
Possible discrepancies (1)
These blocks are registered to PON-HOLDING 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.
| 193.172.138.0/24 /24 | authorized for AS1136 — KPN B.V. |
NIC Handles
AS286-MNT
DUMY-RIPE
DUMY-RIPE
NL-BBNET-MNT