Grammarly Outage History
20 incidents recorded over the last 365 days, 20 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Grammarly Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 20, 2026 | Issues with Superhuman Go not loading or showing error messagesThe incident has been resolved. Superhuman Go is back up and running. | 2h 15m | Resolved |
| Sep 22, 2026 | Chat is not working at go.superhuman.comThis incident has been resolved. | 1h 3m | Resolved |
| Aug 14, 2026 | Users May Experience Login Issues Across Some Grammarly and Superhuman ProductsThis incident has been resolved. | 2h 33m | Resolved |
| Jul 29, 2026 | Go may work slowly or intermittentlyThis incident has been resolved. | 7h 22m | Resolved |
| Jul 16, 2026 | Login to Grammarly via superhuman.com may be temporarily unavailableAmazon has resolved the CloudFront service outage, and our services are back to normal. | 4h 13m | Resolved |
| May 15, 2026 | Some Grammarly and Superhuman users may be unable to log inThis incident has been resolved. | 12 min | Resolved |
| May 7, 2026 | PDF reports may not be available in the Grammarly EditorThis incident has been resolved. | 58 min | Resolved |
| Apr 28, 2026 | Generative AI features may not work as expected in Grammarly for WindowsThis issue has been resolved, and the error message should disappear in a couple of minutes. Thanks for your patience! | 1h 22m | Resolved |
| Apr 10, 2026 | Document Creation, Upload, and Opening Failing in Grammarly EditorThis incident has been resolved. | 3h 54m | Resolved |
| Mar 27, 2026 | The Grammarly Editor is not working as expectedThis issue has been resolved. | 17 min | Resolved |
| Mar 9, 2026 | Increased latency across Grammarly product offeringsThis issue has been resolved. | 3h 14m | Resolved |
| Feb 6, 2026 | The AI-powered Docs is not working as expectedThis incident has been resolved. | 42 min | Resolved |
| Feb 6, 2026 | Some agents may be unavailable or work intermittentlyThis issue has been resolved, and the functionality should be restored. | 46 min | Resolved |
| Feb 5, 2026 | Scheduled Maintenance: Subscription ManagementThe scheduled maintenance related to subscription management has been successfully completed. All subscription-related functionality has been fully restored. Existing subscriptions and active users were not impacted… | 5h 51m | Resolved |
| Feb 3, 2026 | Some Grammarly users may be unable to log in using FacebookThis incident has been resolved. | 63h 47m | Resolved |
| Jan 30, 2026 | Some Grammarly users may be unable to log inThis incident has been resolved. | 2h 12m | Resolved |
| Jan 22, 2026 | We're experiencing a service interruptionThis incident has been resolved. | 27h 19m | Resolved |
| Jan 21, 2026 | Supehuman Go and AI Chat experience temporary service interruptionThis incident has been resolved. | 1h 8m | Resolved |
| Jan 20, 2026 | Users encounter an error when creating or opening a document in Docs at https://app.grammarly.com/This incident has been resolved. | 11 min | Resolved |
| Nov 6, 2025 | Issues logging in at https://superhuman.com and https://app.grammarly.comThis incident has been resolved. | 4h 18m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Grammarly incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Grammarly Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Grammarly acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Grammarly outage in this window ran 2d 15h, against a mean recovery of 6h 41m. If you depend on Grammarly in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.