Data as of Nov 16, 2026

93.92.180.0/22

3 residential-proxy exits · 30 days

PJSC 'Vimpelcom'

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

Residential-proxy exits

Proxy exits
3
0.29% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
14
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

21 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
93.92.181.0/2402
93.92.183.0/2401

Proxy providers listing exits

  • BestProxy
  • GEEKPROXY_FLEX
  • GSocks
  • IPFly
  • Infatica
  • NSocks
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Smartproxy
  • VitalExclusive

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
93.92.176.0/212,048RU-SOVINTEL-20080204PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAOct 18, 2016abuse-b2b@beeline.ru
└ 93.92.180.0/221,024WBTNETADSL NetworkASSIGNED PAFeb 20, 2009abuse-b2b@beeline.ru
via RU-SOVINTEL-20080204

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
Jul 2014
Current origin since
Jul 2014 · 12 yr
Origin networks
1