INET-GT-KIEV-188-163-234-GTUA
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 9 blocks across 9 clusters |
| Cluster ID | 208721995 |
| 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 (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 188.163.234.0/24 | INET-GT-KIEV-188-163-234-GTUA | RIPE | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “INET GT KIEV 188 163” — 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.
- INET-GT-KIEV-188-163-237-GTUA 1 blocks
- INET-GT-KIEV-188-163-238-GTUA 1 blocks
- INET-GT-KIEV-188-163-239-GTUA 1 blocks
- INET-GT-KIEV-188-163-232-GTUA 1 blocks
- INET-GT-KIEV-188-163-235-GTUA 1 blocks
- INET-GT-KIEV-188-163-236-GTUA 1 blocks
- INET-GT-KIEV-188-163-208-GTUA 1 blocks
- INET-GT-KIEV-188-163-233-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.
- INET-SOL-KIEV-188-163-242-GTUA via "Kyivstar" PJSC sub-allocation
- INET-GT-KIEV-188-163-237-GTUA via "Kyivstar" PJSC sub-allocation
- INET-GT-KIEV-188-163-238-GTUA via "Kyivstar" PJSC sub-allocation
- INET-GT-KIEV-188-163-239-GTUA via "Kyivstar" PJSC sub-allocation
- INET-GT-KIEV-94-27-61-160-GTUA via "Kyivstar" PJSC sub-allocation
- INET-SOL-KIEV-188-163-246-GTUA via "Kyivstar" PJSC sub-allocation
- INET-SOL-KIEV-188-163-247-GTUA via "Kyivstar" PJSC sub-allocation
- optinet2_kiev_ua via "SCIENTIFIC-INDUSTRIAL FIRM "VOLZ" LIMITED LIABILITY COMPANY sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
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-MNT