NET-TEL-6

Data as of 2026-08-30
BGP inherited
Cluster stats
Netblocks20
IPv6 20 prefixes (largest 2a0b:3c00::/30)
Cluster ID234275921
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

10 weekly snapshots · JSON
20 0 netblocks since 2026-07-05
2026-07-05 peak 20 2026-08-30

IP Ranges (20)

⬇ export CSV
CIDR Org name Registry Status Confidence
2a0b:3c00::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a0b:3c04::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a11:5940::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a11:5944::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a11:7c40::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a11:7c44::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a11:98c0::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a11:98c4::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a11:c340::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a11:c344::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a12:6c00::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a12:6c04::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a12:8300::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a12:8304::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a12:8d80::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a12:8d84::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a12:f080::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a12:f084::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a12:fb00::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low
2a12:fb04::/30 NET-TEL-6 RIPE AGGREGATED-BY-LIR ● low

IPv6 ranges (20)

showing the 15 largest allocations
CIDR
2a0b:3c00::/30
2a0b:3c04::/30
2a11:5940::/30
2a11:5944::/30
2a11:7c40::/30
2a11:7c44::/30
2a11:98c0::/30
2a11:98c4::/30
2a11:c340::/30
2a11:c344::/30
2a12:6c00::/30
2a12:6c04::/30
2a12:8300::/30
2a12:8304::/30
2a12:8d80::/30

Network trust

what's this?
RPKI hygiene: F how networks compare →
10.0% of checked blocks have valid RPKI ROA coverage (2 of 20)
RPKI-inferred operator iNet Ltd
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE T-MNT