Data as of Nov 17, 2026

83.246.160.0/21

155 residential-proxy exits · 30 days

Joint Stock Company TransTeleCom

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
155
7.6% of its addresses · 30 days
Always-on exits
110
71% of its exits
Spread
2 of 8
/24s with at least one exit
Providers
84
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

289K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
83.246.166.0/24110152
83.246.160.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HydraProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LightningProxies
  • MangoProxy
  • MarsProxies
  • Maskify
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXORA
  • PROXYLANE
  • PROXYSCRAPE
  • PacketStream
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • VitalProxy
  • Webshare

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
83.246.166.0/23
since Mar 2017
AS31364Residential152
110 always on
Joint Stock Company TransTeleCom

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
83.246.128.0/1732,768RU-TRANSTELECOM-20040423Joint Stock Company TransTeleCom (ORG-CJSC19-RIPE) · RUALLOCATED PAApr 23, 2004abuse@ttk.ru
└ 83.246.160.0/2816AKIPKRO-BRN-05AKIPKRO network, cust. BRNASSIGNED PAMay 17, 2005abuse@ttk.ru
via RU-TRANSTELECOM-20040423
└ 83.246.160.32/2732INTR-BRN-05INTR-BRN-05 net, cust. BRNASSIGNED PAJul 15, 2005abuse@ttk.ru
via RU-TRANSTELECOM-20040423
└ 83.246.160.64 - 83.246.160.14380AGMU-BRN-06AGMU-BRN-06, cust. BRNASSIGNED PAJan 10, 2006abuse@ttk.ru
via RU-TRANSTELECOM-20040423
└ 83.246.161.0/24256ALTAIGRIF-BRN-06ALTAIGRIF-BRN-06, cust. BRNASSIGNED PAJul 27, 2006abuse@ttk.ru
via RU-TRANSTELECOM-20040423
└ 83.246.162.0/24256USSS-NET-BRN-06USSS-BRN-06, cust. BRNASSIGNED PANov 16, 2006abuse@ttk.ru
via RU-TRANSTELECOM-20040423

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