Changes / Grammarly / The Grammarly Editor is not working as expected
Grammarly: Critical incident: The Grammarly Editor is not working as expected
Summary
A critical Grammarly Editor interruption made the editor slow or unresponsive and caused connection trouble for some users. It started at 2026-03-27 18:14 UTC and was resolved at 2026-03-27 18:31 UTC, lasting 17 min; Grammarly reported implementing a fix at 03-27 18:26 UTC but did not state a cause.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: The Grammarly Editor is not working as expected
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-03-27 18:14 UTC
Before: not present
After: 2026-03-27 18:31 UTC
Before: not present
After: Grammarly Editor
Before: not present
After: 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.
Before: not present
After: A fix has been implemented, and we're monitoring the results.
Before: not present
After: This issue has been resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: The Grammarly Editor is not working as expected (this change) A critical Grammarly Editor interruption made the editor slow or unresponsive and caused connection trouble for some users. It started at 2026-03-27 18:14 UTC and was resolved at 2026-03-27 18:31 UTC, lasting 17 min; Grammarly reported implementing a fix at 03-27 18:26 UTC but did not state a cause. | Major incident |
All Grammarly changes → · Grammarly profile · Markdown · JSON