Data as of Nov 10, 2026

5.136.3.0/24

14 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement

5.136.0.0/21

RPKI valid

Announced by

AS12389

Type

Residential

Risk

0 / 100 · Low

Residential-proxy exits

Proxy exits

5.5% of its addresses · 30 days

Providers

selling exits here

Oct 11, 2026 – Nov 9, 2026

Exits seen per day

42 observations

Proxy providers listing exits

Byteful
EnigmaProxy
GSocks
IPFly
Infatica
MangoProxy
NodeProxy
NovaProxy
PROXYSCRAPE
Proxy-Seller
ProxyEmpire
Proxyma
RainProxy
Shifter
VantageProxies
VitalExclusive

Announcements

Less specific

Covering announcements

Prefix	Origin	Type	Proxy exits	Holder	RPKI
5.136.0.0/15 since Aug 2016	AS12389	Residential	22,951 216 always on	PJSC Rostelecom
5.136.0.0/13 since Sep 2018	AS12389	Residential	114,604 1,260 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
5.136.0.0/13	524,288	RU-RTK-20120703	PJSC Rostelecom (ORG-JR8-RIPE) · RU	ALLOCATED PA	Jul 3, 2012	abuse@rt.ru
└ 5.136.0.0/17	32,768	WEBSTREAM	OJSC "Sibirtelecom"	ASSIGNED PA	Jul 16, 2012	abuse@rt.ru via RU-RTK-20120703

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

5.136.0.0/21

Routing history

Pattern: Stable
First seen: Nov 2013
Current origin since: Nov 2013 · 13 yr
Origin networks: 1

RPKI

Route origin authorizations

ROA prefix	ASN	Max len	Anchor	Verdict
5.136.0.0/21	AS12389	/21	RIPE	RPKI valid
5.136.0.0/15	AS12389	/15	RIPE	Too specific
5.136.0.0/13	AS12389	/24	RIPE	RPKI valid

IRR

Route objects on 5.136.0.0/21

Origin	Registry	Description	Maintainer	Modified
AS12389	RIPE	Rostelecom networks	ROSTELECOM-MNT	Nov 18, 2013