Windyghoul

Data as of 2026-09-13
Registry
This organisation
Netblocks7 · 817 IPv4 addresses
IPv6 1 prefix (largest 2001:7f8:14::9d:1/128)
Also registered under this name 15 netblocks across 2 separate records
Record ID241900188
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution Registry record
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 (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
91.210.16.231/32 Windyghoul PEERINGDB ASSIGNED ● high
2001:7f8:14::9d:1/128 Windyghoul PEERINGDB ASSIGNED ● high
82.100.28.0/24 Windyghoul RIPE ASSIGNED PA ● low
95.80.216.224/28 Windyghoul RIPE ASSIGNED PA ● low
95.80.218.0/24 Windyghoul RIPE ASSIGNED PA ● low
95.80.228.0/24 Windyghoul RIPE ASSIGNED PA ● low
95.80.229.96/27 Windyghoul RIPE ASSIGNED PA ● low

IPv6 ranges (1)

Footprint over time

12 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-09-13

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
Possible discrepancies (3)

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

82.100.28.0/24 /24 authorized for AS29208 — Quantcom, a.s.
95.80.218.0/24 /24 authorized for AS29208 — Quantcom, a.s.
95.80.228.0/24 /24 authorized for AS29208 — Quantcom, a.s.

NIC Handles

AS205535 DIALTELECOM-MNT DUMY-RIPE DUMY-RIPE