ORELSOFT

Data as of 2026-09-20
BGP inherited
This organisation
Netblocks11
IPv6 7 prefixes (largest 2a06:bfc0::/30)
Also registered under this name 14 netblocks across 4 separate records
Record ID242143816
RegistryPEERINGDB
Customerssee who runs inside 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 · report an issue

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

IPv6 ranges (7)

CIDR
2a06:bfc0::/30
2a06:bfc4::/30
2a0b:4280::/30
2a0b:4284::/30
2001:678:3ac::223/128
2001:7f8:5b::146/128
2001:7f8:5b::523/128

Footprint over time

13 weekly snapshots · JSON
11 0 netblocks since 2026-07-05
2026-07-05 peak 11 2026-09-20

Network trust

what's this?
RPKI hygiene: C how networks compare →
72.7% of checked blocks have valid RPKI ROA coverage (8 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