THO010

BGP inherited
Cluster stats
Netblocks8
All fragments 10 blocks across 3 clusters
Cluster ID210763383
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
78.110.166.104/29 THO010 RIPE ASSIGNED PA ● low
78.157.210.108/30 THO010 RIPE ASSIGNED PA ● low
94.46.245.196/30 THO010 RIPE ASSIGNED PA ● low
94.229.67.72/29 THO010 RIPE ASSIGNED PA ● low
94.229.72.192/30 THO010 RIPE ASSIGNED PA ● low
185.17.24.136/29 THO010 RIPE ASSIGNED PA ● low
185.99.254.72/29 THO010 RIPE ASSIGNED PA ● low
2a01:a500:2263::/48 THO010 RIPE AGGREGATED-BY-LIR ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “THO010” — 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 (8 of 8)
Possible discrepancies (1)

These blocks are registered to THO010 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:2263::/48 /48 authorized for AS42831 — UK Dedicated Servers Limited

NIC Handles

DUMY-RIPE DUMY-RIPE UKSERVERS-MNT