- Detected by Pingoru
- May 22, 2026, 04:08 AM UTC
- Resolved
- May 22, 2026, 05:25 AM UTC
- Duration
- 1h 16m
Affected: Gladly Team Solution
Timeline · 3 updates
-
investigating May 22, 2026, 04:45 AM UTC
We are investigating reports of issues loading Gladly conversations from the APAC region. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified May 22, 2026, 05:02 AM UTC
We are seeing sustained recovery with ability to load conversations from the APAC region. We will continue to monitor. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
resolved May 22, 2026, 05:25 AM UTC
We have confirmed that Gladly has recovered, and agents accessing Gladly from APAC regions should no longer be seeing latency issues. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
Read the full incident report →
- Detected by Pingoru
- May 20, 2026, 07:31 PM UTC
- Resolved
- May 20, 2026, 09:27 PM UTC
- Duration
- 1h 55m
Affected: Gladly AI Solution
Timeline · 3 updates
-
identified May 20, 2026, 07:53 PM UTC
Starting 12:31 PM PT, we identified issues causing elevated handoffs for Gladly AI conversations. We are working on a fix and will update the Status Page with next steps as soon as possible. Please contact Gladly Support should you have any questions.
-
monitoring May 20, 2026, 07:57 PM UTC
We deployed a fix for this issue at 12:52 PM PT, and have observed recovery. We will continue to monitor prior to resolving the Status Page. Please contact Gladly Support should you have any questions.
-
resolved May 20, 2026, 09:27 PM UTC
After actively monitoring system performance, we are happy to report that this issue is now resolved and Gladly AI is fully operational. We will distribute a thorough Root Cause Analysis (RCA) for this incident via email as soon as possible. The RCA will contain details on root cause, incident timeline, recovery steps, and remediation steps. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 01:24 AM UTC
- Resolved
- May 08, 2026, 03:19 AM UTC
- Duration
- 1h 55m
Affected: ReportingRouting, Prioritization and Workflow
Timeline · 4 updates
-
investigating May 08, 2026, 01:24 AM UTC
We are investigating reports of intermittent latency in liveboards and conversation-to-agent routing within a subset of Gladly organizations. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified May 08, 2026, 01:30 AM UTC
We have identified the root cause of this issue and are working on deploying a fix as soon as possible. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
monitoring May 08, 2026, 01:54 AM UTC
After deploying our fix, we are seeing recovery in both liveboards and routing latency. We will continue to monitor prior to resolving this status page. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
resolved May 08, 2026, 03:19 AM UTC
After actively monitoring system performance, we are happy to report that this issue is now resolved and Gladly is fully operational. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
Read the full incident report →
- Detected by Pingoru
- Apr 02, 2026, 06:24 AM UTC
- Resolved
- Apr 02, 2026, 05:43 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 02, 2026, 06:24 AM UTC
Between 10:43 PM - 10:52 PM PT on 04/01/2026, Agents who refreshed their pages or attempted to login to Gladly were unable to do so. Gladly has issued a hotfix for this, and is operating as expected again. Please contact Gladly Support if you have any further questions.
Read the full incident report →
- Detected by Pingoru
- Jan 27, 2026, 07:06 PM UTC
- Resolved
- Jan 28, 2026, 03:58 AM UTC
- Duration
- 8h 51m
Affected: Gladly Structured Threads Solution (Legacy)
Timeline · 4 updates
-
investigating Jan 27, 2026, 07:06 PM UTC
We're actively investigating a sudden increase of unexpected handoffs for customers on (V1) Structured Threads. Please note that this is not affecting Guides.
-
monitoring Jan 27, 2026, 07:41 PM UTC
Handoff behavior has normalized. Our engineering team is performing a root cause analysis to understand the recent fluctuations and prevent recurrence.
-
monitoring Jan 28, 2026, 03:57 AM UTC
Following a period of stable performance monitoring, we have confirmed the issue is fully resolved. Our engineering team is now conducting a post-mortem analysis to implement long-term preventative measures.
-
resolved Jan 28, 2026, 03:58 AM UTC
This incident has been resolved.
Read the full incident report →
Critical January 22, 2026 - Detected by Pingoru
- Jan 22, 2026, 07:51 AM UTC
- Resolved
- Jan 22, 2026, 08:17 AM UTC
- Duration
- 26m
Affected: Gladly Team SolutionGladly Structured Threads Solution (Legacy)
Timeline · 4 updates
-
investigating Jan 22, 2026, 07:51 AM UTC
Gladly is investigating a login issue. We are continuing to work on a resolution, and will continue updating this page every 30 minutes or sooner. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified Jan 22, 2026, 08:14 AM UTC
We have identified the issue, and are working as expediently as possible to resolve it. We will continue to update this Status Page every 30 minutes or sooner until resolved. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
monitoring Jan 22, 2026, 08:14 AM UTC
A fix has been deployed for this issue, and we will continue to monitor. We will post a final update when fully resolved. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
resolved Jan 22, 2026, 08:17 AM UTC
After actively monitoring system performance, we are happy to report that this issue is now resolved and Gladly is fully operational. We will distribute a thorough Root Cause Analysis (RCA) for this incident via email as soon as possible. The RCA will contain details on root cause, incident timeline, recovery steps, and remediation steps. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
Read the full incident report →
- Detected by Pingoru
- Jan 17, 2026, 07:43 PM UTC
- Resolved
- Jan 17, 2026, 07:55 PM UTC
- Duration
- 12m
Affected: Gladly Team Solution
Timeline · 2 updates
-
identified Jan 17, 2026, 07:43 PM UTC
We have identified the issue, and are working as expediently as possible to resolve it. We will continue to update this Status Page every 30 minutes or sooner until resolved. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
resolved Jan 17, 2026, 07:55 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 08, 2026, 05:40 PM UTC
- Resolved
- Jan 08, 2026, 06:02 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 08, 2026, 05:40 PM UTC
Between 10:02 PM PT to 10:13 PM PT, Agents who refreshed Gladly were logged out of the platform and unable to log back in. A fix was rolled out at 10:13 PM PT, which resolved this incident. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
Read the full incident report →
- Detected by Pingoru
- Dec 19, 2025, 04:59 PM UTC
- Resolved
- Dec 19, 2025, 06:04 PM UTC
- Duration
- 1h 4m
Affected: Gladly Team Solution
Timeline · 4 updates
-
investigating Dec 19, 2025, 04:59 PM UTC
Gladly is investigating intermittent latency. We are continuing to work on a resolution, and will continue updating this page every 30 minutes or sooner. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified Dec 19, 2025, 05:18 PM UTC
We have identified the issue, and are deploying a fix. We will continue to update this Status Page every 30 minutes or sooner until resolved. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
monitoring Dec 19, 2025, 05:43 PM UTC
A fix has been deployed for this issue, and we will continue to monitor. We will post a final update when fully resolved. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
resolved Dec 19, 2025, 06:04 PM UTC
After actively monitoring system performance, we are happy to report that this issue is now resolved and Gladly is fully operational. We will distribute a thorough Root Cause Analysis (RCA) for this incident via email as soon as possible. The RCA will contain details on root cause, incident timeline, recovery steps, and remediation steps. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 02:16 PM UTC
- Resolved
- Oct 20, 2025, 10:01 PM UTC
- Duration
- 7h 44m
Affected: Gladly Team SolutionChannel - Chat (Glad App)Channel - VoiceReporting
Timeline · 16 updates
Read the full incident report →
- Detected by Pingoru
- Oct 09, 2025, 01:24 PM UTC
- Resolved
- Oct 09, 2025, 11:35 PM UTC
- Duration
- 10h 10m
Affected: Reporting
Timeline · 8 updates
-
identified Oct 09, 2025, 01:24 PM UTC
We are investigating reports of the "Shared" category in the Reports page missing for Team Manager and Administrator users for Gladly customers who use Insight Builder. Agent-only roles are also currently unable to see the "Language" filter in the Answers Panel. Please contact gladly support should you have any questions.
-
identified Oct 09, 2025, 02:41 PM UTC
We have identified the cause for the missing 'Shared' reports category in the Insight Builder and are currently working on a hotfix. Concurrently, we are continuing to investigate why the 'Language' filter is missing for Agent-only users in the Answers Panel.
-
identified Oct 09, 2025, 03:57 PM UTC
A hotfix is in progress to resolve the issue where the 'Shared' category is missing for Insight Builder (IB) customers. Concurrently, we have two issues that are still under investigation: one concerning missing Sidekick Journey data missing, and another regarding the missing 'Language' filter within the Answers Panel. Edit - As of 8:58 AM PT, Sidekick Journeys data has been restored.
-
identified Oct 09, 2025, 05:15 PM UTC
The fix for the 'Shared' category missing for Insight Builder users is being released to the staging environment for additional testing. The issue causing the 'Language' filter to be missing in the Answers Panel for Agent-only roles remains under investigation.
-
identified Oct 09, 2025, 06:22 PM UTC
The fix for the ‘Shared’ category missing for Insight Builder users is released to the staging environment and is actively being tested. The issue causing the ‘Language’ filter to be missing in the Answers Panel for Agent-only roles remains under investigation.
-
identified Oct 09, 2025, 07:30 PM UTC
The fix for the ‘Shared’ category missing for Insight Builder users is released to the staging environment and is actively being tested. The issue causing the ‘Language’ filter to be missing in the Answers Panel for Agent-only roles has been identified and a fix is currently in the works. We're aiming to release the fix for both issues at the same time.
-
monitoring Oct 09, 2025, 09:35 PM UTC
The fixes for both the missing 'Shared' reports category and the Language filter visibility in the Answers Panel have been released. You'll be asked to reload Gladly to apply the fix. Avoid reloading Gladly while on a live Contact (e.g., phone call) with a customer. Please contact gladly support should you have any questions or observe new issues.
-
resolved Oct 09, 2025, 11:35 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2025, 12:39 AM UTC
- Resolved
- Sep 25, 2025, 01:12 AM UTC
- Duration
- 33m
Affected: Reporting
Timeline · 2 updates
-
identified Sep 25, 2025, 12:39 AM UTC
We have an identified an issue causing elevated data latency beginning ~4:09 PM PT today on Gladly Reports and Gladly Insight Builder. This issue does not affect the Events API, Webhooks, Liveboards or AWS EventBridge, which continue to function as expected. Please contact gladly support should you have any questions.
-
resolved Sep 25, 2025, 01:12 AM UTC
Our technology partner has deployed a fix for this issue. Gladly Reports and Insight Builders should be operating as expected again as of 6:09 PM PT. Please contact gladly support should you have any questions.
Read the full incident report →
- Detected by Pingoru
- Aug 21, 2025, 05:43 PM UTC
- Resolved
- Aug 21, 2025, 07:59 PM UTC
- Duration
- 2h 16m
Affected: Gladly Team Solution
Timeline · 7 updates
-
investigating Aug 21, 2025, 05:35 PM UTC
We’re investigating an issue preventing users from accessing Gladly.
-
investigating Aug 21, 2025, 05:43 PM UTC
We are continuing to work on a resolution for the login issue We will continue to post updates to the Statuspage every 30 minutes until the issue is resolved. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
investigating Aug 21, 2025, 06:08 PM UTC
We continue to work on a resolution for the Agent login issue, and will post updates every 30 minutes until the issue is resolved. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified Aug 21, 2025, 06:24 PM UTC
We have begun to see intermittent availability for Agents to log in due to a recent fix, and are continuing to prioritize all resources into full recovery. We continue to partner with Cloudflare on their ongoing issues, which we are seeing affect behavior. We are working as expediently as possible to resolve this and will continue updating the Status Page every 30 minutes or sooner. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified Aug 21, 2025, 06:41 PM UTC
One of our partners – Cloudflare – is having a major incident with their network configurations that has caused these issues. You can read more on their Status Page here: https://www.cloudflarestatus.com/incidents/d9n3g1vnxdd2 We continue to work closely with them on a resolution, and will update you as soon as possible here. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
monitoring Aug 21, 2025, 07:03 PM UTC
As of 11:55 AM PT, we have deployed network configuration fixes to circumvent the Cloudflare issues, which has restored service. As Agents log back in, we recommend they clear their cache and cookies. We will continue to monitor the system and provide a final update. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
resolved Aug 21, 2025, 07:59 PM UTC
Our monitoring has confirmed that Gladly is stable and fully performant. We will distribute a thorough root cause analysis (RCA) for this incident via email as soon as possible. The RCA will contain details on root cause, incident timeline, recovery steps, and remediation steps. Please contact Gladly Support should you have any questions.
Read the full incident report →
- Detected by Pingoru
- Aug 07, 2025, 02:18 PM UTC
- Resolved
- Aug 07, 2025, 03:01 PM UTC
- Duration
- 43m
Affected: Gladly Structured Threads Solution (Legacy)
Timeline · 2 updates
-
identified Aug 07, 2025, 02:18 PM UTC
We've identified an issue that's preventing the Journeys page from loading Sidekick data and a fix will be rolled out in the next hour. Please note that this is not affecting Sidekick interactions with customers.
-
resolved Aug 07, 2025, 03:01 PM UTC
After actively monitoring system performance, we are happy to report that this issue is now resolved and Gladly is fully operational. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
Read the full incident report →
- Detected by Pingoru
- Jul 31, 2025, 05:57 AM UTC
- Resolved
- Jul 31, 2025, 06:57 AM UTC
- Duration
- 59m
Affected: Gladly Team Solution
Timeline · 4 updates
-
investigating Jul 31, 2025, 05:57 AM UTC
We are currently investigating intermittent reports with Gladly access in certain regions. Please contact gladly support should you have any questions.
-
identified Jul 31, 2025, 06:10 AM UTC
We have identified a potential fix and are working on deploying it. Please contact gladly support should you have any questions.
-
monitoring Jul 31, 2025, 06:42 AM UTC
We have deployed and tested the fix for this issue. Note that Agents may need to log out, then log back into Gladly if they are still experiencing issues with Conversations loading. Please contact gladly support should you have any questions.
-
resolved Jul 31, 2025, 06:57 AM UTC
We have confirmed that the fix deployed has addressed this issue. We will be sending an RCA to those affected as soon as possible. Please contact gladly support should you have any questions.
Read the full incident report →
- Detected by Pingoru
- Jul 16, 2025, 02:19 PM UTC
- Resolved
- Jul 16, 2025, 03:44 PM UTC
- Duration
- 1h 25m
Affected: Gladly Structured Threads Solution (Legacy)
Timeline · 4 updates
-
identified Jul 16, 2025, 02:19 PM UTC
We have identified an issue causing some customers' Gladly Sidekick Generative AI-powered conversations to hand off prematurely. We are working on a fix and expect to deploy and validate shortly. We will continue to keep the Status Page updated every 30 minutes. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
monitoring Jul 16, 2025, 02:27 PM UTC
A fix has been deployed, and we are seeing recovery for those affected. We will continue to monitor. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified Jul 16, 2025, 03:00 PM UTC
Gladly Sidekick Generative AI-powered conversations continue to resolve and handoff as expected. In addition, we are working on a fix that may prevent some customers from editing Sidekick Guides and will update the Status Page every 30 minutes or as soon as it is released. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
resolved Jul 16, 2025, 03:44 PM UTC
Gladly Sidekick Generative AI-powered conversations continue to resolve and handoff as expected. In addition, we have deployed and verified the UI fix preventing modifications to Guides. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
Read the full incident report →
- Detected by Pingoru
- Jun 27, 2025, 06:51 PM UTC
- Resolved
- Jun 27, 2025, 07:19 PM UTC
- Duration
- 27m
Affected: Gladly Structured Threads Solution (Legacy)
Timeline · 4 updates
-
identified Jun 27, 2025, 06:51 PM UTC
We are investigating reports of Sidekick issues affecting ability to run and load Guides powered by Generative AI. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified Jun 27, 2025, 07:01 PM UTC
We have identified a fix, and are working on validating it. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
monitoring Jun 27, 2025, 07:11 PM UTC
We have deployed a fix and are seeing recovery. We will continue to closely monitor over the next hour. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
resolved Jun 27, 2025, 07:19 PM UTC
We have confirmed that Sidekick performance has recovered. We will continue to closely monitor over the next hour. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 07:49 PM UTC
- Resolved
- Jun 12, 2025, 11:05 PM UTC
- Duration
- 3h 15m
Timeline · 3 updates
-
monitoring Jun 12, 2025, 07:49 PM UTC
We are monitoring an incident within Google Cloud Services - one of Gladly's platform partners. At this time, the incident is not affecting the Gladly Production ecosystem - Gladly Sidekick and Gladly Hero continue to function as expected. We will continue to keep the Status Page updated should any changes occur. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
monitoring Jun 12, 2025, 08:50 PM UTC
Gladly continues to see no issues in Production as a result of this incident. We are continuing to actively monitor our metrics and performance. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
resolved Jun 12, 2025, 11:05 PM UTC
Gladly continues to see no issues in Production as a result of this incident. In addition, we have been notified that most Google Cloud products have fully recovered as of 1:45 PM PT. We will resolve this Status Page, and are continuing to actively monitor our metrics and performance. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2025, 04:54 PM UTC
- Resolved
- Jun 05, 2025, 08:50 PM UTC
- Duration
- 3h 55m
Affected: Channel - SMS
Timeline · 6 updates
-
investigating Jun 05, 2025, 04:54 PM UTC
Gladly is investigating an SMS filtering issue with Twilio, our Telephony Partner. We are working as expediently as possible to resolve this and will continue updating the Status Page every 30 minutes. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified Jun 05, 2025, 05:07 PM UTC
Gladly has identified an issue with false positives on SMS filtering with Verizon Wireless numbers. Agents might see messages that should normally send instead fail. This is due to an incident with Twilio. You can read more on their status page here: https://status.twilio.com/incidents/8hh1zhb324h6 We are working as expediently as possible to resolve this and will continue updating the Status Page every 30 minutes. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified Jun 05, 2025, 05:51 PM UTC
We continue to work with our Telephony Partner on the outbound SMS filtering issues. We will update this page in 60 minutes or sooner with updates. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified Jun 05, 2025, 07:01 PM UTC
We continue to work closely with Twilio on the intermittent SMS failures to the Verizon network. We will be in touch as soon as we have an update! Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
monitoring Jun 05, 2025, 07:58 PM UTC
Twilio has deployed a fix, and we are observing recovery. We will continue to monitor the system and provide updates if necessary. We'll send our final update on this issue once we conclude our monitoring and confirm the issue is resolved. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
resolved Jun 05, 2025, 08:50 PM UTC
After actively monitoring system performance, we are happy to report that this issue is now resolved and Gladly is fully operational. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
Read the full incident report →
- Detected by Pingoru
- May 14, 2025, 07:36 PM UTC
- Resolved
- May 14, 2025, 10:30 PM UTC
- Duration
- 2h 54m
Affected: Channel - Email
Timeline · 6 updates
-
investigating May 14, 2025, 07:36 PM UTC
Gladly is investigating an issue with one of our email partners where outbound emails are stuck in sending. We are working as expediently as possible to resolve this and will continue updating the Status Page every 30 minutes. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified May 14, 2025, 07:57 PM UTC
Gladly has identified an intermittent issue with outbound Email delivery, due to an issue with our Email Partner's configurations. We are working as expediently as possible to resolve this and will continue updating the Status Page every 30 minutes. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified May 14, 2025, 08:28 PM UTC
We continue to work with our partner on the intermittent outbound email issues. We will continue updating the Status Page every 30 minutes. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified May 14, 2025, 09:03 PM UTC
Thank you for your patience as we continue to work with our Email partner while they update their platform. We will continue to update every hour or sooner. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
monitoring May 14, 2025, 09:47 PM UTC
Our partner has deployed a fix for this issue. We will continue to monitor the system and provide updates if necessary. We'll send our final update on this issue once we conclude our monitoring and confirm the issue is resolved. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
resolved May 14, 2025, 10:30 PM UTC
After actively monitoring system performance, we are happy to report that this issue is now resolved and Gladly is fully operational. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2025, 03:52 PM UTC
- Resolved
- Mar 31, 2025, 05:30 PM UTC
- Duration
- 1h 37m
Affected: Channel - Voice
Timeline · 6 updates
-
investigating Mar 31, 2025, 03:52 PM UTC
Gladly has identified an issue with intermittent inbound Voice calls disconnecting. We are working as expediently as possible to resolve this and will continue updating the Status Page every 30 minutes. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified Mar 31, 2025, 04:19 PM UTC
Gladly has identified an issue with our telephony partner, and are working closely with them to resolve the issues with inbound calls. We will continue updating the Status Page every 30 minutes. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified Mar 31, 2025, 04:40 PM UTC
Our telephony partner has identified the issue and is implementing a fix. We are working as expediently as possible to resolve this and will continue updating the Status Page every 30 minutes. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified Mar 31, 2025, 05:02 PM UTC
Our telephony partner has applied a remediation while continuing to investigate the root cause. We have not seen issues in the past 15 minutes, and will continue to monitor closely. We'll be back with another update in 30 minutes or less. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
monitoring Mar 31, 2025, 05:17 PM UTC
We have confirmed we have not seen issues in the past 30 minutes, and will continue to monitor. We'll send a final update once we conclude monitoring and confirm the issue is fully resolved. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
resolved Mar 31, 2025, 05:30 PM UTC
After actively monitoring system performance, we are happy to report that this issue is now resolved and Gladly is fully operational. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2025, 02:30 PM UTC
- Resolved
- Mar 19, 2025, 09:59 PM UTC
- Duration
- 7h 28m
Affected: Reporting
Timeline · 14 updates
Read the full incident report →
- Detected by Pingoru
- Dec 12, 2024, 12:17 AM UTC
- Resolved
- Dec 12, 2024, 03:59 AM UTC
- Duration
- 3h 41m
Affected: Gladly Structured Threads Solution (Legacy)
Timeline · 5 updates
-
investigating Dec 12, 2024, 12:17 AM UTC
Gladly is investigating an issue regarding Sidekick handoff issues due to an issue at OpenAI. We are working as expediently as possible to resolve this and will continue updating the Status Page every 30 minutes. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified Dec 12, 2024, 12:32 AM UTC
Gladly has identified the issue on the OpenAI side, and confirmed they are working on a fix. Additionally, we are working to ensure a smooth transition with our backup systems in place. We are working with our partner as expediently as possible to resolve this and will continue updating the Status Page every 30 minutes. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
monitoring Dec 12, 2024, 12:58 AM UTC
OpenAI has deployed a fix for this issue, and are seeing recovery. We will continue to monitor the system and provide updates if necessary. We'll send our final update on this issue once we conclude our monitoring and confirm the issue is resolved. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
monitoring Dec 12, 2024, 01:40 AM UTC
We have implemented an additional fix while OpenAI's status is pending. All Gladly customers should see recovery separately. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
resolved Dec 12, 2024, 03:59 AM UTC
After actively monitoring system performance, we are happy to report that this issue is now resolved. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
Read the full incident report →
- Detected by Pingoru
- Nov 26, 2024, 02:01 PM UTC
- Resolved
- Nov 26, 2024, 05:32 PM UTC
- Duration
- 3h 31m
Affected: Channel - Chat (Glad App)
Timeline · 4 updates
-
identified Nov 26, 2024, 04:08 PM UTC
Gladly is continuing to investigate a fix for intermittent issues with delivery status updates: messages are sending to consumers as expected, though delivery statuses may appear delayed on the timeline. We have found that having Agents restart their computer may help to mitigate the issue. We will continue to update the Status Page every 30 minutes. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
identified Nov 26, 2024, 04:42 PM UTC
We are implementing a fix, and will continue to work as expediently as possible to resolve this. We will continue updating the Status Page every 30 minutes. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
monitoring Nov 26, 2024, 05:10 PM UTC
A fix has been deployed for this issue. We will continue to monitor the system and provide updates if necessary. We'll send our final update on this issue once we conclude our monitoring and confirm the issue is resolved. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
resolved Nov 26, 2024, 05:33 PM UTC
After actively monitoring system performance, we are happy to report that this issue is now resolved and Gladly is fully operational. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
Read the full incident report →
Notice September 25, 2024 - Detected by Pingoru
- Sep 25, 2024, 02:58 PM UTC
- Resolved
- Sep 25, 2024, 04:05 PM UTC
- Duration
- 1h 7m
Affected: Channel - VoiceLogin
Timeline · 4 updates
-
investigating Sep 25, 2024, 03:17 PM UTC
Gladly is investigating an issue with Gladly voice and Agents being logged out. We are working as expediently as possible to resolve this and will continue updating the Status Page every 30 minutes. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
monitoring Sep 25, 2024, 03:31 PM UTC
A fix has been deployed for this issue and we are seeing the system stabilize. We will continue to monitor the system and provide updates if necessary. We'll send our final update on this issue once we conclude our monitoring and confirm the issue is resolved. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
monitoring Sep 25, 2024, 03:45 PM UTC
Between 7:58 AM and 8:00 AM PT Agents may have experienced a "Try Again" disconnection error when logged into Gladly. This was resolved at 8:00 AM PT, and we are continuing to monitor. We'll send our final update on this issue once we conclude our monitoring and confirm the issue is resolved. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
-
resolved Sep 25, 2024, 04:28 PM UTC
After actively monitoring system performance, we are happy to report that this issue is now resolved and Gladly is fully operational. Stuck calls, should have automatically ended after 1-hour, however, you can also send Gladly Support the links to the calls for us to manually end them if you are experiencing any prevailing issues. Any SMS(es) that failed during this time will also be re-sent. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.
Read the full incident report →