Data as of Nov 16, 2026

81.173.96.0/22

5 residential-proxy exits · 30 days

Sewan Nederland B.V.

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

Residential-proxy exits

Proxy exits
5
0.49% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
31
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

296 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
81.173.96.0/2403
81.173.97.0/2401
81.173.98.0/2401

Proxy providers listing exits

  • AnyIP
  • BlurPath
  • BottingTools
  • Byteful
  • CatProxies
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • Geonode
  • HPROXY
  • HideProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • LudaxProxy
  • NiuProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • RainProxy
  • SPYDERPROXY_BASIC
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

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
81.173.96.0/221,024NL-POCOS-20030219Sewan Nederland B.V. (ORG-PB32-RIPE) · NLALLOCATED PAApr 23, 2019abuse@sewan.nl
└ 81.173.99.164/304Subscriber-35EgertonCresentSW32EB-LondonunknownASSIGNED PADec 1, 2020abuse@sewan.nl
via NL-POCOS-20030219

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 2017
Current origin since
Apr 2019 · 7.6 yr
Origin networks
2
Last change of origin
Apr 2019
Recorded history

History

Handoffs
1