RES.PL

Data as of 2026-09-06
Registry
This organisation
Netblocks6
IPv6 2 prefixes (largest 2001:678:3ac::119/128)
Record ID239845368
RegistryPEERINGDB
Customerssee who runs inside 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 · report an issue

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
89.46.144.119/32 RES.PL PEERINGDB ASSIGNED ● high
178.216.41.101/32 RES.PL PEERINGDB ASSIGNED ● high
185.1.42.253/32 RES.PL PEERINGDB ASSIGNED ● high
195.149.233.66/32 RES.PL PEERINGDB ASSIGNED ● high
2001:678:3ac::119/128 RES.PL PEERINGDB ASSIGNED ● high
2001:7f8:5b::357/128 RES.PL PEERINGDB ASSIGNED ● high

IPv6 ranges (2)

Footprint over time

8 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-08-30

Network trust

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

NIC Handles

AS42981