yesterday I was waiting for 25 minutes and I couldn’t contact with live chat, and right now I’m waiting for 15 minutes and I only can see “Please wait..”
is it ok live chat?
Live Chat is working, may be due to long queue your chat didn’t picked early.
i know why you were trying to chat 
I have found and stopped the user, I am truncating only the db name here, but someone was connecting outside from two servers to MSSQL11 and doing some continual processes(sleeping at the point of this paste, but wasn’t always) making HUGE cpu usage.
169 sleeping dbuser_dbname SERVER . dbuser_dbname AWAITING COMMAND 111974 56 07/10 05:41:24 169 0
107 sleeping dbuser_dbname MASTER . dbuser_dbname AWAITING COMMAND 310822 121 07/10 05:41:24 107 0
The 111974 and 310822 are cputime fields, and far larger than any task on the server, including built in tasks. It looks like they may have been doing something like this each morning around this time, and I was up working another issue and caught it today. These are external IPs, and while we allow this for management purposes, syning to servers, doing extensive remote processing is NOT allowed at all. (I am not telling this to you, it was not you, I am saying it is our policy) I am blocking these machines (they referred to them as ‘master’ and ‘server’ here, those are not changed names, direct as it was) from connecting to the server as it is clearly abusive.
Just to compare, normal site db usage will run from the cpu time in 100,s up to sometimes 10-20,000 a few times more than that, but not on a steady basis, system processes like check pointing, full text indexing, may be substantially higher, but they are long term and systemwide processes, not just one user and one db. with exception of a system process the highest cputime upon this check.