Data as of Nov 11, 2026

66.201.4.0/22

12 residential-proxy exits · 30 days

Nebius B.V.

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

Residential-proxy exits

Proxy exits
12
1.2% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
50
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.8K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
66.201.4.0/2405
66.201.5.0/2403
66.201.7.0/2403
66.201.6.0/2401

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FROXY
  • FastProxy
  • FloppyData
  • GSocks
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

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
66.201.0.0/198,192NL-NEBIUS-20011120Nebius B.V. (ORG-NB187-RIPE) · NLALLOCATED PADec 18, 2024noc-abuse@nebius.com
└ 66.201.4.0/221,024PA10-FIP-NEBIUSCLOUD-01-04-2025unknownSUB-ALLOCATED PAApr 1, 2025noc-abuse@nebius.com
via NL-NEBIUS-20011120

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
Mar 2025
Current origin since
Mar 2025 · 1.6 yr
Origin networks
1