Data as of Nov 21, 2026

85.249.235.0/24

1 residential-proxy exit · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
20
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

38 observations

Proxy providers listing exits

  • 9Proxy
  • BirdProxies
  • BuyingProxy
  • ByteProxies
  • Byteful
  • Decodo
  • EnigmaProxy
  • Evomi
  • Geonode
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NovaProxy
  • Oxylabs
  • Proxies.fo
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter

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.235.32/2816OAO_Kompleks_ServisOAO Kompleks ServisASSIGNED PAMar 29, 2012abuse-b2b@beeline.ru
via RU-BeeLine-B2B-clients-NET
└ 85.249.235.48/2816FBOU_VPO_SPGUVKunknownASSIGNED PAMar 29, 2012abuse-b2b@beeline.ru
via RU-BeeLine-B2B-clients-NET
└ 85.249.235.64/2732OOO_Avtoholding_RRTOOO Avtoholding RRTASSIGNED PAMar 29, 2012abuse-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