Pavel Zizka
ORELSOFT
Cluster stats
Netblocks11
All fragments 14 blocks across 4 clusters
Cluster ID193384213
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
89.46.144.223/32 ORELSOFT PEERINGDB ASSIGNED ● high
178.216.40.146/32 ORELSOFT PEERINGDB ASSIGNED ● high
178.216.41.118/32 ORELSOFT PEERINGDB ASSIGNED ● high
195.149.233.162/32 ORELSOFT PEERINGDB ASSIGNED ● high
2001:678:3ac::223/128 ORELSOFT PEERINGDB ASSIGNED ● high
2001:7f8:5b::146/128 ORELSOFT PEERINGDB ASSIGNED ● high
2001:7f8:5b::523/128 ORELSOFT PEERINGDB ASSIGNED ● high
2a06:bfc0::/30 orelsoft-net RIPE ASSIGNED ● low
2a06:bfc4::/30 orelsoft-net RIPE ASSIGNED ● low
2a0b:4280::/30 orelsoft-net RIPE ASSIGNED ● low
2a0b:4284::/30 orelsoft-net RIPE ASSIGNED ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
63.6% of checked blocks have valid RPKI ROA coverage (7 of 11)
Possible discrepancies (2)

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

2a06:bfc0::/30 /30 authorized for AS200918 — Pavel Zizka
2a06:bfc4::/30 /30 authorized for AS200918 — Pavel Zizka

NIC Handles

AS200918 DUMY-RIPE DUMY-RIPE cz-zizka-1-mnt