CompaniesGoogle WorkspaceIncidents
Google Workspace: **Summary** We are experiencing an issue with Google Keep where users may be unable to access keep.google.com via browser. **Description** The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our engineering team is aware of the situation and is actively implementing mitigations. We do not have any ETA at the moment. We will provide the next update by Friday, 2026-03-20 21:00 US/Pacific. **Customer Symptoms** Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. **Workaround** Users are able to use Google Keep via the Android or iOS mobile app.
Affected components: Google Keep
Timeline of updates
- service outage
Summary
We are experiencing an issue with Google Keep where users may be unable to access keep.google.com via browser.
Description
The issue began on Friday, 2026-03-20 15:30 US/Pacific.
Our engineering team is aware of the situation and is actively implementing mitigations. We do not have any ETA at the moment.
We will provide the next update by Friday, 2026-03-20 21:00 US/Pacific.
Customer Symptoms
Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational.
Workaround
Users are able to use Google Keep via the Android or iOS mobile app. - service outage
Summary
We are experiencing an issue with Google Keep where users may be unable to access keep.google.com via browser.
Description
The issue began on Friday, 2026-03-20 15:30 US/Pacific.
Our engineering team is aware of the situation and is actively implementing mitigations. We do not have any ETA at the moment.
We will provide the next update by Friday, 2026-03-20 23:00 US/Pacific.
Customer Symptoms
Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational.
Workaround
Users are able to use Google Keep via the Android or iOS mobile app. - service outage
Summary
We are experiencing an issue with Google Keep where users may be unable to access keep.google.com via browser.
Description
The issue began on Friday, 2026-03-20 15:30 US/Pacific.
Our mitigation efforts are underway and we are seeing the signs of recovery. We do not have an ETA for full mitigation.
We will provide the next update by Saturday, 2026-03-21 00:30 US/Pacific.
Customer Symptoms
Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational.
Workaround
Users are able to use Google Keep via the Android or iOS mobile app. - resolved
Description
The issue has been mitigated as of Friday, 2026-03-20 22:03 US/Pacific.
The service issue which resulted in connection timeouts and 502 error pages, was caused by excess traffic impacting the keep.google.com. Our engineering team has implemented a mitigation and is continuing to work to ensure long-term service stability and prevent recurrence.
We thank you for your patience while we worked on resolving the issue.
Changes Rewindex caught on this incident
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
23a7e31042e43c9a…
Impact, status and times are the vendor’s own, as last archived. View on www.google.com (opens in new tab).
Google Workspace profileRecent Google Workspace incidentsMarkdownJSON