POLITEH_KOLL
BGP inherited
Cluster stats
| Netblocks | 4 |
| Cluster ID | 205167811 |
| 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 (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 82.200.197.188/30 | POLITEH_KOLL | RIPE | ASSIGNED PA | ● low |
| 95.59.233.212/30 | POLITEH_KOLL | RIPE | ASSIGNED PA | ● low |
| 95.59.233.216/30 | POLITEH_KOLL | RIPE | ASSIGNED PA | ● low |
| 95.59.233.224/28 | POLITEH_KOLL | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?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.
- POLITEH_KOLLEDG via JSC Kazakhtelecom sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
KNIC-MNT