Is Grammarly down?
Last checked 4m agoNo incidents right now.
Grammarly is operational right now. Last checked 4m ago; the most recent incident resolved 13d ago.
Real-time Grammarly status, recent outages, and incident history — pulled directly from Grammarly's official status page at https://status.grammarly.com every 5 minutes. Pingoru tracks 23 Grammarly services and has captured 3 incidents in the last 90 days (99.81% uptime). Get email, Slack, Discord, or webhook alerts the moment Grammarly reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Login
Timeline · 3 updates
- identified · Jul 16, 2026, 08:59 AM UTC
We have identified an issue affecting access to Grammarly services via superhuman.com. This may be related to a temporary Amazon CloudFront outage. We apologize for any inconvenience, and updates will be provided as they become available.
- monitoring · Jul 16, 2026, 09:10 AM UTC
We introduced temporary changes to mitigate this issue during CloudFront's outage. Access to Grammarly via superhuman.com should now be restored. We are monitoring the results.
- resolved · Jul 16, 2026, 01:12 PM UTC
Amazon has resolved the CloudFront service outage, and our services are back to normal.
Latest: Amazon has resolved the CloudFront service outage, and our services are back to normal.
-
- Login
Timeline · 3 updates
- investigating · May 15, 2026, 04:33 PM UTC
We’re currently working through a service disruption that is preventing our users from logging in or resetting passwords. We apologize for any inconvenience, and updates will be provided as they become available.
- monitoring · May 15, 2026, 04:43 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · May 15, 2026, 04:45 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Grammarly Editor
Timeline · 3 updates
- investigating · May 07, 2026, 07:30 AM UTC
We’re currently investigating an issue with generating or downloading PDF reports in the Grammarly Editor. We apologize for any inconvenience and will provide an update as soon as possible.
- identified · May 07, 2026, 08:12 AM UTC
The issue has been identified and a fix is being implemented.
- resolved · May 07, 2026, 08:29 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Started Jul 16, 2026, 08:59 AM UTC · Resolved Jul 16, 2026, 01:12 PM UTC · 4h 13m
- Started May 15, 2026, 04:33 PM UTC · Resolved May 15, 2026, 04:45 PM UTC · 12m
- Started May 07, 2026, 07:30 AM UTC · Resolved May 07, 2026, 08:29 AM UTC · 58m