Data as of Nov 13, 2026

81.85.0.0/21

3 residential-proxy exits · 30 days

Nebius B.V.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium
Recent change
New origin May 2026
its first announcement on record
registry: sub-allocated pa to a party the registry does not name by Nebius B.V., May 29, 2026

Residential-proxy exits

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

Exits seen per day

1.3K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
81.85.1.0/2402
81.85.2.0/2401

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • Geonode
  • IPFly
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NovaProxy
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RapidProxy
  • Shifter
  • 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
81.85.0.0/198,192NL-NEBIUS-20020530Nebius B.V. (ORG-NB187-RIPE) · NLALLOCATED PADec 5, 2025noc-abuse@nebius.com
└ 81.85.0.0/212,048LNE-FIP-NEBIUSCLOUD-29-05-2026unknownSUB-ALLOCATED PAMay 29, 2026noc-abuse@nebius.com
via NL-NEBIUS-20020530

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 2026
Current origin since
May 2026 · 5 mo
Origin networks
1