Grammarly has grown so much that few experienced internet surfers have never heard of it. The company has become one of the most trusted sources for grammar correction for written content. If you use it, you might have noticed that the company seems to be suffering some kind of outage.
Most users have been reporting that Grammarly simply isn’t responding to the text they type within familiar data entry screens online, no longer providing any form of spelling or grammar correction. Although its website is online, you may find it difficult to log in (or if you can log in, you might find that a series of errors will pop up announcing service troubles).
The company released the following message this morning: “We’re experiencing some service interruptions at the moment. Some users may have trouble logging in, editing their documents, or accessing their account settings. Other users may not be able to see suggestions or corrections from Grammarly. We’re investigating the problem and will provide an update as soon as possible.” – (Nov 08, 2024 – 08:27 PST)
It has since posted a few more updates announcing that it is still looking into the issue and thanking everyone for their patience. Thus, for now, there aren’t any signs as to what the issue is or what might have caused it. It could have been anything from a bad update that was rolling out to its service (or an update to a partner service it uses) to a cyberattack.
Just know that you aren’t alone if you are experiencing any issues with the service. There is nothing wrong with your system, connection, or anything else on your end. It’s just a waiting game until the company is able to identify and correct the issue.
Update (12:17 PST): Grammarly has reported that the issue was resolved. It mentioned that the company had implemented a fix to resolve the issue and to bring services back online. Thus at this stage, one can assume it was likely an error made to a patch/update of some sort that needed a workaround (or something similar to that, at least). Either way, services appear to be working again.
