UPCLOUD-NL-AMS1-NET
Unresolved
Cluster stats
Netblocks11
All fragments 13 blocks across 3 clusters
Cluster ID192585455
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
11 0 netblocks since 2026-07-05
2026-07-05 peak 11 2026-07-06

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.22.208.0/22 UPCLOUD-NL-AMS1-NET RIPE ASSIGNED PA ● low
85.9.208.0/21 UPCLOUD-NL-AMS1-NET RIPE SUB-ALLOCATED PA ● low
85.9.208.0/22 UPCLOUD-NL-AMS1-NET RIPE ASSIGNED PA ● low
85.9.212.0/22 UPCLOUD-NL-AMS1-NET RIPE ASSIGNED PA ● low
85.9.216.0/23 UPCLOUD-NL-AMS1-NET RIPE ASSIGNED PA ● low
85.9.216.0/22 UPCLOUD-NL-AMS1-NET RIPE SUB-ALLOCATED PA ● low
85.9.218.0/23 UPCLOUD-NL-AMS1-NET RIPE ASSIGNED PA ● low
94.237.5.0/24 UPCLOUD-NL-AMS1-NET RIPE ASSIGNED PA ● low
94.237.6.0/24 UPCLOUD-NL-AMS1-NET RIPE ASSIGNED PA ● low
94.237.7.0/24 UPCLOUD-NL-AMS1-NET RIPE ASSIGNED PA ● low
94.237.108.0/22 UPCLOUD-NL-AMS1-NET RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (11 of 11)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-UPCLOUD