Data as of Nov 14, 2026

83.174.205.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
Providers
33
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

277 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlexyProxies
  • GSocks
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPROCKET_PREMIUM
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • 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.205.0 - 83.174.205.3940OKT-P2P-NETNetwork for P2P client connections in OktyabrskyASSIGNED PAMay 10, 2012abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.205.40/298BASHMOROZPRODUKTLTD BASHMOROZPRODUKT NetworkASSIGNED PAMay 10, 2012abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.205.48/298IPK-NetNetwork of IPK in OktyabrskyASSIGNED PAMay 10, 2012abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.205.56 - 83.174.205.10752OKT-P2P-NETNetwork for P2P client connections in OktyabrskyASSIGNED PASep 25, 2012abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.205.108 - 83.174.205.1158ChP-NAZ-NETChP-NAZ-NETASSIGNED PASep 25, 2012abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.205.116/304OKT-P2P-NETNetwork for P2P client connections in OktyabrskyASSIGNED PASep 25, 2012abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.205.120/298BASHOIL-NETOktyabrsky Branch Of Ufa State Petroleum Technological UnivesityASSIGNED PAFeb 3, 2012abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.205.128 - 83.174.205.19972OKT-P2P-NETNetwork for P2P client connections in OktyabrskyASSIGNED PANov 28, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.205.200/298EVROPLAST-NETOOO EvroplastASSIGNED PANov 28, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.205.208/298ONK-NETNetwork of FGOU SPO ONKASSIGNED PASep 17, 2012abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.205.216/298OKT-P2P-NETNetwork for P2P client connections in OktyabrskyASSIGNED PASep 17, 2012abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.205.224/298PACKER-NETLLP SPC PackerASSIGNED PAMay 26, 2011abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.205.232 - 83.174.205.24716OKT-P2P-NETNetwork for P2P client connections in OktyabrskyASSIGNED PAMay 26, 2011abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.205.248/298RFC-NETNetwork of the Federal State Unitary Enterprise "RFC PFO" in OktyabrskyASSIGNED PAJul 6, 2010abuse@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