PPPOE-KIEV-62-64-120-GTUA

BGP inherited
Cluster stats
Netblocks2
All fragments 5 blocks across 4 clusters
Cluster ID205319013
RegistryRIPE
Customersfind 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 (2)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.64.120.0 – 62.64.120.191 PPPOE-KIEV-62-64-120-GTUA RIPE ASSIGNED PA ● low
62.64.120.224 – 62.64.124.255 PPPOE-KIEV-62-64-120-GTUA RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “PPPOE KIEV 62 64” — 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.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

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 PPPOE-KIEV-62-64-120-GTUA 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.

62.64.120.224 – 62.64.124.255 /22 authorized for AS15895 — "Kyivstar" PJSC

NIC Handles

DUMY-RIPE DUMY-RIPE GTUA-WO-MNT