Glean Outage History

Glean is up right now

Glean had 33 outages in the last 2 years — averaging 1.4 incidents per month.

There were 33 Glean outages since April 9, 2025. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.glean.com

Minor September 3, 2026

Elevated AWS STS errors

Detected by Pingoru
Sep 03, 2026, 11:40 PM UTC
Resolved
Sep 03, 2026, 11:40 PM UTC
Duration
—
Affected: Login
Timeline · 3 updates
  1. investigating Sep 03, 2026, 10:27 PM UTC

    We’re investigating intermittent elevated error rates with AWS STS in us-west-2, including throttling and temporary service-unavailable responses that may affect SAML sign-in. Users may need to retry login, and some backend processing may be delayed while we monitor the situation.

  2. monitoring Sep 03, 2026, 10:47 PM UTC

    The intermittent issue affecting AWS credential refreshes appears to be resolved. Error rates in our backend systems have subsided, and we’ll continue to monitor closely.

  3. resolved Sep 03, 2026, 11:40 PM UTC

    Services have recovered, and we are continuing to monitor system stability.

Read the full incident report →

Minor September 1, 2026

We are investigating an issue impacting Chat/Assistant

Detected by Pingoru
Sep 01, 2026, 06:54 AM UTC
Resolved
Sep 01, 2026, 06:54 AM UTC
Duration
—
Affected: Chat
Timeline · 2 updates
  1. identified Sep 01, 2026, 05:43 AM UTC

    We have identified an internal regression that is causing chat/assistant requests to fail.The root cause has been identified and we are rolling out a fix soon.

  2. resolved Sep 01, 2026, 06:54 AM UTC

    We have rolled out the fix to address the failing chat/assistant errors . Chat/Assistant use cases that were failing should now be working and back to normal.

Read the full incident report →

Minor August 31, 2026

Service degradation from Azure OpenAI causing failed assistant errors

Detected by Pingoru
Aug 31, 2026, 12:13 PM UTC
Resolved
Aug 31, 2026, 12:13 PM UTC
Duration
—
Affected: Other
Timeline · 3 updates
  1. investigating Aug 31, 2026, 09:52 AM UTC

    BYOK customers using Azure OpenAI may experience failed assistant responses. Scope: Affects BYOK customers using Azure OpenAI. We are observing significant errors on Azure OpenAI across customers. Our engineering team is actively working to identify the root cause. We’re sorry for the disruption and appreciate your patience while we investigate.

  2. investigating Aug 31, 2026, 10:37 AM UTC

    Azure OpenAI has acknowledged an ongoing outage and is actively working to resolve it. As a workaround, BYOK customers can configure their default model to use a provider other than Azure OpenAI from the LLM settings page (https://app.glean.com/admin/llms)

  3. resolved Aug 31, 2026, 12:13 PM UTC

    The incident has been resolved. Impact window: From 2:30 pm IST - 4:36 PM IST, some users experienced failed assistant errors. Remediation: Errors from Azure OpenAI have subsided, and the system is operating normally. We apologize for the disruption and appreciate your patience while we addressed this issue.

Read the full incident report →

Minor August 24, 2026

Chat instability caused by hitting OpenAI capacity

Detected by Pingoru
Aug 24, 2026, 06:01 PM UTC
Resolved
Aug 24, 2026, 06:01 PM UTC
Duration
—
Affected: Chat
Timeline · 2 updates
  1. identified Aug 24, 2026, 04:36 PM UTC

    We are hitting Open AI rate limits due to organic traffic growth. We are closely working with Open AI team to fix this.

  2. resolved Aug 24, 2026, 06:01 PM UTC

    OpenAI has increased our capacity. We longer see errors related to this. Please contact our support team if you face any issues

Read the full incident report →

Major July 16, 2026

Chat/Assistant errors due to AzureOpenAI outage

Detected by Pingoru
Jul 16, 2026, 09:35 AM UTC
Resolved
Jul 16, 2026, 09:35 AM UTC
Duration
—
Affected: Chat
Timeline · 1 update
  1. investigating Jul 16, 2026, 09:35 AM UTC

    We have identified an active issue affecting Azure OpenAI Service that is causing chat errors for some users. Our team is actively monitoring the situation and will provide updates as more information becomes available.

Read the full incident report →

Minor July 15, 2026

Elevated chat errors on AWS Bedrock customers

Detected by Pingoru
Jul 15, 2026, 07:05 AM UTC
Resolved
Jul 15, 2026, 07:05 AM UTC
Duration
—
Affected: Chat
Timeline · 1 update
  1. investigating Jul 15, 2026, 07:05 AM UTC

    We are currently seeing elevated chat errors affecting our customers hosted on AWS due to availability issues with Amazon Bedrock. The impact is primarily affecting requests using Claude Opus 4.6 and Claude Sonnet 5. Our team is actively monitoring the situation.

Read the full incident report →

Minor July 13, 2026

Extension actions failing during auth and execution in Chat and Agents

Detected by Pingoru
Jul 13, 2026, 01:40 PM UTC
Resolved
Jul 13, 2026, 01:40 PM UTC
Duration
—
Affected: ChatOtherAgents
Timeline · 5 updates
  1. identified Jul 10, 2026, 05:16 PM UTC

    Some users may experience authentication failures or errors when using extension action packs (e.g., Jira, Confluence, Outlook, Teams). Users attempting to authorize or use these extensions may see HTTP 401 or 500 errors. Our engineering team is actively deploying fixes to affected environments. We expect recovery to progress incrementally as the mitigation completes across deployments. We will continue to closely monitor system behavior as the mitigation completes.

  2. investigating Jul 13, 2026, 04:58 AM UTC

    Some users are experiencing authentication failures or errors when using extension action packs (e.g., Jira, Confluence, Outlook, Teams). Users attempting to authorize or use these extensions might have seen HTTP 401 or 500 errors.

  3. monitoring Jul 13, 2026, 08:43 AM UTC

    Some deployments had issues with executing some of the actions, we have mitigated the issue for almost all the customers

  4. monitoring Jul 13, 2026, 09:06 AM UTC

    We are rolling out a mitigation for the issue affecting Atlassian and other related actions. Impact now: Fix deployed to most of the users. Some users may still experience with Atlassian and related actions, but we expect it to recover as the mitigation completes. We will continue to closely monitor system behavior as the mitigation completes.

  5. monitoring Jul 13, 2026, 01:40 PM UTC

    We have deployed a fix for the issue affecting extension actions, and early signals show error rates have reduced and things are back to normal. We are keeping the systems under heightened monitoring to ensure they remain stable. Impact: Most users should now be able to use the extension actions. If you continue to experience issues, please contact Glean support.

Read the full incident report →

Minor July 10, 2026

Glean Assitant Errors

Detected by Pingoru
Jul 10, 2026, 05:55 AM UTC
Resolved
Jul 10, 2026, 05:55 AM UTC
Duration
—
Affected: Chat
Timeline · 3 updates
  1. monitoring Jul 10, 2026, 03:31 AM UTC

    We are rolling out a mitigation for the issue affecting chat and assitant. Impact now: we expect improving as the mitigation completes. We will continue to closely monitor system behavior as the mitigation completes.

  2. monitoring Jul 10, 2026, 04:26 AM UTC

    We have disabled the change and confirmed that user experience has returned to normal.

  3. resolved Jul 10, 2026, 05:55 AM UTC

    The incident has been resolved. We apologize for the disruption and appreciate your patience while we addressed this issue.

Read the full incident report →

Minor July 3, 2026

Client Token management API is failing

Detected by Pingoru
Jul 03, 2026, 03:02 PM UTC
Resolved
Jul 03, 2026, 03:02 PM UTC
Duration
—
Timeline · 4 updates
  1. identified Jul 03, 2026, 09:26 AM UTC

    We have identified the cause of the issue. We are currently implementing a fix and monitoring its effect.

  2. identified Jul 03, 2026, 09:33 AM UTC

    Incident: Client Token management API is failing We have identified the cause of the issue. We are currently implementing a fix and monitoring its effect.

  3. monitoring Jul 03, 2026, 02:21 PM UTC

    We have deployed a fix for the issue globally. We are keeping the systems under heightened monitoring to ensure they remain stable. Impact: Most admin users should now see the Client Token management functionality restored. If you continue to experience issues, please contact Glean support.

  4. resolved Jul 03, 2026, 03:02 PM UTC

    The incident has been resolved. We apologize for the disruption and appreciate your patience while we addressed this issue.

Read the full incident report →

Minor May 18, 2026

Elevated Google Vertex AI rate limit error on Claude Opus 4.6 model

Detected by Pingoru
May 18, 2026, 04:04 PM UTC
Resolved
May 18, 2026, 04:04 PM UTC
Duration
—
Affected: ChatAgents
Timeline · 5 updates
  1. identified May 18, 2026, 09:00 AM UTC

    We have identified elevated rate limiting from Google Vertex AI. Leading to this error on Glean - "Vertex AI is at capacity right now, so I can't get a response. Give it a few minutes and try again." Our engineering team continues to work with Google support on this issue. Symptom Affected customers may encounter transient errors (429/529) when making requests to the Claude Opus 4.6 model via Glean Chat or Agents. Workaround Affected customers may consider using alternative models.

  2. investigating May 18, 2026, 02:01 PM UTC

    We are experiencing an issue with Vertex AI Online Prediction beginning on Sunday, 2026-05-17 21:10 PDT. Our engineering team continues to investigate the issue. We will provide an update by Monday, 2026-05-18 11:00 PDT with current details. We apologize to all who are affected by the disruption. Symptom Affected customers may encounter transient errors (429/529) when making requests to the Claude Opus 4.6 model Workaround Affected customers may consider using alternative models.

  3. identified May 18, 2026, 02:02 PM UTC

    We have identified elevated rate limiting from Google Vertex AI. We are monitoring the issue and will share updates as service recovers.

  4. resolved May 18, 2026, 03:39 PM UTC

    GCP has resolved the issue with Vertex AI Online Prediction for all affected users as of Monday, 2026-05-18 07:49 PDT. We thank you for your patience while we worked on resolving the issue.

  5. resolved May 18, 2026, 04:04 PM UTC

    The incident has been resolved. Impact window: From May 18, 2026, 9:00 AM UTC to Monday, May 18, 2026, at 14:49 UTC, some users experienced elevated rate limiting from Google Vertex AI. Remediation: The issue with Vertex AI Online Prediction has been resolved for all affected users. We apologize for the disruption and appreciate your patience while we addressed this issue.

Read the full incident report →

Minor May 11, 2026

Search requests timeout in AWS instances

Detected by Pingoru
May 11, 2026, 05:07 AM UTC
Resolved
May 11, 2026, 05:07 AM UTC
Duration
—
Affected: Search
Timeline · 2 updates
  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.

Read the full incident report →

Minor May 7, 2026

Glean AWS customers might experience intermittent server errors

Detected by Pingoru
May 07, 2026, 11:46 AM UTC
Resolved
May 07, 2026, 11:46 AM UTC
Duration
—
Timeline · 2 updates
  1. monitoring May 07, 2026, 09:15 AM UTC

    We are currently observing increased latencies and intermittent server errors with respect to Bedrock models. Our team is actively monitoring the issue .

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

    The incident has been resolved. Impact window: From 1:00 AM to 4:15 AM PDT, some users experienced degraded AI search and assistant performance, including slower response times, due to elevated latency in AWS Bedrock's US-WEST-2 region. Remediation: AWS rebalanced capacity and applied scaling adjustments to their infrastructure, and we have confirmed that user experience has returned to normal. We apologize for the disruption and appreciate your patience while the issue was addressed.

Read the full incident report →

Minor April 23, 2026

Permanent Fix Deployed

Detected by Pingoru
Apr 23, 2026, 06:43 AM UTC
Resolved
Apr 23, 2026, 06:43 AM UTC
Duration
—
Affected: Glean service
Timeline · 1 update
  1. resolved Apr 23, 2026, 06:43 AM UTC

    We have rolled out a permanent fix to this issue

Read the full incident report →

Minor April 14, 2026

Incident resolved

Detected by Pingoru
Apr 14, 2026, 05:19 PM UTC
Resolved
Apr 14, 2026, 05:19 PM UTC
Duration
—
Affected: Glean service
Timeline · 1 update
  1. resolved Apr 14, 2026, 05:19 PM UTC

    The incident has been resolved. Impact window: From Apr 13 09:48:48 AM PDT to Apr 14 10:11:43 AM PDT, some users experienced elevated chat errors due to an upstream OpenAI API auth issue. Remediation: We escalated to OpenAI and OpenAI has resolved the issue upstream. We have monitoring in place that confirms the errors have now been resolved. We apologize for the disruption and appreciate your patience while we addressed this issue.

Read the full incident report →

Minor March 25, 2026

Atlassian token request rate limiting

Detected by Pingoru
Mar 25, 2026, 07:39 AM UTC
Resolved
Mar 25, 2026, 07:39 AM UTC
Duration
—
Affected: Glean service
Timeline · 1 update
  1. resolved Mar 25, 2026, 07:39 AM UTC

    The issue of authentication errors for Jira and Confluence is now resolved. The root cause was an IP block from Atlassian which was triggered by a spike in the number of user token requests. We have worked with Atlassian to get the IP block removed. We have also made fixes to fail gracefully when Atlassian starts returning errors for auth requests.

Read the full incident report →

Minor March 9, 2026

Search and Chat failures

Detected by Pingoru
Mar 09, 2026, 04:34 PM UTC
Resolved
Mar 09, 2026, 04:34 PM UTC
Duration
—
Affected: Glean service
Timeline · 1 update
  1. resolved Mar 09, 2026, 04:34 PM UTC

    Google has confirmed multiple GCP products are affected in us-central1. Multiple cloud services impacted Issue has been mitigated now after a confirmation from google

Read the full incident report →

Minor March 4, 2026

Users facing login issues

Detected by Pingoru
Mar 04, 2026, 09:07 AM UTC
Resolved
Mar 04, 2026, 09:07 AM UTC
Duration
—
Affected: Glean service
Timeline · 1 update
  1. resolved Mar 04, 2026, 09:07 AM UTC

    Fix has been rolled out successfully and users are no longer facing login issues

Read the full incident report →

Minor February 28, 2026

gemini-models-429-errors

Detected by Pingoru
Feb 28, 2026, 08:02 AM UTC
Resolved
Feb 28, 2026, 08:02 AM UTC
Duration
—
Affected: Glean service
Timeline · 1 update
  1. resolved Feb 28, 2026, 08:02 AM UTC

    Google confirms the issue is fixed.

Read the full incident report →

Major January 28, 2026

Glean MCP outage

Detected by Pingoru
Jan 28, 2026, 11:41 AM UTC
Resolved
Jan 28, 2026, 11:41 AM UTC
Duration
—
Affected: Glean service
Timeline · 1 update
  1. resolved Jan 28, 2026, 11:41 AM UTC

    The issue has been resolved.

Read the full incident report →