Data as of Nov 14, 2026

37.61.176.0/22

13 residential-proxy exits · 30 days

Limited Liability Company 'TTK-Svyaz' · space held by Joint Stock Company TransTeleCom

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

Residential-proxy exits

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

Exits seen per day

1.7K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
37.61.178.0/24010
37.61.176.0/2402
37.61.177.0/2401

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

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
37.61.176.0/212,048RU-TRANSTELECOM-20120120Joint Stock Company TransTeleCom (ORG-CJSC19-RIPE) · RUALLOCATED PAJan 20, 2012abuse@ttk.ru
└ 37.61.176.0/298SAMARA-TTK-NET-12S1042NET PrivMTUVTRosaviac /29ASSIGNED PAMay 21, 2012abuse@ttk.ru
via RU-TRANSTELECOM-20120120
└ 37.61.176.8/298SAMARA-TTK-NET-12S1097NET PrivMTUVTRosaviac /29ASSIGNED PAMay 21, 2012abuse@ttk.ru
via RU-TRANSTELECOM-20120120
└ 37.61.176.16/298SAMARA-TTK-NET-12S1169NET Zhigulevskoe pivo /29ASSIGNED PAMay 28, 2012abuse@ttk.ru
via RU-TRANSTELECOM-20120120
└ 37.61.176.24/298SAMARA-TTK-NET-12S1026NET Vip-auto /29ASSIGNED PAJun 21, 2012abuse@ttk.ru
via RU-TRANSTELECOM-20120120
└ 37.61.176.32/298SAMARA-TTK-NET-12S1492net TeremSamara /29ASSIGNED PAJul 5, 2012abuse@ttk.ru
via RU-TRANSTELECOM-20120120
└ 37.61.176.40/298SAMARA-TTK-NET-12S1496NET Soyuz /29ASSIGNED PAJul 5, 2012abuse@ttk.ru
via RU-TRANSTELECOM-20120120
└ 37.61.176.48/298SAMARA-TTK-NET-12S1209net GorodSamara /29ASSIGNED PAJul 10, 2012abuse@ttk.ru
via RU-TRANSTELECOM-20120120
└ 37.61.176.56 - 37.61.176.160105SAMARA-TTK-NETPtoP networks, Samara-TranstelecomASSIGNED PAOct 12, 2012abuse@ttk.ru
via RU-TRANSTELECOM-20120120
└ 37.61.176.161 - 37.61.176.19131SAMARA-TTK-NET-12S1296NET TelediskontVolga /27ASSIGNED PAJun 14, 2012abuse@ttk.ru
via RU-TRANSTELECOM-20120120
└ 37.61.176.192/2732SAMARA-TTK-NET-08C0164net MegdunarodnyInstitutRinka /27ASSIGNED PAJun 5, 2012abuse@ttk.ru
via RU-TRANSTELECOM-20120120
└ 37.61.176.224/2732SAMARA-TTK-NET-12S1124NET RegionKommunik /27ASSIGNED PAMay 21, 2012abuse@ttk.ru
via RU-TRANSTELECOM-20120120
└ 37.61.177.0 - 37.61.179.255768SAMARA-TTK-NETPtoP networks, Samara-TranstelecomASSIGNED PAOct 11, 2012abuse@ttk.ru
via RU-TRANSTELECOM-20120120

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
Mar 2023
Current origin since
Mar 2023 · 3.6 yr
Origin networks
1