TAH002

BGP inherited
Cluster stats
Netblocks10
Cluster ID210663723
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
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
5.101.140.48/30 TAH002 RIPE ASSIGNED PA ● low
5.101.142.180/30 TAH002 RIPE ASSIGNED PA ● low
5.101.151.216/30 TAH002 RIPE ASSIGNED PA ● low
5.101.168.52/30 TAH002 RIPE ASSIGNED PA ● low
37.9.59.84/30 TAH002 RIPE ASSIGNED PA ● low
37.9.63.132/30 TAH002 RIPE ASSIGNED PA ● low
77.74.193.188/30 TAH002 RIPE ASSIGNED PA ● low
94.46.195.228/30 TAH002 RIPE ASSIGNED PA ● low
185.103.97.168/30 TAH002 RIPE ASSIGNED PA ● low
2a01:a500:1938::/48 TAH002 RIPE AGGREGATED-BY-LIR ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (10 of 10)
Possible discrepancies (1)

These blocks are registered to TAH002 but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a01:a500:1938::/48 /48 authorized for AS42831 — UK Dedicated Servers Limited

NIC Handles

DUMY-RIPE DUMY-RIPE UKSERVERS-MNT