OP TELECOM
Cluster stats
Netblocks17
All fragments 134 blocks across 44 clusters
Cluster ID191607467
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 2 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (17)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.166.112.0/23 OP TELECOM BGP ANNOUNCED ● high
45.166.112.0/24 OP TELECOM BGP ANNOUNCED ● high
45.166.112.0/22 OP TELECOM BGP ANNOUNCED ● high
45.166.113.0/24 OP TELECOM BGP ANNOUNCED ● high
45.166.114.0/24 OP TELECOM BGP ANNOUNCED ● high
45.166.114.0/23 OP TELECOM BGP ANNOUNCED ● high
45.166.115.0/24 OP TELECOM BGP ANNOUNCED ● high
187.16.208.117/32 OP TELECOM PEERINGDB ASSIGNED ● high
187.16.218.140/32 OP TELECOM PEERINGDB ASSIGNED ● high
2001:12f8::208:117/128 OP TELECOM PEERINGDB ASSIGNED ● high
2001:12f8::218:140/128 OP TELECOM PEERINGDB ASSIGNED ● high
2804:55c4::/33 OP TELECOM BGP ANNOUNCED ● high
2804:55c4::/32 OP TELECOM BGP ANNOUNCED ● high
2804:55c4:8000::/33 OP TELECOM BGP ANNOUNCED ● high
2804:55c4:ec00::/44 OP TELECOM BGP ANNOUNCED ● high
2804:55c4:ec00::/46 OP TELECOM BGP ANNOUNCED ● high
2804:55c4:ec04::/46 OP TELECOM BGP ANNOUNCED ● high

Network trust

what's this?
RPKI hygiene: D how networks compare →
23.5% of checked blocks have valid RPKI ROA coverage (4 of 17)
No discrepancies found among checked blocks.

NIC Handles

AS267955 AS267955