Data as of Nov 15, 2026

109.161.48.0/24

18 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
18
7.0% of its addresses · 30 days
Always-on exits
2
11% of its exits
Providers
46
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

8.6K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
109.161.0.0/17
since Dec 2009
AS13118Residential8,441
11 always on
PJSC Rostelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
109.161.0.0/1732,768RU-RTK-20090904PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PASep 4, 2009abuse@rt.ru
└ 109.161.48.0/221,024MACROREGIONAL_CENTEROJSC Rostelecom, Yaroslavl branchASSIGNED PAApr 10, 2026abuse@rt.ru
via RU-RTK-20090904

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

109.161.32.0/19

Routing history

Pattern
Stable
First seen
May 2012
Current origin since
May 2012 · 15 yr
Origin networks
1