Data as of Nov 15, 2026

46.61.128.0/24

8 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
2
25% of its exits
Providers
44
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

2.4K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Kookey
  • LightningProxies
  • MangoProxy
  • NSocks
  • NovaProxy
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RolaProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • ThunderProxy
  • VitalExclusive
  • VitalProxy
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.61.0.0/16
since Sep 2018
AS12389Residential13,720
119 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.128.0/25128SchekinoazotTicket 10-31594-3ASSIGNED PANov 30, 2010abuse@rt.ru
via RU-RTK-20101022
└ 46.61.128.128/25128PIRSTicket 10-34450-4ASSIGNED PANov 30, 2010abuse@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.128.0/17

Routing history

Pattern
Stable
First seen
Dec 2010
Current origin since
Dec 2010 · 16 yr
Origin networks
1