Data as of Nov 21, 2026

217.61.104.0/21

1 residential-proxy exit · 30 days

Aruba S.p.A.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
1
0.05% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
18
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

110 observations

Proxy providers listing exits

  • BottingTools
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • GEEKPROXY_TURBO
  • GloryCloud
  • IPFly
  • IPMUSK
  • KindProxy
  • MoMoProxy
  • NSTPROXY_PRIME
  • NiuProxy
  • Novada
  • Proxiware
  • ProxyRack
  • RapidProxy
  • SCRAPELESS
  • SwiftProxy
  • VitalExclusive

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.61.96.0/198,192IT-TECHNORAIL-20001101Aruba S.p.A. (ORG-TS9-RIPE) · ITALLOCATED PADec 9, 2025abuse@staff.aruba.it
└ 217.61.104.0/24256ARUBADE-NETAruba GmbH Cloud NetworkASSIGNED PAJan 30, 2017abuse@staff.aruba.it
via IT-TECHNORAIL-20001101
└ 217.61.105.0/24256ARUBADE-NETAruba GmbH Cloud NetworkASSIGNED PAJan 30, 2017abuse@staff.aruba.it
via IT-TECHNORAIL-20001101
└ 217.61.106.0/24256ARUBADE-NETAruba GmbH Cloud NetworkASSIGNED PAJan 30, 2017abuse@staff.aruba.it
via IT-TECHNORAIL-20001101
└ 217.61.107.0/24256ARUBADE-NETAruba GmbH Cloud NetworkASSIGNED PAJan 30, 2017abuse@staff.aruba.it
via IT-TECHNORAIL-20001101
└ 217.61.108.0/24256ARUBADE-NETAruba GmbH - Cloud Services DEASSIGNED PAJan 30, 2017abuse@staff.aruba.it
via IT-TECHNORAIL-20001101
└ 217.61.109.0/24256ARUBADE-NETAruba GmbH Cloud NetworkASSIGNED PAJan 30, 2017abuse@staff.aruba.it
via IT-TECHNORAIL-20001101
└ 217.61.110.0/24256ARUBADE-NETAruba GmbH Cloud NetworkASSIGNED PAJan 30, 2017abuse@staff.aruba.it
via IT-TECHNORAIL-20001101
└ 217.61.111.0/24256ARUBADE-NETAruba GmbH Cloud NetworkASSIGNED PAJan 30, 2017abuse@staff.aruba.it
via IT-TECHNORAIL-20001101

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2016
Current origin since
Jan 2017 · 9.8 yr
Origin networks
2
Last change of origin
Jan 2017
Recorded history

History

Handoffs
1