Key Telecom
Cluster stats
| Netblocks | 8 |
| All fragments | 241 blocks across 63 clusters |
| Cluster ID | 193390756 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (8)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 91.221.180.78/32 | Key Telecom | PEERINGDB | ASSIGNED | ● high |
| 91.221.180.79/32 | Key Telecom | PEERINGDB | ASSIGNED | ● high |
| 193.232.87.105/32 | Key Telecom | PEERINGDB | ASSIGNED | ● high |
| 193.232.87.110/32 | Key Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:401::87:105/128 | Key Telecom | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:401::87:110/128 | Key Telecom | PEERINGDB | ASSIGNED | ● high |
| 2a0b:9fc0:1:0:3:9701:180:78/128 | Key Telecom | PEERINGDB | ASSIGNED | ● high |
| 2a0b:9fc0:1:0:3:9701:180:79/128 | Key Telecom | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(4 of 8)
No discrepancies found among checked blocks.
NIC Handles
AS49814