OTEL Telecoms
Cluster stats
Netblocks16
All fragments 22 blocks across 6 clusters
Cluster ID193382456
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
196.10.141.40/32 OTEL Telecoms PEERINGDB ASSIGNED ● high
196.60.8.209/32 OTEL Telecoms PEERINGDB ASSIGNED ● high
196.60.9.10/32 OTEL Telecoms PEERINGDB ASSIGNED ● high
196.60.70.195/32 OTEL Telecoms PEERINGDB ASSIGNED ● high
196.60.96.75/32 OTEL Telecoms PEERINGDB ASSIGNED ● high
196.223.15.32/32 OTEL Telecoms PEERINGDB ASSIGNED ● high
196.223.22.75/32 OTEL Telecoms PEERINGDB ASSIGNED ● high
196.223.30.75/32 OTEL Telecoms PEERINGDB ASSIGNED ● high
2001:43f8:1f0::75/128 OTEL Telecoms PEERINGDB ASSIGNED ● high
2001:43f8:1f1::75/128 OTEL Telecoms PEERINGDB ASSIGNED ● high
2001:43f8:1f2::75/128 OTEL Telecoms PEERINGDB ASSIGNED ● high
2001:43f8:6d0::209/128 OTEL Telecoms PEERINGDB ASSIGNED ● high
2001:43f8:6d0::9:10/128 OTEL Telecoms PEERINGDB ASSIGNED ● high
2001:43f8:6d1::195/128 OTEL Telecoms PEERINGDB ASSIGNED ● high
2001:43f8:6d2::40/128 OTEL Telecoms PEERINGDB ASSIGNED ● high
79.134.220.112/29 OTEL-LAN RIPE ASSIGNED PA ● low

Network trust

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

NIC Handles

AS37356 DUMY-RIPE DUMY-RIPE OBIT-MNT