Oops Telecom
Cluster stats
Netblocks13
Cluster ID193085504
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 9 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (13)

⬇ 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
203.131.95.168/29 OOPS-PH APNIC ASSIGNED NON-PORTABLE ● 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
182.71.224.144/29 OOPS-3283439-Bangalore APNIC ASSIGNED NON-PORTABLE ● low
182.72.114.240/29 OOPS-3277425-Mumbai APNIC ASSIGNED NON-PORTABLE ● low
182.75.15.151/32 OOPS-3283439-Bangalore APNIC ASSIGNED NON-PORTABLE ● low
182.78.184.84/30 OOPS-3283439-Bangalore APNIC ASSIGNED NON-PORTABLE ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (13 of 13)
No discrepancies found among checked blocks.

NIC Handles

AB913-AP AE135-AP AS28624 JA47-AP JA47-AP MAINT-IN-BBIL MAINT-PH-EPLDT NA40-AP NA40-AP