SAPIENT

BGP inherited
Cluster stats
Netblocks10 · 391 IPv4 addresses
Registered in Germany (8) · India (1)
All fragments 18 blocks across 9 clusters
Cluster ID209934672
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names 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
103.43.3.0/24 SAPIENT APNIC ASSIGNED PORTABLE ● high
2001:df4:740::/48 SAPIENT APNIC ASSIGNED PORTABLE ● high
62.53.229.64/28 SAPIENT RIPE ASSIGNED PA ● low
62.53.229.144/29 SAPIENT RIPE ASSIGNED PA ● low
62.53.229.176/28 SAPIENT RIPE ASSIGNED PA ● low
62.53.229.232/29 SAPIENT RIPE ASSIGNED PA ● low
62.53.229.240/28 SAPIENT RIPE ASSIGNED PA ● low
213.20.225.128/27 SAPIENT RIPE ASSIGNED PA ● low
213.20.238.96/27 SAPIENT RIPE ASSIGNED PA ● low
217.188.215.80/28 SAPIENT RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

DUMY-RIPE DUMY-RIPE MAINT-IN-IRINN MDA-Z MN416-AP MN416-AP