- Level
- confirmed
- Worst impact
- Degraded
- Components
- Login
- Down Index
- 22of 100
What to do
Check whether you use Grammarly Login. 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 4h 14m it lasted.
Anything that failed between 2026-07-16 08:59 UTC and 2026-07-16 13:12 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
- identified
We have identified an issue affecting access to Grammarly services via superhuman.com. This may be related to a temporary Amazon CloudFront outage. We apologize for any inconvenience, and updates will be provided as they become available.
provider
- monitoring
We introduced temporary changes to mitigate this issue during CloudFront's outage. Access to Grammarly via superhuman.com should now be restored. We are monitoring the results.
provider
- resolved
Amazon has resolved the CloudFront service outage, and our services are back to normal.
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-8a94a167dd
Is Grammarly still down?
No, this incident was resolved 2026-07-16 13:12 UTC. For Grammarly's live state, see https://down.guide/grammarly.
How long did it last?
4h 14m, from 2026-07-16 08:59 UTC to 2026-07-16 13:12 UTC, by the times Grammarly posted.
What was affected?
Grammarly named Login.
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.