Data as of Nov 10, 2026

46.48.136.0/22

3 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
3
0.29% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
26
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

1.1K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
46.48.139.0/2402
46.48.136.0/2401

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.48.128.0/18
since May 2019
AS12389Residential2,915
24 always on
PJSC Rostelecom
46.48.128.0/17
since May 2019
AS12389Residential6,856
58 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.48.128.0/1732,768RU-RTK-20100625PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJun 25, 2010abuse@rt.ru
└ 46.48.128.0 - 46.48.160.2558,448SAKHAunknownASSIGNED PAJul 17, 2025abuse@rt.ru
via RU-RTK-20100625

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.48.128.0/20

Routing history

Pattern
Stable
First seen
May 2017
Current origin since
May 2017 · 9.4 yr
Origin networks
1