Gladly Outage History

Started Nov 05, 2026, 08:56 PM UTC· resolved Nov 05, 2026, 09:13 PM UTC

1. investigating Nov 05, 2026, 08:56 PM UTC

   Gladly is investigating voice functionality issues. 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.

2. investigating Nov 05, 2026, 09:00 PM UTC

   We are continuing to investigate this issue.

3. resolved Nov 05, 2026, 09:13 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 →

Started Nov 02, 2026, 07:15 PM UTC· resolved Nov 02, 2026, 10:21 PM UTC

1. monitoring Nov 02, 2026, 07:15 PM UTC

   We have resolved an issue causing intermittent routing and profile latency between ~10:45 AM PT - 11:00 AM PT. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.

2. monitoring Nov 02, 2026, 07:58 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.

3. monitoring Nov 02, 2026, 08:12 PM UTC

   A fix was deployed for this issue at ~11:00 AM PT, and we will continue to monitor. We recommend agents clear their cache and cookies before logging back into Gladly. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.

4. resolved Nov 02, 2026, 10:21 PM UTC

   We have confirmed that the fix in place has resolved this issue. 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 →

Started Oct 23, 2026, 03:43 PM UTC· resolved Oct 23, 2026, 04:53 PM UTC

1. investigating Oct 23, 2026, 03:43 PM UTC

   We are investigating reports of intermittent issues with login and routing. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.

2. identified Oct 23, 2026, 04:04 PM UTC

   We have identified potential root cause connected to Cloudflare. We are investigating mitigation options and will post here every 30 minutes or when an update is available - whichever comes first. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.

3. monitoring Oct 23, 2026, 04:23 PM UTC

   We have implemented a fix for this issue and are monitoring. Agents may need to clear their cache and cookies before logging back in. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.

4. resolved Oct 23, 2026, 04:53 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 →

Started Oct 19, 2026, 06:29 PM UTC· resolved Oct 19, 2026, 09:37 PM UTC

1. identified Oct 19, 2026, 06:29 PM UTC

   We are investigating issues with Gladly Insights Agent causing conversational report building / querying to return errors. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.

2. monitoring Oct 19, 2026, 06:48 PM UTC

   We have identified root cause and have deployed a fix that we are monitoring. Customers should now be able to access Insights Agent again after exiting, then re-entering it. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.

3. resolved Oct 19, 2026, 09:37 PM UTC

   We have completed our monitoring period, and have confirmed that the fix we implemented has addressed this issue fully. 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 →

Started Sep 24, 2026, 02:45 PM UTC· resolved Sep 24, 2026, 05:44 PM UTC

1. identified Sep 24, 2026, 02:45 PM UTC

   We have identified the issue where Topics panel selections are being blocked by the Answers & Team Assist panel, and we 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.

2. identified Sep 24, 2026, 03:51 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.

3. identified Sep 24, 2026, 04:53 PM UTC

   We're still working on 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.

4. resolved Sep 24, 2026, 05:44 PM UTC

   We have deployed a fix for this issue, and the topics panel is behaving as expected again when utilized with Team Assist. 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 →

Started Sep 10, 2026, 03:08 PM UTC· resolved Sep 11, 2026, 12:30 AM UTC

1. investigating Sep 10, 2026, 03:08 PM UTC

   Gladly is investigating an intermittent issue on querying reports. We are continuing to work on a resolution with the Google team 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.

2. investigating Sep 10, 2026, 03:10 PM UTC

   We are continuing to investigate this issue.

3. identified Sep 10, 2026, 03:45 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.

4. identified Sep 10, 2026, 04:17 PM UTC

   We are continuing to work on a resolution with the Google team 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.

5. investigating Sep 10, 2026, 05:06 PM UTC

   Gladly is investigating Intermittent Report Loading Issues 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.

6. monitoring Sep 10, 2026, 05:10 PM UTC

   As of ~9:45 AM PT, Gladly Team reporting (e.g.: Conversations Export Report, Contact Export, Work Sessions) have been restored. Gladly AI Sessions reporting is currently undergoing maintenance, and we will post back on its status 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.

7. resolved Sep 11, 2026, 12:30 AM UTC

   Our monitoring indicates that issues with Gladly reports remain performant. At this time, 2 reports - Gladly AI Sessions Detail and Gladly AI Sessions Detail with Messages - remain under maintenanace. We will communicate fixes for those reports over release notes. 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 →

Started Sep 09, 2026, 10:19 PM UTC· resolved Sep 10, 2026, 02:45 AM UTC

1. identified Sep 09, 2026, 10:19 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.

2. identified Sep 09, 2026, 10:19 PM UTC

   We are continuing to work on a fix for this issue.

3. identified Sep 09, 2026, 10:20 PM UTC

   We are continuing to work on a fix for this issue.

4. identified Sep 09, 2026, 11:15 PM UTC

   We are continuing to work on a fix for this issue.

5. identified Sep 10, 2026, 12:44 AM UTC

   We have identified a fix for this issue and are working as quickly as possible to deploy it. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.

6. monitoring Sep 10, 2026, 01:25 AM UTC

   A fix has been deployed, and we are monitoring reporting performance. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.

7. resolved Sep 10, 2026, 02:45 AM UTC

   Our post-fix monitoring has indicated 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 →

Started Sep 09, 2026, 12:50 PM UTC· resolved Sep 09, 2026, 02:49 PM UTC

1. investigating Sep 09, 2026, 12:50 PM UTC

   We have identified the issue with the reports UI not loading, 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.

2. investigating Sep 09, 2026, 12:59 PM UTC

   Gladly is investigating a/an where reports page is not loading 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.

3. investigating Sep 09, 2026, 01:00 PM UTC

   We are continuing to investigate this issue.

4. identified Sep 09, 2026, 01:44 PM UTC

   Gladly is investigating where reports page is not loading. We're communicating with our partner team to resolve this. 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.

5. identified Sep 09, 2026, 02:11 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.

6. monitoring Sep 09, 2026, 02:19 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. Our team partnered up with Google to do a refresh on Looker access to fix 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.

7. resolved Sep 09, 2026, 02:49 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. Google support team restarted the instance to fix Looker access. 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 →

Started Aug 31, 2026, 10:55 PM UTC· resolved Sep 01, 2026, 03:42 AM UTC

1. investigating Aug 31, 2026, 10:55 PM UTC

   We're investigating an issue regarding Reports not loading. We are actively investigating 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.

2. identified Aug 31, 2026, 11:30 PM UTC

   We have identified the root cause of this issue and are actively working with our reporting partners to remediate. We 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.

3. identified Sep 01, 2026, 01:28 AM UTC

   We're continuing to work with our reporting partner to remediate this issue. Thank you for your patience. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.

4. identified Sep 01, 2026, 02:00 AM UTC

   We're continuing to work with our reporting partner to remediate this issue. We will continue to update the status page very 120 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.

5. monitoring Sep 01, 2026, 03:06 AM UTC

   The issue affecting report loading has been resolved and we are seeing normal performance across the reporting service. We will continue to monitor closely and will provide a final update once we've confirmed 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. Reporting

6. resolved Sep 01, 2026, 03:42 AM UTC

   We have confirmed that the issue has been resolved. Reports are loading normally, and we have confirmed stable performance across the reporting service. Thank you for your patience while we worked through this. 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 →

Started Aug 01, 2026, 06:06 AM UTC· resolved Aug 01, 2026, 07:00 AM UTC

1. investigating Aug 01, 2026, 06:06 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.

2. monitoring Aug 01, 2026, 06:42 AM UTC

   We deployed a fix for this issue at 11:42 PM PT. Agents are now able to login to Gladly and access as usual. 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.

3. resolved Aug 01, 2026, 07:00 AM UTC

   We have completed our monitoring period and confirmed that the issue is fully mitigated. All services are functioning normally. 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 →

Started Jul 30, 2026, 07:37 PM UTC· resolved Jul 30, 2026, 07:41 PM UTC

1. identified Jul 30, 2026, 07:37 PM UTC

   We have identified an issue on Gladly AI causing elevated handoffs starting ~12:24 PM PT on Chat, Email and SMS. We have determined root cause, and are expecting to deploy a fix imminently. Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.

2. resolved Jul 30, 2026, 07:41 PM UTC

   This has been resolved as of 12:40 PM PT, and Gladly AI is no longer experiencing elevated handoffs on Chat, Email and SMS. 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 →

Started Jun 22, 2026, 01:52 PM UTC· resolved Jun 22, 2026, 04:59 PM UTC

1. investigating Jun 22, 2026, 01:52 PM UTC

   Gladly is investigating an issue that's preventing some users from accessing Gladly Team. 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.

2. investigating Jun 22, 2026, 02:23 PM UTC

   We are continuing to investigate reports of some users being unable to access Gladly, along with general system slowness. We will provide another update within 30 minutes or as soon as we have more information.

3. investigating Jun 22, 2026, 03:03 PM UTC

   Gladly's own systems remain operational. However, an ongoing Cloudflare incident is disrupting some of the communication streams Gladly depends on, which may prevent some users from logging in or result in degraded performance. We are continuing to monitor the situation closely.

4. monitoring Jun 22, 2026, 03:27 PM UTC

   Cloudflare continues to reroute traffic away from affected services. Gladly users who experienced impact are now observing recovery and a return to normal functionality. We will continue to monitor the Cloudflare incident at this time.

5. resolved Jun 22, 2026, 04:59 PM UTC

   After actively monitoring system performance, we are happy to report that the Cloudflare 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 →

Started Jun 02, 2026, 02:52 PM UTC· resolved Jun 02, 2026, 04:21 PM UTC

1. investigating Jun 02, 2026, 02:52 PM UTC

   We're actively investigating reports of Gladly Team not loading. Symptoms include blank white screens, conversations not loading, and agents unable to answer calls.

2. identified Jun 02, 2026, 03:07 PM UTC

   Please advice Gladly Team users to log out of Gladly Team and do a hard refresh of their browser. - Windows: Google Chrome, Microsoft Edge, Press Ctrl + F5 OR Ctrl + Shift + R. - Mac OS: Google Chrome, Edge: Press Cmd + Shift + R.

3. monitoring Jun 02, 2026, 03:25 PM UTC

   We have identified the cause of the loading and connectivity issues reported this morning. Between approximately 9:30 and 11:05 AM ET, a transient network degradation in our cloud infrastructure caused database connections to drop, resulting in errors for agents attempting to load or use the Gladly platform. The issue affected multiple customers simultaneously and was not related to any changes to Gladly's application code. The platform has fully recovered as of 11:05 AM ET. If your agents are still seeing errors, logging out and performing a hard refresh of the browser should resolve any lingering session issues. 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.

4. resolved Jun 02, 2026, 04:21 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 →

Started May 22, 2026, 04:08 AM UTC· resolved May 22, 2026, 05:25 AM UTC

1. investigating May 22, 2026, 04:08 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.

2. identified May 22, 2026, 04:35 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.

3. 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 →

Started May 20, 2026, 07:31 PM UTC· resolved May 20, 2026, 09:27 PM UTC

1. identified May 20, 2026, 07:31 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.

2. monitoring May 20, 2026, 07:52 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.

3. 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. The initial impact was from 12:25-12:52pm PT and secondary one from 2:30-2:40pm PT. 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 →

Started May 08, 2026, 01:24 AM UTC· resolved May 08, 2026, 03:19 AM UTC

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

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

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

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

Started Apr 02, 2026, 05:43 AM UTC· resolved Apr 02, 2026, 05:52 AM UTC

1. resolved Apr 02, 2026, 05:43 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 →

Started Jan 27, 2026, 07:06 PM UTC· resolved Jan 28, 2026, 03:58 AM UTC

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

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

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

4. resolved Jan 28, 2026, 03:58 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 22, 2026, 07:51 AM UTC· resolved Jan 22, 2026, 08:17 AM UTC

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

2. identified Jan 22, 2026, 08:10 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.

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

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

Started Jan 17, 2026, 07:43 PM UTC· resolved Jan 17, 2026, 07:55 PM UTC

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

2. resolved Jan 17, 2026, 07:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 08, 2026, 06:02 AM UTC· resolved Jan 08, 2026, 06:13 AM UTC

1. resolved Jan 08, 2026, 06:02 AM 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 →

Started Dec 19, 2025, 04:59 PM UTC· resolved Dec 19, 2025, 06:04 PM UTC

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

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

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

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

Started Dec 05, 2025, 08:56 AM UTC· resolved Dec 05, 2025, 09:20 AM UTC

1. investigating Dec 05, 2025, 08:56 AM UTC

   Gladly is investigating an issue where users are unable to log into Gladly. 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.

2. identified Dec 05, 2025, 09:00 AM UTC

   We have identified the cause as due to an issue with our partner, Cloudflare. You can read more on their status page here: https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page.

3. monitoring Dec 05, 2025, 09:12 AM UTC

   Cloudflare has deployed a fix 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.

4. resolved Dec 05, 2025, 09:20 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 →

Started Oct 20, 2025, 02:16 PM UTC· resolved Oct 20, 2025, 10:01 PM UTC

1. investigating Oct 20, 2025, 02:16 PM UTC

   We are currently investigating reports of Voice and Reporting errors that are affecting some Gladly customers. Our engineering team is actively working to identify the root cause and restore full functionality as quickly as possible. We will continue to provide updates every 30 minutes as more information becomes available and progress is made toward resolution. If you have any questions or need assistance in the meantime, please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page. We appreciate your patience and understanding as we work to resolve this issue.

2. investigating Oct 20, 2025, 03:00 PM UTC

   We are aware of and actively addressing the Voice and Reporting errors currently impacting some Gladly customers. Our engineering team is working as expediently as possible to identify the cause and implement a resolution. We will continue to update this Status Page every 30 minutes or sooner if new information becomes available until the issue is fully resolved. If you have any questions or require assistance, please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page. Thank you for your patience and understanding as we work diligently to restore full functionality.

3. identified Oct 20, 2025, 03:33 PM UTC

   We are currently aware of and actively investigating Voice and Reporting errors impacting some Gladly customers. Our initial findings indicate that these disruptions are related to the ongoing AWS infrastructure incident affecting multiple services globally. Our engineering teams are closely monitoring both AWS updates while implementing mitigation steps to minimize impact. We are working as expediently as possible to restore full functionality. We will continue to update this Status Page every 30 minutes or sooner if new information becomes available until the issue is fully resolved. If you have any questions or require assistance, Please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page. Thank you for your continued patience and understanding as we work to restore normal operations.

4. identified Oct 20, 2025, 04:03 PM UTC

   We’d like to provide an update on the Voice and Reporting errors currently affecting some Gladly customers. As of October 20, 8:43 AM PDT, AWS has identified the source of the network connectivity issues impacting its services. According to AWS, the root cause is an internal subsystem these issues have caused intermittent disruptions in Voice and Reporting functions for some customers. Our engineering team continues to closely monitor AWS’s recovery efforts and will take all necessary actions to stabilize performance on our end. We will provide the next update within 30 minutes or sooner as new information becomes available. If you have any questions or need assistance, please contact Gladly Support should you have any questions or use this alternative form if you are unable to access the Help page. Thank you for your patience and understanding as we work to ensure full service restoration.

5. identified Oct 20, 2025, 04:30 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.

6. identified Oct 20, 2025, 05:03 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.

7. identified Oct 20, 2025, 05:32 PM UTC

   We’d like to share the latest update regarding the Voice and Reporting errors currently affecting some Gladly customers. As of October 20, 9:45 AM PDT, AWS continues to apply mitigation steps to address the network load balancer health issue impacting multiple AWS services. Connectivity has been restored for most services, and recovery efforts are ongoing. We are closely monitoring the situation and will provide the next update within 30 minutes or sooner as new information becomes available. If you have any questions or require assistance, please contactGladly Support should you have any questions or use this alternative form if you are unable to access the Help page. . Thank you for your continued patience and understanding.

8. identified Oct 20, 2025, 06:29 PM UTC

   We’d like to share the latest update regarding the ongoing issue impacting the Gladly platform. As of 10:38 AM PDT, AWS reports progress in resolving launch failures for new EC2 instances. Internal subsystems within EC2 are now showing early signs of recovery in several Availability Zones (AZs) within the US-EAST-1 region. AWS is applying mitigations to the remaining AZs, after which launch errors and network connectivity issues are expected to subside. Because the Gladly platform relies on AWS infrastructure, this incident continues to cause intermittent disruptions across multiple areas of Gladly, including: Platform access and overall performance Inability to connect to phone calls Missed or failed call connections Chats not routing properly to agents Related integrations and connected services Our engineering team remains in close coordination with AWS and continues to monitor recovery efforts closely to ensure full restoration of Gladly services. We will provide the next update by 12:00 PM PDT or sooner as new information becomes available. If you have any questions or require assistance, please contact Gladly Support or use this alternative form if you are unable to access the Help page. Thank you for your continued patience and understanding as we work diligently to restore full platform functionality.

9. identified Oct 20, 2025, 07:05 PM UTC

   We’d like to provide the latest update regarding the ongoing issue impacting the Gladly platform. As of 11:22 AM PDT, AWS reports continued progress in resolving launch failures for new EC2 instances. They are seeing increased launches of new instances and decreasing network connectivity issues in the US-EAST-1 region. Because the Gladly platform relies on AWS infrastructure, this outage has resulted in intermittent disruptions across multiple areas of Gladly, including: Platform access and overall performance Phone calls not connecting and missed calls Chats not routing properly to agents Related integrations and connected services Our engineering team continues to closely monitor AWS recovery efforts and is actively coordinating to ensure full restoration of Gladly services. We will provide the next update by 12:30 PM PDT or sooner as new information becomes available. If you have any questions or require assistance, please contact Gladly Support or use this alternative form if you are unable to access the Help page. Thank you for your continued patience and understanding as we work diligently to restore full platform functionality.

10. identified Oct 20, 2025, 07:32 PM UTC

    We’d like to share the latest update regarding the ongoing issue impacting the Gladly platform. As of 12:30 PM PDT, AWS continues to observe recovery across all services. Instance launches are now succeeding across multiple Availability Zones (AZs) in the US-EAST-1 region, and overall network connectivity continues to improve. Because the Gladly platform relies on AWS infrastructure, this incident continues to cause intermittent disruptions across multiple areas of Gladly, including: Platform access and performance Phone calls not connecting or missed calls Chats not routing to agents Related integrations and connected services Our engineering team remains in close coordination with AWS and continues to actively monitor progress to ensure full restoration of Gladly services. We will provide the next update by 1:00 PM PDT or sooner as new information becomes available. If you have any questions or require assistance, please contact Gladly Support or use this alternative form if you are unable to access the Help page. Thank you for your continued patience and understanding as we work diligently to restore full platform functionality.

11. identified Oct 20, 2025, 08:12 PM UTC

    We’d like to provide the latest update regarding the ongoing issue impacting the Gladly platform. As of 1:03 PM PDT, AWS reports continued service recovery across all AWS services. They have begun reducing throttles for new EC2 instance launches in the US-EAST-1 region that were previously implemented to mitigate impact. Because the Gladly platform relies on AWS infrastructure, some customers may still experience intermittent performance or connectivity issues across areas such as: Platform access and load times Phone calls not connecting or being missed Chats not routing properly to agents Related integrations and connected services Our engineering team remains in close coordination with AWS and continues to monitor their progress to ensure the complete restoration of all Gladly services. We will provide the next update by 1:45 PM PDT or sooner as new information becomes available. If you have any questions or require assistance, please contact Gladly Support or use this alternative form if you are unable to access the Help page. Thank you for your continued patience and understanding as we work diligently toward full platform recovery.

12. identified Oct 20, 2025, 08:52 PM UTC

    We’d like to provide the latest update regarding the ongoing issue impacting the Gladly platform. As of 1:03 PM PDT, AWS reports continued service recovery across all AWS services. They have begun reducing throttles for new EC2 instance launches in the US-EAST-1 region that were previously implemented to mitigate impact. Because the Gladly platform relies on AWS infrastructure, some customers may still experience intermittent performance or connectivity issues across areas such as: Platform access and load times Phone calls not connecting or being missed Chats not routing properly to agents Related integrations and connected services Our engineering team remains in close coordination with AWS and continues to monitor their progress to ensure the complete restoration of all Gladly services. We will provide the next update by 2:00 PM PDT or sooner as new information becomes available. If you have any questions or require assistance, please contact Gladly Support or use this alternative form if you are unable to access the Help page. Thank you for your continued patience and understanding as we work diligently toward full platform recovery.

13. identified Oct 20, 2025, 09:20 PM UTC

    We’d like to share the latest update regarding the ongoing issue impacting the Gladly platform. As of October 20, 2:20 PM PDT, AWS has restored EC2 instance launch throttles to pre-event levels, and EC2 launch failures have fully recovered across all Availability Zones (AZs) in the US-EAST-1 Region. AWS services that depend on EC2 launches—such as Redshift—are successfully processing their backlogs and are expected to reach full recovery within the next two hours. Because the Gladly platform relies on AWS infrastructure, some customers may continue to experience intermittent performance or connectivity issues across the platform, including: Platform access and speed Phone call connectivity or missed calls Chat routing to agents Related integrations and connected services Our engineering team remains in close coordination with AWS and continues to monitor all systems as recovery progresses toward complete restoration. We will provide the next update by 2:30 PM PDT or sooner as new information becomes available. If you have any questions or require assistance, please contact Gladly Support or use this alternative form if you are unable to access the Help page. Thank you for your continued patience and understanding as we work diligently toward full platform recovery.

14. identified Oct 20, 2025, 09:35 PM UTC

    We are continuing to see recovery with chat, phone and messaging services fully restored. Customers may experience delays in reporting updates. We expect these to continue resolving throughout the evening. If you have any questions or need assistance, please contact Gladly Support or use this alternative form if you’re unable to access the Help page. Thank you for your continued patience as AWS finalizes recovery efforts.

15. monitoring Oct 20, 2025, 09:45 PM UTC

    We are continuing to see recovery with chat, phone and messaging services fully restored. Customers may experience delays in reporting updates. We expect these to continue resolving throughout the evening. If you have any questions or need assistance, please contact Gladly Support or use this alternative form if you’re unable to access the Help page. Thank you for your continued patience as AWS finalizes recovery efforts.

16. resolved Oct 20, 2025, 10:01 PM UTC

    As of 3:01 PM PDT, all AWS services have returned to normal operations, Gladly platform is now fully operational. Our engineering team continues to monitor system performance and will share AWS’s (RCA) once available. If you have any questions or notice lingering issues, please contact Gladly Support or use this alternative form. Thank you for your patience and understanding during this incident.

Read the full incident report →

Started Oct 20, 2025, 07:10 AM UTC· resolved Oct 20, 2025, 09:56 AM UTC

1. investigating Oct 20, 2025, 07:10 AM UTC

   Gladly is investigating issues with network performance related to an AWS outage. 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.

2. identified Oct 20, 2025, 07:15 AM UTC

   We have identified the issue due to an AWS outage. Agents are intermittently unable to log into Gladly and send messages. You can review the AWS status page here: https://health.aws.amazon.com/health/status 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.

3. identified Oct 20, 2025, 07:25 AM UTC

   We are working as expediently as possible with AWS to resolve their issues. 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.

4. identified Oct 20, 2025, 07:30 AM UTC

   We continue to work to mitigate the issues stemming from the AWS outage. We will continue to post updates here every 30 minutes or sooner. Please use this alternative form to contact Gladly support.

5. identified Oct 20, 2025, 08:51 AM UTC

   The AWS regional outage is also affecting support request creation through the Gladly UI and the associated responses. Please contact Gladly Support at [email protected] should you have any questions.

6. identified Oct 20, 2025, 09:19 AM UTC

   We are working as expediently as possible with AWS to resolve their issues. We will continue to update this Status Page every 30 minutes or sooner until resolved. Please contact Gladly Support at [email protected] should you have any questions.

7. monitoring Oct 20, 2025, 09:39 AM UTC

   AWS has deployed a fix 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.

8. resolved Oct 20, 2025, 09:56 AM UTC

   After actively monitoring system performance, we are happy to report that this issue is now resolved and Gladly is operational. Backfills of Customer Journeys will be completed imminently. 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 →