Data as of Nov 13, 2026

217.148.196.0/22

1 residential-proxy exit · 30 days

PJSC 'Vimpelcom'

Announcement
No RPKI
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
1
0.10% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
10
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

689 observations

Proxy providers listing exits

  • BottingTools
  • Byteful
  • CatProxies
  • EZProxies
  • GSocks
  • Geonode
  • Infatica
  • NodeProxy
  • PacketStream
  • ProxyGeo

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
217.148.196.0/24
since May 2005
AS20533ResidentialPJSC "Vimpelcom"
217.148.197.0/24
since May 2005
AS20533ResidentialPJSC "Vimpelcom"
217.148.198.0/24
since May 2005
AS20533ResidentialPJSC "Vimpelcom"
217.148.199.0/24
since May 2005
AS20533Residential1PJSC "Vimpelcom"

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.148.192.0/204,096RU-SOVINTEL-20010307PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PAJul 21, 2021abuse-b2b@beeline.ru
└ 217.148.196.0/221,024SAKHTELSakhalin Telecom networkASSIGNED PADec 22, 2017abuse-b2b@beeline.ru
via RU-SOVINTEL-20010307

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 217.148.192.0/20

217.148.192.0/20

Routing history

Pattern
Stable
First seen
Nov 2008
Current origin since
Nov 2008 · 18 yr
Origin networks
1