Chat disabled

I got my chat disabled , How to know whether it's a permanent restriction or temporary ?
during games, it shows me " chat disabled" with no duration or anything.. 
and how can i get it enabled again ?

yeah it's every game , thx for ur help

I've tried the application and i found that live chat is working normally , what's the matter with website ?

I'm having the same problem. Chat is disabled at every single game today first time in a long time!

I never even chat during game, so I haven't used any abusive or inappropriate language for that matter.
I tried disabling my Ad Blocker but that doesn't seem to make a difference. Every single game is showing this.
A few years ago I had the same experience, again I don't chat in game. I'm too busy concentrating. I'm using Waterfox Web Browser. I don't think it is web browser related.
I did not get any warning. The only message I got is from Chess.com having 18 points refunded as I lost to some cheaters in Rapid.
The only thing I did say sarcastically to one cheater is "great engine" in chat. I'm not sure if my chat is disabled for this. But it was very obvious that I lost to that cheater as later on, his account indeed got banned and my points were refunded!
I normally don't say anything in chat. But if my chat got disabled for this reason, that's plain wrong as that's not offensive at all and doesn't warrant a Chat ban.
Again, there's no explanation from Chess.com to ask for the reasons behind the Chat being disabled. If such comments like these are inappropriate they should warn us if this is a violation. Clearly that's also not naming and shaming as I am not publicly naming the cheater on the forum.

Go to https://www.chess.com/settings/liveIn Settings--->Live Chess---> Game Chat--->Select: Nobody and click Save.
In my case the setting is marked as Everyone but I am unable to send any chat messages for some reason.

contact support i guess. i summon @martin_stahl

I am offensive by nature and must be contained, I understand

contact support i guess. i summon @martin_stahl

I messaged Martin, no indication of my chat being muted from what his response was.
So, definitely this is some weird bug that occurred out of no where.
Other people are reporting this issue in another thread as well. The question, is it happening to all users or just certain users?
Because if it is happening only with certain users then there must be some glitch related to certain accounts and not being triggered with others?
Or could it be the algorithm of Chess.com chat abuse detection wrongly thinks I wrote something wrong in chat? I had a player insult me yesterday in chat after I beat him.
Of-course, I ignored and did not respond nor did I bother to report the chat message. I genuinely don't care plus I know he probably said it out of frustration. At the same time I get plenty of compliments from other players as well. Plus late night I don't always perform my best.
But the question is whether the Chat is disabled because the AI is confused and thinks I made the bad remarks and disabled my chat.

Jokes aside, I've searched the Discord server history and apparently some people were banned for only saying "gg", which I have said as well, I think you're on to something, it might be something with the algorithm

I found out that there was an update that had some bugs causing the issue. That update has been rolled back until the bugs are fixed so chat should be working for those that had the problem

I can confirm that the issue has been fixed and chat is working again, but for how long I do not know!
For a moment I was paranoid yesterday thinking what must have gone wrong. I had this same issue a few years ago and I guess it was the same bug.

Not that I really care about the chat functionality, it's just that I didn't want to think my account was being muted unfairly.

Also when Chat is disabled there's that annoying round question mark icon that's a little distracting. Now I don't have to see it when chat is fixed again.
Most of the time from my experience people don't usually chat in chess, it is usually very rare.

Whatever it was before was a different issue. This was caused by a change in code that was newly implemented