LAYER3 INTEL
Get started
Sign in
Data as of Nov 15, 2026

83.246.160.0/24

1 residential-proxy exit · 30 days

Joint Stock Company TransTeleCom

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

Residential-proxy exits

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

Exits seen per day

449 observations

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GonzoProxy
  • HydraProxy
  • Infatica
  • MangoProxy
  • NodeMaven
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VitalExclusive
  • VitalProxy

Registrations in this block

The registry's network records over this block, widest first, each 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

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 83.246.160.0/21

83.246.160.0/21

Routing history

Pattern
Stable
First seen
Jun 2011
Current origin since
Jun 2011 · 15 yr
Origin networks
1