- Level
- confirmed
- Worst impact
- Major outage
- Components
- Grammarly Editor
- Down Index
- 37of 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 11m it lasted.
Anything that failed between 2026-01-20 21:57 UTC and 2026-01-20 22:08 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 2
- identified
The issue has been identified and a fix is being implemented.
provider
- resolved
This incident has been resolved.
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-38ab558ff0
Is Grammarly still down?
No, this incident was resolved 2026-01-20 22:08 UTC. For Grammarly's live state, see https://down.guide/grammarly.
How long did it last?
11m, from 2026-01-20 21:57 UTC to 2026-01-20 22:08 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.