TIEHALLINTO-NET

BGP inherited
Cluster stats
Netblocks10
All fragments 12 blocks across 3 clusters
Cluster ID209040795
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
192.130.84.200/29 TIEHALLINTO-NET RIPE ASSIGNED PA ● low
192.130.84.228/30 TIEHALLINTO-NET RIPE ASSIGNED PA ● low
193.209.247.148/30 TIEHALLINTO-NET RIPE ASSIGNED PA ● low
193.209.247.152/29 TIEHALLINTO-NET RIPE ASSIGNED PA ● low
193.209.254.0/26 TIEHALLINTO-NET RIPE ASSIGNED PA ● low
194.137.197.144/29 TIEHALLINTO-NET RIPE ASSIGNED PA ● low
212.50.130.0/29 TIEHALLINTO-NET RIPE ASSIGNED PA ● low
212.182.219.28/30 TIEHALLINTO-NET RIPE ASSIGNED PA ● low
213.139.168.180/30 TIEHALLINTO-NET RIPE ASSIGNED PA ● low
213.216.194.248/29 TIEHALLINTO-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “TIEHALLINTO” — 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: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

DATANET-NOC DUMY-RIPE DUMY-RIPE FI2G-MNT