Loading status…
Grammarly status · SaaS · checked (2s ago)
No — Grammarly is not down. All Grammarly systems are reported operational.
According to Grammarly's official status page, Grammarly was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Grammarly's feed reported no outage in 100.00% of our checks.
Everything above is read from Grammarly's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Grammarly in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Grammarly checks writing for grammar, clarity and tone through browser extensions, desktop apps and an editor, with generative features layered on. It processes text server-side, which is why an outage stops suggestions appearing anywhere.
The status page separates the editor and the extensions from the account and authentication systems, and separates the enterprise offering. Suggestions failing while you can still type is the normal shape of a Grammarly incident — the extension degrades to doing nothing rather than blocking the page it is on.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Grammarly's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Grammarly was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 2s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Grammarly's status endpoint.
Grammarly has published 24 incidents in the last 12 months, the 20 most recent shown here. Only what Grammarly posted itself — not every problem users hit.
resolved · Aug 14, 03:24 PM (36d ago)
resolved · Jul 29, 05:47 PM (52d ago)
resolved · Jul 16, 08:59 AM (65d ago)
resolved · May 15, 04:33 PM (127d ago)
resolved · May 7, 07:30 AM (135d ago)
resolved · Apr 28, 02:15 PM (144d ago)
resolved · Apr 10, 06:42 PM (162d ago)
resolved · Mar 27, 06:14 PM (176d ago)
resolved · Mar 9, 04:52 PM (194d ago)
resolved · Feb 6, 08:09 PM (225d ago)
resolved · Feb 6, 03:02 PM (225d ago)
resolved · Feb 5, 01:46 AM (227d ago)
resolved · Feb 3, 02:51 AM (229d ago)
resolved · Jan 30, 08:12 PM (232d ago)
resolved · Jan 22, 09:50 PM (240d ago)
resolved · Jan 21, 12:40 AM (242d ago)
resolved · Jan 20, 09:57 PM (242d ago)
resolved · Nov 6, 10:29 PM (317d ago)
resolved · Oct 23, 07:17 PM (331d ago)
resolved · Oct 21, 07:49 AM (333d ago)
The extension is frequently blocked rather than broken: many sites, and most rich text editors inside them, disable third-party extensions, and corporate policies block Grammarly outright for data reasons. Suggestions stopping in one application while working in another points at that application. A free account simply does not receive the advanced suggestions a paid one does.
