SHAM

BGP inherited
Cluster stats
Netblocks7
Registered in France (3) · China (1) · Israel (1) · JO (1) · KZ (1)
All fragments 10 blocks across 4 clusters
Cluster ID209022501
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 9 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
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
114.255.15.0/25 SHAM APNIC ASSIGNED NON-PORTABLE ● high
81.218.78.32/27 SHAM RIPE ASSIGNED PA ● low
82.200.244.144/30 SHAM RIPE ASSIGNED PA ● low
194.165.146.72/29 SHAM RIPE ASSIGNED PA ● low
213.30.178.184/30 SHAM RIPE ASSIGNED PA ● low
213.30.178.188/30 SHAM RIPE ASSIGNED PA ● low
213.30.178.192/29 SHAM RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “SHAM” — 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 →
85.7% of checked blocks have valid RPKI ROA coverage (6 of 7)
No discrepancies found among checked blocks.

NIC Handles

AS8551-MNT COMPLETEL-MNT DUMY-RIPE DUMY-RIPE GO-JOR KNIC-MNT MAINT-CNCGROUP-BJ ST638-AP ST638-AP