Skip to content

Incident detail

**Summary** We are experiencing an issue with Google Keep where users may be unable to access keep.google.com via…

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.

Resolved incidentCritical

Timeline window

to

Outage alerts

Get alerted the next time Google Workspace breaks

Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update Google Workspace posted, oldest to newest, exactly as it appeared on their official status page.

  1. Investigating

    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.

  2. Monitoring

    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.

  3. Monitoring

    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.

  4. 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.

Keep exploring

More from Google Workspace

Neighboring incidents on Google Workspace's timeline and the rest of their record on OutageDeck.