Outage recap · Grammarly

Grammarly outage — July 29, 2026

On July 29, 2026, Grammarly had a reported incident on Grammarly's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Go may work slowly or intermittently

major
Started
Jul 29, 1:47 PM EDT
Resolved
Jul 29, 9:09 PM EDT
Duration
7h 22m

Grammarly's updates (3)

  1. identified · Jul 29, 1:47 PM EDT

    We're currently working on a fix for an issue causing slow performance in Go. Users may experience delays when loading, editing, or saving documents at app.grammarly.com or using Go & agents. Our team is actively looking into the issue and working to restore normal performance as quickly as possible. We'll post an update as soon as we have more information. Thank you for your patience.

  2. monitoring · Jul 29, 2:04 PM EDT

    A fix has been implemented, and we're monitoring the results.

  3. resolved · Jul 29, 9:09 PM EDT

    This incident has been resolved.

What our checks recorded

We checked Grammarly 87 times from Grammarly's start time to its resolution, once every five minutes. Every one of them reached Grammarly's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 164 ms, against 170 ms over the 24 hours before. Grammarly posted the incident at Jul 29, 1:47 PM EDT.

Updates are Grammarly's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

AIDownCheck is not affiliated with Grammarly. This recap summarizes incidents published on Grammarly's official status page.