Data as of Nov 11, 2026

85.174.63.0/24

1 residential-proxy exit · 30 days

PJSC Rostelecom

Announcement

this exact prefix

RPKI valid

Announced by

AS33934

Type

Residential

Risk

0 / 100 · Low

Residential-proxy exits

Proxy exits

0.39% of its addresses · 30 days

Providers

selling exits here

Oct 12, 2026 – Nov 10, 2026

Exits seen per day

36 observations

Proxy providers listing exits

ByteProxies
GSocks
Infatica
MangoProxy
NodeProxy
NovaProxy
Shifter
VitalExclusive

Announcements

Less specific

Covering announcements

Prefix	Origin	Type	Proxy exits	Holder	RPKI
85.174.0.0/17 since Mar 2008	AS33934	Residential	8,708 1 always on	PJSC Rostelecom
85.172.0.0/14 since Sep 2018	AS12389	Residential	39,121 2,957 always on	PJSC Rostelecom

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

Range	Addresses	Netname	Holder	Type	Created	Abuse contact
85.172.0.0/14	262,144	RU-RTK-20041222	PJSC Rostelecom (ORG-JR8-RIPE) · RU	ALLOCATED PA	Dec 22, 2004	abuse@rt.ru
└ 85.174.0.0/17	32,768	Macroregional_South	OJSC Rostelecom Macroregional Branch South	ASSIGNED PA	Feb 29, 2008	abuse@rt.ru via RU-RTK-20041222

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

Summary

Routing history

Pattern: Stable
First seen: Aug 2019
Current origin since: Aug 2019 · 7.2 yr
Origin networks: 1

RPKI

Route origin authorizations

ROA prefix	ASN	Max len	Anchor	Verdict
85.174.63.0/24	AS33934	/24	RIPE	RPKI valid
85.174.0.0/17	AS33934	/17	RIPE	Too specific
85.172.0.0/14	AS12389	/24	RIPE	Another network

IRR

Route objects on the exact prefix

Origin	Registry	Description	Maintainer	Modified
AS33934	RIPE		ROSTELECOM-MNT	Dec 11, 2024