Key Telecom
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 8 |
| IPv6 | 4 prefixes (largest 2001:7f8:20:401::87:105/128) |
| Cluster ID | 214593104 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 · report an issue | |
Footprint over time
6 weekly snapshots · JSON
8
0 netblocks since 2026-07-05
2026-07-05
peak 8
2026-07-26
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 |
IPv6 ranges (4)
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