PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Grammarly is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Grammarly. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Grammarly issues today?

As of Oct 12, 2026 12:20 UTC, 0 users had reported issues with Grammarly in the previous 24 hours.

How can I report a Grammarly outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Productivity

Is Grammarly down right now?

NormalOfficial status last polled Oct 12, 2026 11:54 UTCgrammarly.com Official status page

Grammarly writing assistant

Are you on the Grammarly team and see something inaccurate? Report it to us. We respond within one business day.

Is Grammarly down right now?

No. Grammarly has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 12, 2026 12:20 UTC

Normal

Grammarly is operating normally

As of Oct 12, 2026 12:20 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

Sep 22, 2026 16:16 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Grammarly.

Incident days

No recorded incident

2h 20m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Grammarly. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

1 incident

Busiest day

2h 20m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Grammarly: vendor-reported major incident on September 22 (tracked 2h 20m)

Sep 22, 01:56 PM → Sep 22, 04:16 PM · 2h 20m · high

Grammarly reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 2h 20m, from Tue, 22 Sep 2026 13:56:19 GMT to Tue, 22 Sep 2026 16:16:21 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration

2h 20m

tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

Sep 22, 01:56 PM
The vendor reported a major-impact incident on its own status page; PulseWatch began tracking it
Sep 22, 01:56 PM
Status updated: possible issue
Sep 22, 04:16 PM
PulseWatch closed the incident

Official updates

Sep 22, 01:56 PM
Grammarly reported the incident on its status page.
View official source

Reliability

Detected by PulseWatch

30-day uptime

99.68%

90-day uptime

99.89%

Calculated from Grammarly's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other productivity services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedHigh

Grammarly: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Grammarly or have an alert rule on it can be alerted, labelled vendor-reported.

9/22/2026, 1:56:19 PM · 2h 20m

01:56 PM04:16 PM

Detection9/22/2026, 1:56:19 PM · 19d ago

Detected — high severity

ResolvedHigh