Data as of Nov 10, 2026

46.48.141.0/24

2 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

0.78% of its addresses · 30 days

Providers

selling exits here

Oct 11, 2026 – Nov 9, 2026

Exits seen per day

48 observations

Proxy providers listing exits

Ake.net
BottingTools
Byteful
CatProxies
CoreProxy
DataImpulse
EnigmaProxy
GeekProxy
IPCola
IPRoyal
MarsProxies
NodeProxy
NovaProxy
PSBProxy
PrivateByte
Proxy4U
ProxyEmpire
ProxyRack
ProxyWing
Shifter
SpyderProxy
TrustProxy

Announcements

Less specific

Covering announcements

Prefix	Origin	Type	Proxy exits	Holder	RPKI
46.48.128.0/18 since May 2019	AS12389	Residential	2,915 24 always on	PJSC Rostelecom
46.48.128.0/17 since May 2019	AS12389	Residential	6,856 58 always on	PJSC Rostelecom

Registrations in this block

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

Range	Addresses	Netname	Holder	Type	Created	Abuse contact
46.48.128.0/17	32,768	RU-RTK-20100625	PJSC Rostelecom (ORG-JR8-RIPE) · RU	ALLOCATED PA	Jun 25, 2010	abuse@rt.ru
└ 46.48.128.0 - 46.48.160.255	8,448	SAKHA	unknown	ASSIGNED PA	Jul 17, 2025	abuse@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

Announcement Routing history RPKI & IRR Whois & 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.4 yr
Origin networks: 1

RPKI

Route origin authorizations

ROA prefix	ASN	Max len	Anchor	Verdict
46.48.128.0/20	AS21487	/20	RIPE	RPKI valid
46.48.128.0/18	AS12389	/18	RIPE	Another network
46.48.128.0/17	AS12389	/17	RIPE	Another network

IRR

Route objects on 46.48.128.0/20

Origin	Registry	Description	Maintainer	Modified
AS21487	RIPE	Sakhatelecom, Yakutsk	SAKHA-MNT	Jun 7, 2017