Sownet

Data as of 2026-11-01
Registry
This organisation
Netblocks9 · 1,091 IPv4 addresses
IPv6 2 prefixes (largest 2001:678:3ac::271/128)
Record ID261130613
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
83.230.15.0/24 SOWNET RIPE ASSIGNED PA ● high
89.46.145.23/32 Sownet PEERINGDB ASSIGNED ● high
178.216.40.158/32 Sownet PEERINGDB ASSIGNED ● high
195.82.176.0/24 SOWNET RIPE ASSIGNED PA ● high
195.82.178.0/23 SOWNET RIPE ASSIGNED PA ● high
195.82.188.0/26 SOWNET RIPE ASSIGNED PA ● high
195.149.233.219/32 Sownet PEERINGDB ASSIGNED ● high
2001:678:3ac::271/128 Sownet PEERINGDB ASSIGNED ● high
2001:7f8:5b::158/128 Sownet PEERINGDB ASSIGNED ● high

IPv6 ranges (2)

Footprint over time

19 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-11-01

Network trust

what's this?
RPKI hygiene: B how networks compare →
88.9% of checked blocks have valid RPKI ROA coverage (8 of 9)
Possible discrepancies (1)

These blocks are registered to Sownet 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.

83.230.15.0/24 /24 authorized for AS35434 — PirxNet Grzegorz Bialas

NIC Handles

AS62031 DUMY-RIPE DUMY-RIPE PL-CKPOLSL-MNT STG23-RIPE