Data as of Nov 12, 2026

37.205.48.0/21

50 residential-proxy exits · 30 days

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

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
50
2.4% of its addresses · 30 days
Always-on exits
7
14% of its exits
Spread
7 of 8
/24s with at least one exit
Providers
70
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

18K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NSocks
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
37.205.48.0/24
since Nov 2016
AS21127Residential1Limited Liability Company "TTK-Svyaz"

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.205.48.0/212,048RU-TTKS-20120328Limited Liability Company "TTK-Svyaz" (ORG-LLC51-RIPE) · RUALLOCATED PAMar 28, 2012nmc@ttk.ru
└ 37.205.48.0/24256ZSTTK-RTL-NETJSC "Zap-Sib TransTeleCom"ASSIGNED PAJan 18, 2019nmc@ttk.ru
via RU-TTKS-20120328
└ 37.205.49.0/24256ZSTTK-RTL-NETNovokuznetskASSIGNED PAJan 18, 2019nmc@ttk.ru
via RU-TTKS-20120328
└ 37.205.50.0/23512ZSTTK-RTL-NETJSC "Zap-Sib TransTeleCom"ASSIGNED PAJan 18, 2019nmc@ttk.ru
via RU-TTKS-20120328
└ 37.205.52.0/24256ZSTTK-RTL-NETJSC "Zap-Sib TransTeleCom"ASSIGNED PAJan 18, 2019nmc@ttk.ru
via RU-TTKS-20120328
└ 37.205.53.0/24256ZSTTK-RTL-NETJSC "Zap-Sib TransTeleCom"ASSIGNED PAJan 18, 2019nmc@ttk.ru
via RU-TTKS-20120328
└ 37.205.54.0/24256ZSTTK-RTL-NETJSC "Zap-Sib TransTeleCom"ASSIGNED PAJan 18, 2019nmc@ttk.ru
via RU-TTKS-20120328
└ 37.205.55.0/24256ZSTTK-RTL-NETNovokuznetskASSIGNED PAJan 18, 2019nmc@ttk.ru
via RU-TTKS-20120328

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
Apr 2012
Current origin since
Apr 2012 · 15 yr
Origin networks
1