Data as of Nov 14, 2026

46.61.174.0/24

3 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
22
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

1.2K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • Byteful
  • Decodo
  • EnigmaProxy
  • FlashProxy
  • FloppyData
  • IPFly
  • IPPeak
  • NovaProxy
  • Novada
  • Oxylabs
  • ProxyWing
  • PuraRoute
  • RapidProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.61.0.0/16
since Sep 2018
AS12389Residential13,740
116 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.174.0/2664PovtechTicket 569-962456ASSIGNED PAMay 24, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.174.64/2664Vesna-NetTicket 248-596315ASSIGNED PAMay 24, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.174.128/2664BYSLTicket 597-89626ASSIGNED PAMay 24, 2011abuse@rt.ru
via RU-RTK-20101022
└ 46.61.174.192/2664DeBitTicket 197-489631ASSIGNED PAMay 24, 2011abuse@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