Glean incident

Search requests timeout in AWS instances

Minor Resolved View vendor source →

Glean experienced a minor incident on May 11, 2026 affecting Search, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 11, 2026, 05:07 AM UTC
Resolved
May 11, 2026, 05:07 AM UTC
Duration
Detected by Pingoru
May 11, 2026, 05:07 AM UTC

Affected components

Search

Update timeline

  1. identified May 08, 2026, 06:20 AM UTC

    The incident was triggered by an AWS availability issue affecting underlying compute and storage in a single availability zone. That event left the search cluster without a healthy master node, which caused search requests to time out or fail. During recovery, the master node could not restart because its persistent volume was still marked in use on the impacted instance, delaying failover until the volume attachment problem was resolved and healthy search capacity was restored. This is affecting only the AWS hosted instances. Please refer AWS status page: https://health.aws.amazon.com/health/status?path=open-issues

  2. resolved May 11, 2026, 05:07 AM UTC

    We have successfully restored all Glean instances in the us-east-1 region that were impacted by the recent AWS EC2 outage.