Data as of Nov 15, 2026

85.249.252.0/24

2 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement

this exact prefix

No RPKI

Announced by

AS3216

Type

Business

Risk

0 / 100 · Low

Residential-proxy exits

Proxy exits

0.78% of its addresses · 30 days

Always-on exits

50% of its exits

Providers

selling exits here

Oct 16, 2026 – Nov 14, 2026

Exits seen per day

2.9K observations

Proxy providers listing exits

2Captcha
Ake.net
BirdProxies
BottingTools
ByteProxies
Byteful
CliProxy
FlashProxy
GonzoProxy
IPOasis
Infatica
LightningProxies
NSocks
NodeMaven
Proxiware
Proxy-Seller
ProxyEmpire
Proxyma
Shifter
VibeProxies
VitalExclusive
VitalProxy

Announcements

Less specific

Covering announcements

Prefix	Origin	Type	Proxy exits	Holder	RPKI
85.249.224.0/19 since May 2005	AS20597	Business	9 1 always on	PJSC "Vimpelcom" via now PAO Vimpelcom - formely ZAO "ELTEL"

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.249.0.0/16	65,536	RU-SOVINTEL-20050124	PJSC "Vimpelcom" (ORG-ES15-RIPE) · RU	ALLOCATED PA	Jan 24, 2005	abuse-b2b@beeline.ru
└ 85.249.224.0/19	8,192	RU-BeeLine-B2B-clients-NET	now PAO Vimpelcom - formely ZAO "ELTEL" (ORG-EA40-RIPE) · RU	LIR-PARTITIONED PA	Jul 5, 2012	abuse-b2b@beeline.ru
└ 85.249.252.0/24	256	RU-Bee-Line-FTTB-B2B-clients-NET	111250 Russia SOVINTEL/EDN et ELTEL	ASSIGNED PA	Oct 26, 2021	abuse-b2b@beeline.ru via RU-BeeLine-B2B-clients-NET

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 Whois & abuse

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern: Stable
First seen: Dec 2021
Current origin since: Dec 2021 · 4.9 yr
Origin networks: 1