PPPOE-KIEV-GTUA
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 21 blocks across 19 clusters |
| Cluster ID | 208458131 |
| 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 (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 89.162.248.0/24 | PPPOE-KIEV-GTUA | RIPE | ASSIGNED PA | ● low |
| 89.162.250.0/24 | PPPOE-KIEV-GTUA | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “PPPOE KIEV” — 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.
- PPPOE-KIEV-62-64-120-GTUA 2 blocks
- PPPoE-KIEV-89-162-153-GTUA 1 blocks
- PPPoE-KIEV-85-223-203-GTUA 1 blocks
- PPPoE-KIEV-85-223-200-GTUA 1 blocks
- PPPoE-KIEV-85-223-201-GTUA 1 blocks
- PPPoE-KIEV-85-223-202-GTUA 1 blocks
- PPPoE-KIEV-89-162-156-GTUA 1 blocks
- PPPoE-KIEV-89-162-152-GTUA 1 blocks
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.
- PPPoE-KIEV-89-162-152-GTUA via "Kyivstar" PJSC sub-allocation
- PPPoE-KIEV-89-162-153-GTUA via "Kyivstar" PJSC sub-allocation
- PPPoE-KIEV-89-162-156-GTUA via "Kyivstar" PJSC sub-allocation
- INET-PPPoE-KIEV-89-162-238-GTUA via "Kyivstar" PJSC sub-allocation
- INET-PPPoE-KIEV-89-162-239-GTUA via "Kyivstar" PJSC sub-allocation
- INET-PPPoE-KIEV-89-162-162-GTUA via "Kyivstar" PJSC sub-allocation
- PPPoE-KIEV-85-223-200-GTUA via "Kyivstar" PJSC sub-allocation
- PPPoE-KIEV-85-223-201-GTUA via "Kyivstar" PJSC sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
RPKI-inferred operator
"Kyivstar" PJSC
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
DUMY-RIPE
DUMY-RIPE
GTUA-WO-MNT