LAYER3 INTEL
Get started
Sign in
Data as of Nov 15, 2026

83.174.192.0/18

1 anonymizer address · <0.01% · VPN889 residential-proxy exits · 30 days

PJSC 'Bashinformsvyaz'

Announcement
this exact prefix
No RPKI
Announced by
AS28812
Type
Residential
87% of it

Residential-proxy exits

Proxy exits
889
5.4% of its addresses · 30 days
Always-on exits
10
1.1% of its exits
Spread
54 of 64
/24s with at least one exit
Providers
122
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

84K observations
  • VPN · anonymizer
  • Residential
  • Business

/24s with the most always-on exits

/24Always-on exitsProxy exits
83.174.203.0/2425
83.174.215.0/2424
83.174.214.0/2417
83.174.212.0/2417
83.174.209.0/2416
83.174.223.0/2415
83.174.204.0/2414
83.174.231.0/2412
83.174.244.0/24058
83.174.246.0/24056
83.174.241.0/24055
83.174.249.0/24051
83.174.255.0/24051
83.174.252.0/24050
83.174.242.0/24049
83.174.251.0/24049
83.174.245.0/24048
83.174.240.0/24047
83.174.248.0/24046
83.174.253.0/24041
83.174.250.0/24040
83.174.247.0/24039
83.174.254.0/24035
83.174.243.0/24035

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HELODATA
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LOKIPROXY
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PSBProxy
  • PYPROXY
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM
IPv4 market

Path

1 · Holder
PJSC "Bashinformsvyaz"
record created May 21, 2004
2 · Leased from
not leased
3 · Announced by
AS28812 PJSC 'Bashinformsvyaz'
since Jan 2008 · 18.9 yr ago
4 · Use
VPN servicesnamed VPN Gate
Residential

Operators, sellers and brokers

VPN services

NameParentIn 83.174.192.0/18/24s
VPN GateUniversity of Tsukuba
1<0.01%
1

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

83.174.192.0/18

From the registry to its use

  1. May 21, 2004
    Registry record
    PJSC "Bashinformsvyaz"
    ALLOCATED PA
    83.174.192.0/18
  2. Jun 18, 2004
    Route object
    AS28812 PJSC 'Bashinformsvyaz'
    RIPE route object for AS28812 PJSC 'Bashinformsvyaz', maintainer RUMS-MNT
    83.174.192.0/20
  3. Aug 3, 2004
    Route object
    AS28812 PJSC 'Bashinformsvyaz'
    RIPE route object for AS28812 PJSC 'Bashinformsvyaz', maintainer RUMS-MNT
    83.174.208.0/20
  4. Aug 26, 2004
    Route object
    AS28812 PJSC 'Bashinformsvyaz'
    RIPE route object for AS28812 PJSC 'Bashinformsvyaz', maintainer RUMS-MNT
    83.174.208.0/21
  5. Aug 26, 2004
    Route object
    AS28812 PJSC 'Bashinformsvyaz'
    RIPE route object for AS28812 PJSC 'Bashinformsvyaz', maintainer RUMS-MNT
    83.174.224.0/20
  6. Aug 26, 2004
    Route object
    AS28812 PJSC 'Bashinformsvyaz'
    RIPE route object for AS28812 PJSC 'Bashinformsvyaz', maintainer RUMS-MNT
    83.174.224.0/21
  7. Nov 6, 2007
    Route object
    AS28812 PJSC 'Bashinformsvyaz'
    RIPE route object for AS28812 PJSC 'Bashinformsvyaz', maintainer RUMS-MNT
    83.174.240.0/21
  8. Nov 6, 2007
    Route object
    AS28812 PJSC 'Bashinformsvyaz'
    RIPE route object for AS28812 PJSC 'Bashinformsvyaz', maintainer RUMS-MNT
    83.174.248.0/21
  9. Dec 26, 2007
    Route object
    AS28812 PJSC 'Bashinformsvyaz'
    RIPE route object for AS28812 PJSC 'Bashinformsvyaz', maintainer RUMS-MNT
    83.174.232.0/22
  10. Dec 26, 2007
    Route object
    AS28812 PJSC 'Bashinformsvyaz'
    RIPE route object for AS28812 PJSC 'Bashinformsvyaz', maintainer RUMS-MNT
    83.174.236.0/22
  11. Jan 1, 2008– today
    Announced
    AS28812 PJSC 'Bashinformsvyaz'
    Internet provider
  12. Apr 11, 2008
    Route object
    AS28812 PJSC 'Bashinformsvyaz'
    RIPE route object for AS28812 PJSC 'Bashinformsvyaz', maintainer RUMS-MNT
  13. Jun 1, 2021
    Route object
    AS12389 PJSC Rostelecom
    RIPE route object for AS12389 PJSC Rostelecom, maintainer BASHNET-MNT RUMS-MNT
    83.174.240.0/20
  14. today
    Used
    VPN Gate
    VPN

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, 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.192.0 - 83.174.195.2391,008ru-bashtelJSC Bashinformsvyaz - RUMSASSIGNED PAMar 25, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.195.240/2816AIRUFA-NETAirport Ufa NetworksASSIGNED PAMar 25, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.196.8 - 83.174.196.6356ru-bashtelBashinformsvyaz companyASSIGNED PAFeb 13, 2012abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.196.64/2816SBBASH-NETSaving Bank of BashkortostanASSIGNED PAMay 27, 2015abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.196.80/298RU-BASHTELBashinformsvyaz companyASSIGNED PAApr 6, 2012abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.196.128/2732RUMS-HOSTING-NETNetwork for HostingASSIGNED PAMay 31, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.196.160/2732ELECTRON-NETSociety with limited liability ELECTRONASSIGNED PASep 1, 2009abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.197.0 - 83.174.197.215216BASHTEL-NETBASHTEL host clientsASSIGNED PAOct 21, 2019abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.197.216/298NET-DIGISOLNetworks of LTD Digital solutionsASSIGNED PAAug 16, 2017abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.197.224/2732BASHTEL-NETBASHTEL host clientsASSIGNED PAOct 21, 2019abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.199.0/24256BIS-NETBashinformsvyaz Company,, BB NetworkASSIGNED PAJun 8, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.200.56/298TKBK-NETNetwork of KBK TuimazyASSIGNED PAFeb 8, 2013abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.200.64/2664UFA-P2P-NETNetwork for P2P client connections in UfaASSIGNED PAMay 28, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.200.128/298SWTC-NETNetwork for JSC SWTCASSIGNED PAApr 22, 2005abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.200.136 - 83.174.200.15924SIB-P2P-NETNetwork for P2P client connections in SibayASSIGNED PAFeb 6, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.200.160/298RFC-NETNetwork of the Federal State Unitary Enterprise "RFC PFO" in SibayASSIGNED PAMay 23, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.200.168/298NET-ZAURALIENetwork of OOO Produkts of ZauralieASSIGNED PASep 13, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.200.176/298SIB-P2P-NETNetwork for P2P client connections in SibayASSIGNED PAMay 4, 2012abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.200.192/2664NFK-P2P-NETNetwork for P2P client connections in NeftekamskASSIGNED PAMay 28, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.201.0/2664SLV-P2P-NETNetwork for P2P client connections in SalavatASSIGNED PAJan 24, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.201.72/298UGOK-NETNetwork for UGOK, UchalyASSIGNED PAMay 24, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.201.80/298UCHALY-ISP-NETNetwork for InetCenter UchalyASSIGNED PAMay 24, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.201.96 - 83.174.201.11924BLR-P2P-NETNetwork for P2P client connections in BeloretskASSIGNED PAMay 30, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.201.120/298RFC-NETNetwork of the Federal State Unitary Enterprise "RFC PFO" in BeloretskASSIGNED PAMay 24, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.201.128 - 83.174.201.16740STR-P2P-NETNetwork for P2P client connections in SterlitamakASSIGNED PAFeb 9, 2012abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.201.168/298NET-PSBNetworks of Bank PSB in SterlitramakASSIGNED PAApr 26, 2011abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.201.176/2816STR-UGNTUSterlitamak branch of UGNTUASSIGNED PAMay 29, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.201.192/298STR-P2P-NETNetwork for P2P client connections in SterlitamakASSIGNED PAFeb 6, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.201.200/298NET-SmileNetworks of LTD Smile in SterlitramakASSIGNED PASep 13, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.201.208 - 83.174.201.25548STR-P2P-NETNetwork for P2P client connections in SterlitamakASSIGNED PAFeb 6, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.202.0/298BIRSKPU-NETNet for Birsk Pedagogical CollegeASSIGNED PAMay 24, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.202.8 - 83.174.202.3124BIRSK-P2P-NETNetwork for P2P client connections in BirskASSIGNED PAMay 28, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.202.32/2732ISH-P2P-NETNetwork for P2P client connections in IshimayASSIGNED PAMay 28, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.202.64/2664TMZ-P2P-NETNetwork for P2P client connections in TuimazyASSIGNED PAMay 28, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.202.128/2664SLV-P2P-NETNetwork for P2P client connections in SalavatASSIGNED PAMay 28, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.202.192 - 83.174.202.24756BLB-P2P-NETNetwork for P2P client connections in BelebeyASSIGNED PAOct 26, 2009abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.202.248/298RFC-NETNetwork of the Federal State Unitary Enterprise "RFC PFO" in BelebeyASSIGNED PAOct 26, 2009abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.203.0/24256MKNET"Megacom" Limited CompanyASSIGNED PAApr 4, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 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
└ 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
└ 83.174.206.0/2664INTERCOM-NETSalavat Intercom networksASSIGNED PAMay 24, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.206.64/2664SLV-P2P-NETNetwork for P2P client connections in SalavatASSIGNED PADec 18, 2009abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.206.128/2816BIB-SLV-NETBashinvestbank, Salavat, RussiaASSIGNED PAAug 26, 2008abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.206.144/2816SLV-P2P-NETNetwork for P2P client connections in SalavatASSIGNED PADec 18, 2009abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.206.160/2816SALSTEKLO-NETJSC SalavatstekloASSIGNED PADec 3, 2009abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.206.176/2816SLV-P2P-NETNetwork for P2P client connections in SalavatASSIGNED PADec 18, 2009abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.206.192/2664MLZ-P2P-NETNetwork for P2P client connections in MeleuzASSIGNED PAMay 29, 2007abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 83.174.207.0/24256SNOS-NETJSC Salavatnefteorgsintez NetworkASSIGNED PAOct 13, 2005abuse@bashtel.ru
via RU-BASHTEL-20040521
└ 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
└ 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
└ 83.174.240.0/204,096DSL-POOLBashinformsvyaz Company, RUMS, DSL POOLASSIGNED PADec 16, 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.

Composition

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

Announced space

Address share

Announced space

Types across the prefix

16,384 addresses
TypeAddressesShareRanges
Residential14,21587%13
Business2,16813%76
VPNanonymizer1<0.01%1

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

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