Data as of Nov 13, 2026

85.249.252.0/23

5 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
No RPKI
Announced by
Type
Business

Residential-proxy exits

Proxy exits
5
0.98% of its addresses · 30 days
Always-on exits
1
20% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
28
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

3.3K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
85.249.252.0/2412
85.249.253.0/2403

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • GonzoProxy
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
85.249.252.0/24
since Dec 2021
AS3216Business2
1 always on
PJSC "Vimpelcom"
via now PAO Vimpelcom - formely ZAO "ELTEL"
85.249.253.0/24
since Nov 2021
AS3216Business3PJSC "Vimpelcom"
via now PAO Vimpelcom - formely ZAO "ELTEL"

Registrations in this block

The registry's network records over this block, widest first, each 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.252.0/24256RU-Bee-Line-FTTB-B2B-clients-NET111250 Russia SOVINTEL/EDN et ELTELASSIGNED PAOct 26, 2021abuse-b2b@beeline.ru
via RU-BeeLine-B2B-clients-NET
└ 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

Who has announced 85.249.224.0/19

85.249.224.0/19

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1