THEMIS

BGP inherited
Cluster stats
Netblocks6
Registered in Switzerland (2) · France (1) · NC (1)
All fragments 11 blocks across 6 clusters
Cluster ID204943900
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 10 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.23.55.20/32 THEMIS PEERINGDB ASSIGNED ● high
2001:df0:77c0::/48 THEMIS APNIC ASSIGNED PORTABLE ● high
2401:c00:1:4::20/128 THEMIS PEERINGDB ASSIGNED ● high
109.237.248.0 – 109.237.248.39 THEMIS RIPE ASSIGNED PA ● low
194.209.248.176/29 THEMIS-NET RIPE ASSIGNED PA ● low
212.243.229.120/29 THEMIS-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “THEMIS” — 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 (6 of 6)
No discrepancies found among checked blocks.

NIC Handles

APNIC-HM AS149520 AT1651-AP CH-UNISOURCE-MNT DUMY-RIPE DUMY-RIPE ORG-TA89-AP RMI-MNT TA353-AP TA353-AP