Skip to main content
Grammarly

Issues with Superhuman Go not loading or showing error messages

Partial outage Lasted 2h 15m · started · Grammarly's page

Level
confirmed
Worst impact
Partial outage
Components
Superhuman Go & Agents
Down Index
30of 100

What to do

  • Check whether you use Grammarly Superhuman Go & Agents. 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 2h 15m it lasted.

    Anything that failed between 2026-10-20 18:03 UTC and 2026-10-20 20:18 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

  1. identified

    Superhuman Go may fail to load the conversation or may display an error message. Our engineers are investigating the issue and will provide an update shortly.

    provider

  2. resolved

    The incident has been resolved. Superhuman Go is back up and running.

    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-4790f40359

Is Grammarly still down?

No, this incident was resolved 2026-10-20 20:18 UTC. For Grammarly's live state, see https://down.guide/grammarly.

How long did it last?

2h 15m, from 2026-10-20 18:03 UTC to 2026-10-20 20:18 UTC, by the times Grammarly posted.

What was affected?

Grammarly named Superhuman Go & Agents.

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.