TWT-CUST-6161

BGP inherited
Cluster stats
Netblocks8
All fragments 47,538 blocks across 32,957 clusters
Cluster ID210849544
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

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.63.171.236/30 TWT-CUST-6161 RIPE ASSIGNED PA ● low
77.239.150.48/30 TWT-CUST-6161 RIPE ASSIGNED PA ● low
80.210.100.168/30 TWT-CUST-6161 RIPE ASSIGNED PA ● low
80.210.105.92/30 TWT-CUST-6161 RIPE ASSIGNED PA ● low
80.210.123.128/30 TWT-CUST-6161 RIPE ASSIGNED PA ● low
80.210.123.196/30 TWT-CUST-6161 RIPE ASSIGNED PA ● low
82.113.221.216/30 TWT-CUST-6161 RIPE ASSIGNED PA ● low
95.142.178.104/30 TWT-CUST-6161 RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “TWT CUST” — 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.
Combined view of all 32,957 name-family clusters →
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 (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE IT-TWT-MNT