Data as of Nov 21, 2026

83.174.224.0/20

62 residential-proxy exits · 30 days

PJSC 'Bashinformsvyaz'

Announcement
No RPKI
Announced by
Type
Residential
88% of it

Residential-proxy exits

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

Exits seen per day

15K observations
  • Residential
  • Business

Proxy providers listing exits

  • 711Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • B2Proxy
  • BUYPERSONALPROXY
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GeekProxy
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HPROXY
  • HideProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LAMAPROXY
  • LemonPrime
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIWARE_ECO
  • PROXYCOVE
  • PROXYLANE
  • PROXYSAVER
  • PROXYSCRAPE
  • PSBProxy
  • PrivateByte
  • ProxiesVision
  • 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
└ 83.174.232.0/2816STR-P2P-NETNetwork for P2P client connections in SterlitamakASSIGNED PAFeb 11, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.232.16/298MECHATRONMECHATRON Engineering Company Inc.ASSIGNED PASep 13, 2006abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.232.24/298TNH-NETJSC Transheftehim, SterlitamakASSIGNED PADec 7, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.232.32 - 83.174.232.12796STR-P2P-NETNetwork for P2P client connections in SterlitamakASSIGNED PAFeb 11, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.232.128/25128STR-HOST-CLIENTNetwork for P2P client connections in SterlitamakASSIGNED PAMay 21, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.233.0/24256UFA-P2P-NETNetwork for P2P client connections in UfaASSIGNED PAJan 24, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.234.0/2664KUM-P2P-NETNetwork for P2P client connections in KumertauASSIGNED PAMar 3, 2011abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.234.64/2664UCH-P2P-NETNetwork for P2P client connections in UchalyASSIGNED PAMay 30, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.234.128/25128UFA-P2P-NETNetwork for P2P client connections in UfaASSIGNED PAJan 25, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.235.0/24256BASHTEL-NETBASHTEL pppoe clientsASSIGNED PAOct 21, 2019abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.236.0/221,024DSL-POOLBashinformsvyaz Company, RUMS, DSL POOL for regional clientsASSIGNED PAMay 8, 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.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

4,096 addresses
TypeAddressesShareRanges
Residential3,58488%3
Business51213%8

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