LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

46.48.133.0/24

4 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
32
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

3.9K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • GonzoProxy
  • HydraProxy
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • Smartproxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.48.128.0/18
since May 2019
AS12389Residential3,004
5 always on
PJSC Rostelecom
46.48.128.0/17
since May 2019
AS12389Residential7,050
5 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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.5 yr
Origin networks
1