Glean Outage History
Glean is up right nowPingoru has recorded 36 incidents for Glean: 28 in the last 12 months and 7 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 5 | 14 of 720 (2%) |
| May 2026 | 3 | 77 of 744 (10%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 5 | 11 of 744 (1%) |
| August 2026 | 2 | 2 of 744 (0%) |
| September 2026 | 2 | 3 of 720 (0%) |
| October 2026 | 3 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 107 (0%) |
Incidents, newest first
Notice October 26, 2026 We are investigating elevated Server errors affecting Claude model requests through AWS Bedrock 2h 3m
Started Oct 26, 2026, 09:01 AM UTC· resolved Oct 26, 2026, 11:04 AM UTC
- investigating Oct 26, 2026, 09:04 AM UTC
We are investigating elevated Server errors affecting Claude model requests through AWS Bedrock. We will share updates as more information becomes available.
- resolved Oct 26, 2026, 11:04 AM UTC
Claude requests through AWS bedrock have stabilized. We are continuing to monitor performance closely to ensure ongoing stability.
Notice October 22, 2026 We are investigating an issue impacting AWS customers using Sonnet 5.5 through Bedrock 1h 43m
Started Oct 22, 2026, 08:24 AM UTC· resolved Oct 22, 2026, 10:07 AM UTC
- investigating Oct 22, 2026, 08:29 AM UTC
We are investigating elevated Server errors affecting Claude Sonnet 5.5 requests through AWS Bedrock. We will share updates as more information becomes available.
- resolved Oct 22, 2026, 10:07 AM UTC
Claude Sonnet requests through AWS bedrock have stabilized as of 10:00 AM UTC. We are continuing to monitor performance closely to ensure ongoing stability.
Notice October 12, 2026 AWS Bedrock rate limiting for Claude Opus 8h 44m
Started Oct 12, 2026, 09:07 AM UTC· resolved Oct 12, 2026, 05:52 PM UTC
- investigating Oct 12, 2026, 09:17 AM UTC
We are investigating elevated HTTP 503 errors affecting Claude Opus 4.8 requests through AWS Bedrock. Some requests may fail. We will share updates as more information becomes available.
- investigating Oct 12, 2026, 09:40 AM UTC
Recovery has been confirmed for the elevated HTTP 503 errors affecting Claude Opus 4.8 requests through AWS Bedrock. We will continue to monitor service health.
- investigating Oct 12, 2026, 12:09 PM UTC
We are investigating elevated HTTP 429 rate-limit errors affecting Claude Opus 4.8 and 5.5 requests through AWS Bedrock. Based on current information, the issue is limited to AWS-hosted customers in us-west-2. AWS has acknowledged the issue.
- investigating Oct 12, 2026, 03:43 PM UTC
HTTP 429 rate-limit errors from AWS Bedrock remain unresolved. We are initiating failover of all affected customers to an alternate provider as a mitigation. We will share another update as the failover progresses.
- resolved Oct 12, 2026, 05:52 PM UTC
All affected customers have been successfully migrated to an alternate provider. Claude Opus requests have stabilized as of 10:00 AM PST. We are continuing to monitor performance closely to ensure ongoing stability.
Notice September 3, 2026 Elevated AWS STS errors 1h 56m Login
Started Sep 03, 2026, 09:44 PM UTC· resolved Sep 03, 2026, 11:40 PM UTC
- 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.
- 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.
- resolved Sep 03, 2026, 11:40 PM UTC
Services have recovered, and we are continuing to monitor system stability.
Critical September 1, 2026 We are investigating an issue impacting Chat/Assistant 3h 4m Chat
Started Sep 01, 2026, 03:49 AM UTC· resolved Sep 01, 2026, 06:54 AM UTC
- 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.
- 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.
Notice August 31, 2026 Service degradation from Azure OpenAI causing failed assistant errors 2h 57m Chat, Other
Started Aug 31, 2026, 09:16 AM UTC· resolved Aug 31, 2026, 12:13 PM UTC
- 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.
- 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)
- 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.
Critical August 24, 2026 Chat instability caused by hitting OpenAI capacity 1h 38m Chat
Started Aug 24, 2026, 04:23 PM UTC· resolved Aug 24, 2026, 06:01 PM UTC
- 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.
- 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
Major July 16, 2026 Chat/Assistant errors due to AzureOpenAI outage 24m Chat
Started Jul 16, 2026, 09:11 AM UTC· resolved Jul 16, 2026, 09:35 AM UTC
- resolved Jul 16, 2026, 09:35 AM UTC
Between 09:08 UTC on 16 Jul 2026 and 11:43 UTC on 16 Jul 2026, Azure experienced a platform issue affecting the Azure OpenAI Service service in the East US 2 region. During this incident, some customers experienced service interruptions with resources hosted in the region.
- resolved Sep 08, 2026, 11:21 PM UTC
Between 09:08 UTC on 16 Jul 2026 and 11:43 UTC on 16 Jul 2026, Azure experienced a platform issue affecting the Azure OpenAI Service service in the East US 2 region. During this incident, some customers experienced service interruptions with resources hosted in the region.
Major July 15, 2026 Elevated chat errors on AWS Bedrock customers 5m Chat
Started Jul 15, 2026, 06:59 AM UTC· resolved Jul 15, 2026, 07:05 AM UTC
- resolved 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.
- resolved Sep 02, 2026, 04:39 PM 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.
Notice July 10, 2026 Extension actions failing during auth and execution in Chat and Agents 2d 20h Chat, Other, Agents
Started Jul 10, 2026, 05:02 PM UTC· resolved Jul 13, 2026, 01:40 PM UTC
- resolved Jul 10, 2026, 05:16 PM UTC
Some users were 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. Our engineering team has deployed fixes to affected environments.
- 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.
- 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.
- resolved Jul 13, 2026, 01:40 PM UTC
A fix for the issue affecting extension actions has been deployed and is now resolved for nearly all customers. We're reaching out directly to the small number of remaining customers who need to complete a few steps on their end. If you had already authenticated to some of the Extension tools between 9th July 2026 and 13th July 2026 PST, then you will be requested to authenticate to those tools again.
Critical July 10, 2026 Glean Assitant Errors 3h 54m Chat
Started Jul 10, 2026, 02:00 AM UTC· resolved Jul 10, 2026, 05:55 AM UTC
- 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.
- monitoring Jul 10, 2026, 04:26 AM UTC
We have disabled the change and confirmed that user experience has returned to normal.
- 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.
Critical July 3, 2026 Client Token management API is failing 6h 25m Rest API
Started Jul 03, 2026, 08:36 AM UTC· resolved Jul 03, 2026, 03:02 PM UTC
- 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.
- identified Jul 03, 2026, 09:31 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.
- 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.
- monitoring Jul 03, 2026, 02:20 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.
- 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.
- 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.
Notice May 18, 2026 Elevated Google Vertex AI rate limit error on Claude Opus 4.6 model 7h 4m Chat, Agents
Started May 18, 2026, 09:00 AM UTC· resolved May 18, 2026, 04:04 PM UTC
- 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.
- 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.
Critical May 8, 2026 Search requests timeout in AWS instances 3d 4h Search
Started May 08, 2026, 12:11 AM UTC· resolved May 11, 2026, 05:07 AM UTC
- 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
- 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.
Notice May 7, 2026 Glean AWS customers might experience intermittent server errors 2h 41m
Started May 07, 2026, 09:05 AM UTC· resolved May 07, 2026, 11:46 AM UTC
- 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 .
- 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.
Notice April 23, 2026 Degraded auth experience while connecting to certain data sources 39m Glean service, Chat, Agents, Search
Started Apr 23, 2026, 04:29 PM UTC· resolved Apr 23, 2026, 05:09 PM UTC
- investigating Apr 23, 2026, 04:52 PM UTC
Customers may experience auth issues while connecting to a certain data sources for chat, search and actions. We’re sorry for the disruption and appreciate your patience while we investigate.
- monitoring Apr 23, 2026, 04:55 PM UTC
We have deployed a fix for the issue affecting OAuth. We are keeping the systems under heightened monitoring to ensure they remain stable.
- resolved Apr 23, 2026, 05:09 PM UTC
The incident has been resolved. We apologize for the disruption and appreciate your patience while we addressed this issue.
Critical April 22, 2026 Permanent Fix Deployed 14h 19m Glean service, Chat, Agents
Started Apr 22, 2026, 04:24 PM UTC· resolved Apr 23, 2026, 06:43 AM UTC
- investigating Apr 22, 2026, 04:30 PM UTC
Customers may experience chat failures. Our engineering team is actively working to identify the root cause. We’re sorry for the disruption and appreciate your patience while we investigate.
- identified Apr 22, 2026, 04:35 PM UTC
We are rolling out a mitigation for the issue affecting chat and agents for customers using Glean key for LLMs. We will continue to closely monitor system behavior as the mitigation completes.
- monitoring Apr 22, 2026, 05:02 PM UTC
We have deployed a fix for the issue, and early signals show performance has stabilized. We are keeping the systems under heightened monitoring to ensure they remain stable. Impact: Most users should now see [normal behavior / significantly improved performance]. If you continue to experience issues, please contact Glean support.
- resolved Apr 23, 2026, 06:43 AM UTC
We have rolled out a permanent fix to this issue
Notice April 13, 2026 Incident resolved 1d Glean service, Chat
Started Apr 13, 2026, 04:48 PM UTC· resolved Apr 14, 2026, 05:19 PM UTC
- monitoring Apr 13, 2026, 07:17 PM UTC
We continue to be partially impacted by OpenAI's ongoing authentication errors (https://status.openai.com/incidents/qyc50x3t).
- monitoring Apr 13, 2026, 11:35 PM UTC
No change in partial impact from OpenAI's ongoing authentication errors (https://status.openai.com/incidents/qyc50x3t).
- monitoring Apr 13, 2026, 11:35 PM UTC
No change in partial impact from OpenAI's ongoing authentication errors: https://status.openai.com/incidents/qyc50x3t
- monitoring Apr 14, 2026, 02:59 AM UTC
OpenAI reports issue has been mitigated and are monitoring the recovery.
- resolved Apr 14, 2026, 05:11 PM UTC
OpenAI auth errors have resolved
- 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.
Notice April 6, 2026 Chat failing in multiple deployments 1h 36m Glean service, Chat
Started Apr 06, 2026, 07:01 PM UTC· resolved Apr 06, 2026, 08:37 PM UTC
- investigating Apr 06, 2026, 07:10 PM UTC
We are currently investigating reports of chat failures from multiple deployments. We believe there may be an issue with GCP Vertex AI, and we are currently troubleshooting.
- identified Apr 06, 2026, 08:20 PM UTC
We have identified the cause, and we are rolling out a fix.
- resolved Apr 06, 2026, 08:37 PM UTC
We finished rolling out the fix.
Notice April 2, 2026 Confluence User Oauth flow broken 15h 25m Glean service
Started Apr 02, 2026, 03:05 PM UTC· resolved Apr 03, 2026, 06:31 AM UTC
- identified Apr 02, 2026, 03:11 PM UTC
Confluence's user OAuth flow is broken. A fix is underway.
- monitoring Apr 02, 2026, 03:26 PM UTC
The fix is in place and the issue is resolved. We’re monitoring it.
- resolved Apr 03, 2026, 06:31 AM UTC
The issue is resolved.
Major March 25, 2026 Atlassian token request rate limiting 58m Glean service
Started Mar 25, 2026, 06:40 AM UTC· resolved Mar 25, 2026, 07:39 AM UTC
- 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.
- resolved Jul 14, 2026, 07:33 PM 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.
Critical March 9, 2026 Search and Chat failures 4h 54m Glean service, Chat, Search
Started Mar 09, 2026, 11:40 AM UTC· resolved Mar 09, 2026, 04:34 PM UTC
- monitoring Mar 09, 2026, 02:42 PM UTC
Google has confirmed multiple GCP products are affected in us-central1. Multiple cloud services impacted
- 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
Critical March 4, 2026 Users facing login issues 6h 42m Glean service, Login
Started Mar 04, 2026, 02:24 AM UTC· resolved Mar 04, 2026, 09:07 AM UTC
- identified Mar 04, 2026, 02:51 AM UTC
Actively working on mitigation.
- identified Mar 04, 2026, 04:43 AM UTC
We have the fix ready, we are actively working on rolling out the fix
- resolved Mar 04, 2026, 09:07 AM UTC
Fix has been rolled out successfully and users are no longer facing login issues
Notice February 27, 2026 gemini-models-429-errors 17h 44m Glean service
Started Feb 27, 2026, 02:17 PM UTC· resolved Feb 28, 2026, 08:02 AM UTC
- investigating Feb 27, 2026, 02:19 PM UTC
Gemini models running into 429s across the customers regardless of Glean Key or Customer Key.
- identified Feb 27, 2026, 03:09 PM UTC
We opened a case with Google. They said an internal error is causing 429 errors, and the product team is fixing it.
- monitoring Feb 27, 2026, 04:20 PM UTC
GCP confirmed that the issue is resolved. Please refer - https://status.cloud.google.com/incidents/41E5S3mkTGDfkZuJZH5k
- resolved Feb 28, 2026, 08:02 AM UTC
Google confirms the issue is fixed.
Major February 18, 2026 Chat file download unavailable 6h 38m Glean service, Chat
Started Feb 18, 2026, 08:50 PM UTC· resolved Feb 19, 2026, 03:28 AM UTC
- identified Feb 18, 2026, 09:13 PM UTC
We have identified an issue causing images generated by Chat to fail to display for some customers. Core Search, Chat, and Agent experiences remain otherwise fully available. Our engineering team has implemented a fix and is rolling it out across affected environments. We will provide another update once the rollout is complete or if we observe any change in impact.
- resolved Feb 19, 2026, 03:28 AM UTC
The issue has now been verified fixed.