Data as of Nov 21, 2026

83.174.224.0/21

32 residential-proxy exits · 30 days

PJSC 'Bashinformsvyaz'

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

Residential-proxy exits

Proxy exits
32
1.6% of its addresses · 30 days
Always-on exits
1
3.1% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
86
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

8.6K observations

Proxy providers listing exits

  • 711Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • Ake.net
  • B2Proxy
  • BUYPERSONALPROXY
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GeekProxy
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • HPROXY
  • HideProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LAMAPROXY
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NextProxy
  • NodeProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYCOVE
  • PROXYLANE
  • PROXYSAVER
  • PROXYSCRAPE
  • PSBProxy
  • PrivateByte
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • Shifter
  • SpyderProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • 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.224.0/24256SLVT-NETJSC Bashinformsviaz, Communication Node in Salavat CityASSIGNED PANov 26, 2004abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.225.0/24256BASHTEL-NETBASHTEL pppoe clientsASSIGNED PAOct 21, 2019abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.226.0/24256OKT-DIALUP-NETDialup pool for clients in Oktyabrsky CityASSIGNED PAMay 22, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.227.0/24256TMZ-DIALUP-NETDialup pool for clients in Tuimazy CityASSIGNED PAMay 22, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.228.0/24256BASHTEL-NETBASHTEL pppoe clientsASSIGNED PAOct 21, 2019abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.229.0/24256STR-DIALUP-NETDialup pool for clients in Sterlitamak CityASSIGNED PAMay 22, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.230.0/24256NFK-DIALUP-NETDialup pool for clients in Neftekamsk CityASSIGNED PAMay 22, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.231.0/24256BASHTEL-NETBASHTEL pppoe clientsASSIGNED PAOct 21, 2019abuse@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