Data as of Nov 17, 2026

85.249.253.0/24

2 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
this exact prefix
No RPKI
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
21
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

335 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
85.249.224.0/19
since May 2005
AS20597Business8
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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
85.249.0.0/1665,536RU-SOVINTEL-20050124PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAJan 24, 2005abuse-b2b@beeline.ru
└ 85.249.224.0/198,192RU-BeeLine-B2B-clients-NETnow PAO Vimpelcom - formely ZAO "ELTEL" (ORG-EA40-RIPE) · RULIR-PARTITIONED PAJul 5, 2012abuse-b2b@beeline.ru
└ 85.249.253.0/24256RU-Bee-Line-B2B-FTTB-clients-NET111250 Russia SOVINTEL/EDN et ELTELASSIGNED PAOct 26, 2021abuse-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

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Nov 2021
Current origin since
Nov 2021 · 5.0 yr
Origin networks
1