Oops Telecom

Data as of 2026-09-20
BGP inherited
This organisation
Netblocks9
IPv6 4 prefixes (largest 2001:12f8:0:1::17/128)
Record ID242139445
RegistryPEERINGDB
Customerssee who runs inside 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

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.72.187/32 Oops Telecom PEERINGDB ASSIGNED ● high
45.227.1.19/32 Oops Telecom PEERINGDB ASSIGNED ● high
187.16.216.103/32 Oops Telecom PEERINGDB ASSIGNED ● high
200.219.130.17/32 Oops Telecom PEERINGDB ASSIGNED ● high
2001:12f8::103/128 Oops Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:1::17/128 Oops Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:9::187/128 Oops Telecom PEERINGDB ASSIGNED ● high
2001:12f8:0:31::19/128 Oops Telecom PEERINGDB ASSIGNED ● high
187.110.64.0/28 OOPS TELECOM LTDA ARIN REALLOCATED ● low

IPv6 ranges (4)

CIDR
2001:12f8:0:1::17/128
2001:12f8:0:31::19/128
2001:12f8:0:9::187/128
2001:12f8::103/128

Footprint over time

13 weekly snapshots · JSON
9 -4 netblocks since 2026-07-05
2026-07-05 peak 13 2026-09-20

Network trust

what's this?
RPKI hygiene: B how networks compare →
88.9% of checked blocks have valid RPKI ROA coverage (8 of 9)
No discrepancies found among checked blocks.

NIC Handles

16992716000152 AS28624 MVC101 MVC101 MVC101