I3 NET TELECOM

BGP inherited
Cluster stats
Netblocks6
Cluster ID207725849
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
6 -6 netblocks since 2026-07-05
2026-07-05 peak 13 2026-07-13

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.75.199/32 I3 NET TELECOM PEERINGDB ASSIGNED ● high
187.16.195.59/32 I3 NET TELECOM PEERINGDB ASSIGNED ● high
187.16.208.5/32 I3 NET TELECOM PEERINGDB ASSIGNED ● high
2001:12f8::208:5/128 I3 NET TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:9::147:199/128 I3 NET TELECOM PEERINGDB ASSIGNED ● high
2001:12f8:0:18::59/128 I3 NET TELECOM PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

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

NIC Handles

AS273380