Data as of Nov 20, 2026

83.174.204.0/24

4 residential-proxy exits · 30 days

PJSC 'Bashinformsvyaz'

Announcement
No RPKI
Announced by
Type
Business

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
32
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

3.9K observations

Proxy providers listing exits

  • 2Captcha
  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlexyProxies
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
83.174.192.0/1816,384RU-BASHTEL-20040521PJSC "Bashinformsvyaz" (ORG-BC2-RIPE) · RUALLOCATED PAMay 21, 2004abuse@bashtel.ru
└ 83.174.204.0 - 83.174.204.2324TMZ-P2P-NETNetwork for P2P client connections in TuimazyASSIGNED PAFeb 7, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.204.24/298RFC-NETNetwork of the Federal State Unitary Enterprise "RFC PFO" in TuimazyASSIGNED PAMay 24, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.204.32/298TMZ-P2P-NETNetwork for P2P client connections in TuimazyASSIGNED PAApr 1, 2011abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.204.40/298MBRR-NETNetwork of the MBRR in TuimazyASSIGNED PAJan 13, 2011abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.204.48/2816TMZ-P2P-NETNetwork for P2P client connections in TuimazyASSIGNED PAApr 1, 2011abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.204.64/298ISH-P2P-NETNetwork for P2P client connections in IshimayASSIGNED PAFeb 7, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.204.72/298RFC-NETNetwork of the Federal State Unitary Enterprise "RFC PFO" in IshimbayASSIGNED PASep 13, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.204.80 - 83.174.204.12748ISH-P2P-NETNetwork for P2P client connections in IshimayASSIGNED PAFeb 7, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.204.128/2816NFK-P2P-NETNetwork for P2P client connections in NeftekamskASSIGNED PAFeb 7, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.204.144/298RFC-NETNetwork of the Federal State Unitary Enterprise "RFC PFO" in NeftekamskASSIGNED PASep 13, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.204.152 - 83.174.204.18332NFK-P2P-NETNetwork for P2P client connections in NeftekamskASSIGNED PAMar 20, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.204.184/298SMAIL-NFK-NETNetwork of OOO Smail, NeftekamskASSIGNED PAMar 20, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.204.192/2664BLR-P2P-NETNetwork for P2P client connections in BeloretskASSIGNED PAJan 25, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521

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 83.174.192.0/18

83.174.192.0/18

Routing history

Pattern
Stable
First seen
Jan 2008
Current origin since
Jan 2008 · 19 yr
Origin networks
1