Data as of Nov 13, 2026

85.115.248.0/24

50 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

Announcement
this exact prefix
No RPKI
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
50
20% of its addresses · 30 days
Providers
54
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

690 observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Datarama
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RealProxy
  • ResiProxies
  • SPYDERPROXY_BASIC
  • Shifter
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

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.115.224.0/198,192RU-BEE3G-20050304PJSC "Vimpelcom" (ORG-JA8-RIPE) · RUALLOCATED PAMar 4, 2005Internet.abuse@beeline.ru
└ 85.115.248.0/24256BEE_internet-StavropolFirewall pool in StavropolASSIGNED PAOct 23, 2009Internet.abuse@beeline.ru
via RU-BEE3G-20050304

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
Nov 2009
Current origin since
Nov 2009 · 17 yr
Origin networks
1