TTNC-NET

BGP inherited
Cluster stats
Netblocks6 · 330 IPv4 addresses
All fragments 14 blocks across 4 clusters
Cluster ID204571254
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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

Footprint over time

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

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.254.152.8/29 TTNC-LTD RIPE ASSIGNED PA ● low
62.255.2.208/28 TTNC-LTD RIPE ASSIGNED PA ● low
84.45.99.168/29 TTNC-NET RIPE ASSIGNED PA ● low
84.45.100.192/28 TTNC-NET RIPE ASSIGNED PA ● low
84.45.107.0/24 TTNC-NET RIPE ASSIGNED PA ● low
213.106.144.192/27 TTNC-LTD RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “TTNC” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
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: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (3 of 6)
No discrepancies found among checked blocks.

NIC Handles

AS5089-MNT C4L-MNT DUMY-RIPE DUMY-RIPE