Data as of Nov 11, 2026

46.61.40.0/24

95 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
95
37% of its addresses · 30 days
Providers
68
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

2.7K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • ResiProxies
  • Shifter
  • SwiftProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.61.0.0/18
since Jan 2018
AS12389Residential6,534PJSC Rostelecom
46.61.0.0/16
since Sep 2018
AS12389Residential13,660
113 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
46.61.0.0/1665,536RU-RTK-20101022PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 30, 2011abuse@rt.ru
└ 46.61.0.0/1816,384Macroregional_SouthOJSC Rostelecom Macroregional Branch SouthASSIGNED PAMay 22, 2012abuse@rt.ru
via RU-RTK-20101022

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

46.61.32.0/19

Routing history

Pattern
Stable
First seen
Mar 2024
Current origin since
Mar 2024 · 2.6 yr
Origin networks
1