Data as of Nov 20, 2026

83.174.208.0/20

62 residential-proxy exits · 30 days

PJSC 'Bashinformsvyaz'

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

Residential-proxy exits

Proxy exits
62
1.5% of its addresses · 30 days
Always-on exits
7
11% of its exits
Spread
14 of 16
/24s with at least one exit
Providers
74
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

26K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • B2Proxy
  • BUYPERSONALPROXY
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HASDATA
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSAVER
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RolaProxy
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy

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.208.0/212,048RUMS-DIALUPBashinformsvyaz Company, RUMS, DialUp PoolASSIGNED PANov 23, 2004abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.216.0/23512BASHTEL-NETBASHTEL pppoe clientsASSIGNED PAOct 21, 2019abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.218.128/25128KUM-DIALUP-NETDialup pool for clients in Kumertau CityASSIGNED PAMay 22, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.219.0 - 83.174.222.2551,024RUMS-DIALUPBashinformsvyaz Company, RUMS, DialUp PoolASSIGNED PAMay 25, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.223.0/24256BLR-DIALUP-NETDialup pool for clients in Beloretsk City and Uchaly CityASSIGNED PAMay 22, 2007abuse@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