OP TELECOM
Data as of 2026-08-16
BGP inherited
Cluster stats
| Netblocks | 5 · 1,026 IPv4 addresses |
| IPv6 | 2 prefixes (largest 2001:12f8::208:117/128) |
| Cluster ID | 222462712 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
3 weekly snapshots · JSON
18
+1 netblocks since 2026-07-05
2026-07-05
peak 18
2026-07-12
IP Ranges (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 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 |
| 45.166.112.0/22 | OP TELECOM | ARIN | ALLOCATED | ● low |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: B
how networks compare →
80.0%
of checked blocks have valid RPKI ROA coverage
(4 of 5)
No discrepancies found among checked blocks.
NIC Handles
18473954000187
AS267955
GUCSI48
GUCSI48
UETLT4