Winogrady

Registry
Cluster stats
Netblocks8
All fragments 30 blocks across 2 clusters
Cluster ID213184210
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.4.36/32 Winogrady PEERINGDB ASSIGNED ● high
185.1.4.136/32 Winogrady PEERINGDB ASSIGNED ● high
195.182.218.94/32 Winogrady PEERINGDB ASSIGNED ● high
195.182.219.108/32 Winogrady PEERINGDB ASSIGNED ● high
2001:7f8:42::a519:7227:1/128 Winogrady PEERINGDB ASSIGNED ● high
2001:7f8:42::a519:7227:2/128 Winogrady PEERINGDB ASSIGNED ● high
2001:7f8:4b::24/128 Winogrady PEERINGDB ASSIGNED ● high
2001:7f8:4b::1:24/128 Winogrady PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “Winogrady” — 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.

Network trust

what's this?
RPKI hygiene: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (4 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS197227