Pendo outage history

Some customers are experiencing authentication errors when connecting to the Pendo MCP, which prevents the connection from being established. Our team is actively investigating to determine cause of this disruption. Existing MCP connections will continue to work until session expiration.

We are continuing to investigate the cause of this disruption.

This incident has been resolved.

We are currently investigating an issue where pairing a mobile device with the Pendo Designer fails. This affects on-device guide testing and Mobile Debugger in multiple regions. We'll share an update as soon as we have more information.

This incident has been resolved.

We have identified the cause of a disruption affecting guide targeting for a subset of visitors in the US environment, beginning at approximately 3:50 PM EDT. Our team is actively deploying a fix and will provide a further update as it is confirmed.

Guide targeting has been restored. We are continuing to monitor for any further issues.

This incident has been resolved.

We have deployed a fix for a disruption affecting login, guide delivery latency (web and mobile), and event data processing latency in our US environment. Our team is actively monitoring to confirm the behavior is fully resolved and will provide a further update once that's confirmed.

We are continuing to monitor for any further issues.

Guide deliverability, data processing, and logins have been restored. There was no loss of data. There may be a small delay in event processing.

This incident has been resolved.

We are investigating reports of users being unexpectedly signed out of Pendo and prompted to log back in. This is affecting a subset of users in the US Environment and we are currently investigating other environments for similar behavior. Our team is actively working to determine the cause. If you are experiencing this, clearing your browser's cache and cookies for the Pendo domain (or restarting your browser) has resolved the disruption for some users. We'll share updates as we learn more.

We have investigated the issue and consider this incident resolved.

We are investigating a disruption affecting Pendo's AI assistant, Leo. Some customers may be unable to continue a conversation with Leo after the first message. Our team has identified the behavior and is deploying a fix. Further updates will follow.

We have tested and deployed a fix and the issue with continuing conversations in Leo should be resolved. We will continue to monitor the fix for a period of time before resolving the issue.

This incident is resolved.

We are investigating a disruption affecting how Pendo guides display for customers using the beta version of the Pendo Web SDK. Customers on the stable Web SDK are not affected. Our team is actively investigating and further updates will follow.

We have identified the behavior affecting Pendo guides on the beta version of the Pendo Web SDK, where guides may prevent interaction with the underlying page. We are deploying a change to restore normal behavior. Customers on the stable Web SDK are not affected. Further updates will follow.

We have deployed a change to restore normal guide behavior on the beta version of the Pendo Web SDK. Customers on the stable Web SDK are not affected. We are monitoring to confirm full recovery and will follow up once resolution is confirmed.

This disruption has been fully resolved. The Stable Web SDK was not impacted at any point. Thank you for your patience.

This morning we experienced delays in processing of incoming events. While no events were lost during this time, the delays could have impacted the targeting of guides which rely on page and feature views for eligibility. At this time, we are back to normal processing latency for 90% of customers, and should soon catch up for the rest.

All events other than session replay events are back to normal processing latency. We are continuing to make progress on the session replay event backlog.

We are continuing to monitor for any further issues.

All event processing delays have been caught up. This incident is resolved.

We have identified a disruption affecting multiple Data Sync destinations. Customers with Data Sync destinations configured may be experiencing delivery failures and may have received automated destination-failure notification emails from Pendo. Our engineering team is actively working to restore connectivity across affected destinations. If you received a destination-failure notification email, no action is required from you at this time. We will provide updated guidance if steps are needed on your end.

We have restored connectivity across all affected Data Sync destinations. No further action is required from you. Recurring exports are queued and processing. Some delays in delivery may persist through the weekend, but will not result in destinations being automatically disabled. The backfill of any missing data from the disruption window is planned for early next week to avoid any impact to ongoing processing and delivery. We will post another update once the backfill is complete.

This incident has been resolved.

Between June 3, 2026 and June 4, 2026, some customers experienced two related issues affecting in-app guides on the Pendo platform (pendo.io environment): Guide Targeting Disruption: Guides that used negated, nested segment rules ("Segment is not equal to...") were incorrectly evaluated due to a segment flag processing bug. Affected guides may have failed to display to intended audiences during this window. Conversational AI Guide Editor Unavailable: The Conversational AI interface within the guide editor ("Edit in Pendo") was inaccessible.

Pendo Academy is showing "unauthorized" in all environments. This is not related to user credentials. Our teams are currently investigating the root cause.

This incident has been resolved and Pendo Academy should be accessible across all regions now.

We are currently experiencing a delay in Agent Analytics data processing for customers in our EU region. This is caused by 429 rate limit errors from a third-party AI provider. We will provide an update and resolution as soon as possible.

We have a fix in place that has begun mitigating the issue; we expect full resolution but will continue to monitor for the time being.

This issue is now formally resolved.

We are aware that the issue we believed we had fully resolved yesterday has continued after we employed yesterday's fix. The issue may be impacting some customers' Salesforce integrations. Affected users may experience authentication errors or disruptions to Salesforce-connected features (e.g. our Gong integration for Listen). Our engineering team is actively investigating and working toward a resolution. We will provide further updates as more information becomes available.

We have identified the root cause of the issue and are currently testing the fix before rolling it out to production.

We deployed the fix and will continue to monitor to ensure it resolves the initial issue.

This incident has been resolved.

We are aware of an issue that may be impacting some customers' Salesforce integrations. Affected users may experience authentication errors or disruptions to Salesforce-connected features (e.g. our Gong integration for Listen). Our engineering team is actively investigating and working toward a resolution. We will provide further updates as more information becomes available.

We are working currently to roll out a hotfix to mitigate this issue.

We have deployed a hotfix for the issue impacting Salesforce integrations and are actively monitoring. If your integration is still not syncing, a Pendo admin and a Salesforce user with the proper Salesforce permissions may need to re-authenticate your Salesforce connection manually. To manually reset please 1) Navigate to Subscription Settings > Metadata 2) Scroll to Salesforce Integration 3) Click Begin 4) Authenticate with Salesforce (then following instructions in Salesforce) 5) Finally hit Sync to resume. For more details on Salesforce requirements and set-up, please review the "Prerequisites" and "Set up the connection" sections in the article here: https://support.pendo.io/hc/en-us/articles/16584371535771-Set-up-the-Salesforce-integration-for-Pendo If you continue to experience issues after re-authenticating, please reach out to our support team.

This incident has been resolved.

We are currently investigating an issue affecting guide delivery in the US1 region. Guides are not loading for end users in this environment. Our team is actively working on a resolution.

We have implemented some changes to mitigate the issue with partial restoration, but are still working to fully resolve and identify the root cause of the issue.

Guide delivery in the US1 region has been restore and guides are now loading normally. We are continuing to monitor the situation.

This incident has now been fully resolved.

We are currently experiencing an issue causing Listen email notifications to be unavailable. Our team has identified an issue and has temporarily disabled Listen emails while we work on a fix. All other Pendo email services are unaffected.

We are continuing to work towards a resolution. We will continue to provide updates as they become available.

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

This incident has been resolved.

We are aware of an issue affecting the Visual Design Studio (VDS) where opening a guide for editing may intermittently load a previously opened guide instead of the selected one. In some cases, the guide picker may also appear unexpectedly. Workaround: In the Designer, click the guide name displayed in the top banner to open the guide picker, select the correct guide from the list, and click Proceed to load it. Our engineering team is investigating. We will provide further updates as our investigation progresses. We apologize for any disruption to your workflow.

We are continuing to investigate this issue.

We are continuing to investigate the issue affecting the Visual Design Studio (VDS) where opening a guide for editing may intermittently load a previously opened guide instead of the selected one. In some cases, the guide picker may also appear unexpectedly. Workaround: In the Designer, click the guide name displayed in the top banner to open the guide picker, select the correct guide from the list, and click Proceed to load it. Our engineering team remains actively engaged in the investigation. We will provide additional updates as more information becomes available. We apologize for the continued disruption and appreciate your patience.

We have identified a bug in a code release and are currently working to revert to mitigate this issue using our Visual Designer.

We have successfully reverted the code causing the issue and are monitoring the issue.

We consider this issue fully resolved.

We are aware of an issue affecting users attempting to connect to the Pendo MCP server, where authentication is failing with an "invalid scope" error. Our engineering team has identified the root cause and a fix is currently in progress — we will provide an update once it has been deployed to production.

Our team has identified the issue with a code change on Monday, April 4, which we are currently rolling back.

We have successfully rolled back and are now monitoring the issue.

The rollback we have implemented has successfully fixed the "invalid scope" authentication error and this issue is now resolved.

We are currently investigating an issue where event processing is delayed for a subset of customers. Affected users may notice delays or gaps in analytics data as we work with our vendor to restore full service. We have escalated the issue and are actively monitoring the situation. We will provide updates as more information becomes available.

The root issue causing the event processing day has been identified and we are working with our vendor toward full resolution.

The issue causing delays in event processing has been fully resolved.

This incident has been resolved.

We are currently investigating an issue in our US region where users are unable to edit existing segments. Any attempt to add a rule to a pre-existing segment will result in an error. We are investigating if there are similar impacts to other regions currently. As a workaround, cloning and existing segment or creating new segments works as expected. Our team is working to identify the cause of this issue and we will share an update as soon as possible. We apologize for any inconvenience this may cause.

We have identified the cause of an issue in our US region where users are unable to edit existing segments. Any attempt to add a rule to a pre-existing segment will result in an error. Impact has been narrowed to US region only. We are currently working to roll out a fix. As a workaround, cloning and existing segment or creating new segments works as expected.

We are happy to report that the issue preventing users in our US region from editing existing segments has been fully resolved. All systems are now operating normally, and you can once again edit and manage all of your segments without error. We apologize for the disruption this may have caused and appreciate your patience as we worked to implement a fix.