SOTPM-NET

BGP inherited
Cluster stats
Netblocks9
All fragments 10 blocks across 2 clusters
Cluster ID210418234
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
37.109.1.160/29 SOTPM-NET RIPE ASSIGNED PA ● low
37.109.30.112/30 SOTPM-NET RIPE ASSIGNED PA ● low
37.247.231.156/30 SOTPM-NET RIPE ASSIGNED PA ● low
37.247.231.232/29 SOTPM-NET RIPE ASSIGNED PA ● low
37.247.231.240/29 SOTPM-NET RIPE ASSIGNED PA ● low
37.247.232.8/29 SOTPM-NET RIPE ASSIGNED PA ● low
37.247.232.16/29 SOTPM-NET RIPE ASSIGNED PA ● low
37.247.232.24/29 SOTPM-NET RIPE ASSIGNED PA ● low
178.183.3.184/30 SOTPM RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “SOTPM” — 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.
  • Krakow via Netia SA sub-allocation

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
No discrepancies found among checked blocks.

NIC Handles

AS12912-AUX-MNT DUMY-RIPE DUMY-RIPE POLKOMTEL-MNT