Data as of Nov 15, 2026

37.140.26.0/24

28 residential-proxy exits · 30 days

Intersvyaz-2 JSC

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

Residential-proxy exits

Proxy exits
28
11% of its addresses · 30 days
Providers
57
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

4.2K observations

Proxy providers listing exits

  • 9Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLEETPROXY
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HELODATA
  • IPFly
  • IPMUSK
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateProxy
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
37.140.0.0/1732,768RU-INTERSVYAZ-20120229Intersvyaz-2 JSC (ORG-IJ7-RIPE) · RUALLOCATED PAFeb 29, 2012abuse@is74.ru
└ 37.140.0.0/1816,384INTERSV-NET-38Intersvyaz-2 JSCASSIGNED PAMar 15, 2012abuse@is74.ru
via RU-INTERSVYAZ-20120229

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 37.140.0.0/17

37.140.0.0/17

Routing history

Pattern
Stable
First seen
Mar 2012
Current origin since
Mar 2012 · 15 yr
Origin networks
1