Data as of Nov 13, 2026

217.145.32.0/23

2 residential-proxy exits · 30 days

IP Nexia N.V.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Internet provider
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
2
0.39% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
9
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

58 observations

Proxy providers listing exits

  • BlurPath
  • BottingTools
  • CliProxy
  • IPFly
  • IPPeak
  • MoMoProxy
  • NovProxy
  • PuraRoute
  • RainProxy

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.145.32.0/204,096BE-TOLEDO-20010221IP Nexia N.V. (ORG-TTS7-RIPE) · BEALLOCATED PA—abuse@ipnexia.com
└ 217.145.32.0/23512IPNexia-BASE-NETunknownASSIGNED PAMay 30, 2002abuse@ipnexia.com
via BE-TOLEDO-20010221

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 2005
Current origin since
May 2005 · 22 yr
Origin networks
1