Data as of Nov 11, 2026

94.233.76.0/23

4 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
4
0.78% of its addresses · 30 days
Always-on exits
1
25% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
29
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

739 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
94.233.76.0/2413
94.233.77.0/2401

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
94.233.0.0/17
since Apr 2009
AS33934Residential5,156
10 always on
PJSC Rostelecom

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
94.233.0.0/1665,536RU-RTK-20080918PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PASep 18, 2008abuse@rt.ru
└ 94.233.0.0/1732,768Macroregional_SouthOJSC Rostelecom Macroregional Branch SouthASSIGNED PAApr 8, 2009abuse@rt.ru
via RU-RTK-20080918

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Aug 2019
Current origin since
Sep 2024 · 2.1 yr
Origin networks
1