Data as of Nov 19, 2026

213.171.41.0/24

1 residential-proxy exit · 30 days

JSC Zarubezhneft · space held by JSC Comcor

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

Residential-proxy exits

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

Exits seen per day

631 observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • Decodo
  • EnigmaProxy
  • Geonode
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.171.32.0/19
since May 2005
AS8732Residential76
9 always on
JSC Comcor

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
213.171.32.0/198,192RU-COMCOR-20001219JSC Comcor (ORG-CA35-RIPE) · RUALLOCATED PADec 14, 2001netadm@comcor.ru
└ 213.171.41.0/24256COMCOR-B2B-ClientsNetwork for COMCOR-B2B-ClientsASSIGNED PANov 9, 2018netadm@comcor.ru
via RU-COMCOR-20001219

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jan 2022
Current origin since
Jan 2024 · 2.8 yr
Origin networks
1