- Level
- confirmed
- Worst impact
- Degraded
- Components
- Grammarly Editor
- Down Index
- 20of 100
What to do
Check whether you use Grammarly Grammarly Editor. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 43m it lasted.
Anything that failed between 2025-01-23 17:36 UTC and 2025-01-23 19:20 UTC may need a replay.Subscribe to Grammarly's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=grammarly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Grammarly 3
- investigating
We are currently experiencing a service interruption that may cause the Grammarly Editor to be slow or unresponsive. Some users may also have trouble connecting to Grammarly. Sorry about that! We're investigating the cause and will provide an update as soon as possible.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
The Grammarly Editor is back up and running! Thanks for your patience!
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-98920c86ae
Is Grammarly still down?
No, this incident was resolved 2025-01-23 19:20 UTC. For Grammarly's live state, see https://down.guide/grammarly.
How long did it last?
1h 43m, from 2025-01-23 17:36 UTC to 2025-01-23 19:20 UTC, by the times Grammarly posted.
What was affected?
Grammarly named Grammarly Editor.
What caused it?
Grammarly hasn't published a root cause. If it does, it shows here.
Where does this come from?
Grammarly's official status page, https://status.grammarly.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.