Histórico de interrupções do Pendo

1. 2 Gwengolo 2026 da 15:48 UTCinvestigating

   Estamos investigando relatos de usuários serem inesperadamente assinados fora do Pendo e solicitados a voltar. Isso está afetando um subconjunto de usuários no ambiente dos EUA e estamos atualmente investigando outros ambientes para comportamento semelhante. A nossa equipa está a trabalhar activamente para determinar a causa. Se você está experimentando isso, limpar o cache e cookies do seu navegador para o domínio Pendo (ou reiniciar o navegador) resolveu a perturbação para alguns usuários. Partilharemos actualizações à medida que soubermos mais.

2. 2 Gwengolo 2026 da 16:45 UTCresolved

   Investigamos a questão e consideramos este incidente resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 27 Gouere 2026 da 14:48 UTCidentified

   Estamos a investigar uma perturbação que afecta o assistente de IA do Pendo, Leo. Alguns clientes podem ser incapazes de continuar uma conversa com Leo após a primeira mensagem. A nossa equipa identificou o comportamento e está a implantar uma solução. Seguem-se mais actualizações.

2. 27 Gouere 2026 da 15:06 UTCmonitoring

   Testámos e implantámos uma solução e o problema com conversas em Leo deve ser resolvido. Continuaremos a monitorar a correção por um período de tempo antes de resolver o problema.

3. 27 Gouere 2026 da 15:25 UTCresolved

   Este incidente está resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 14 Gouere 2026 da 12:56 UTCinvestigating

   Estamos investigando uma perturbação que afeta como o Pendo guia a exibição para os clientes usando a versão beta do Pendo Web SDK. Os clientes do Web SDK estável não são afetados. Nossa equipe está investigando ativamente e novas atualizações serão seguidas.

2. 14 Gouere 2026 da 13:19 UTCidentified

   Identificamos o comportamento que afeta os guias do Pendo na versão beta do Pendo Web SDK, onde os guias podem impedir a interação com a página subjacente. Estamos a implantar uma mudança para restaurar o comportamento normal. Os clientes do Web SDK estável não são afetados. Seguem-se mais actualizações.

3. 14 Gouere 2026 da 14:14 UTCmonitoring

   Implantamos uma alteração para restaurar o comportamento normal do guia na versão beta do Pendo Web SDK. Os clientes do Web SDK estável não são afetados. Estamos a monitorizar para confirmar a recuperação total e iremos dar seguimento uma vez confirmada a resolução.

4. 14 Gouere 2026 da 15:53 UTCresolved

   Esta perturbação foi totalmente resolvida. O SDK Web estável não foi impactado em nenhum ponto. Obrigado pela vossa paciência.

Traduzido automaticamente da atualização oficial do incidente.

1. 10 Gouere 2026 da 10:58 UTCmonitoring

   Esta manhã, tivemos atrasos no processamento dos acontecimentos. Embora nenhum evento tenha sido perdido durante este período, os atrasos poderiam ter impactado o direcionamento de guias que dependem de páginas e pontos de vista de recursos para elegibilidade. Neste momento, estamos de volta à latência normal de processamento para 90% dos clientes, e logo deve alcançar para o resto.

2. 10 Gouere 2026 da 11:08 UTCmonitoring

   Todos os eventos que não os eventos de repetição de sessão estão de volta à latência normal do processamento. Continuamos a fazer progressos no backlog do evento de repetição da sessão.

3. 10 Gouere 2026 da 11:13 UTCmonitoring

   Continuamos monitorando quaisquer outros problemas.

4. 10 Gouere 2026 da 12:35 UTCresolved

   Todos os atrasos de processamento de eventos foram apanhados. Este incidente está resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 2 Gouere 2026 da 15:47 UTCidentified

   Identificamos uma perturbação que afeta vários destinos do Data Sync. Clientes com destinos Data Sync configurados podem estar experimentando falhas de entrega e podem ter recebido emails de notificação de falha de destino automatizados do Pendo. Nossa equipe de engenharia está trabalhando ativamente para restaurar a conectividade entre os destinos afetados. Se você recebeu um email de notificação de falha de destino, nenhuma ação é necessária de você neste momento. Forneceremos orientações atualizadas se forem necessários passos em sua extremidade.

2. 2 Gouere 2026 da 21:40 UTCmonitoring

   Restauramos a conectividade em todos os destinos afetados do Data Sync. Não é necessária nenhuma ação adicional de você. Exportações recorrentes estão em fila de espera e processamento. Alguns atrasos na entrega podem persistir durante o fim de semana, mas não resultará em destinos sendo automaticamente desativados. O preenchimento de quaisquer dados faltantes da janela de interrupção está planejado para o início da próxima semana para evitar qualquer impacto no processamento e entrega em curso. Publicaremos outra atualização assim que o preenchimento estiver completo.

3. 3 Gouere 2026 da 13:08 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 15 Mezheven 2026 da 19:56 UTCresolved

   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.

1. 29 Mae 2026 da 12:40 UTCinvestigating

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

2. 29 Mae 2026 da 15:32 UTCresolved

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

1. 28 Mae 2026 da 21:34 UTCinvestigating

   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.

2. 28 Mae 2026 da 22:21 UTCmonitoring

   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.

3. 29 Mae 2026 da 00:16 UTCresolved

   This issue is now formally resolved.

1. 28 Mae 2026 da 14:41 UTCinvestigating

   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.

2. 28 Mae 2026 da 17:29 UTCidentified

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

3. 28 Mae 2026 da 18:29 UTCmonitoring

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

4. 9 Mezheven 2026 da 12:39 UTCresolved

   This incident has been resolved.

1. 27 Mae 2026 da 15:56 UTCidentified

   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.

2. 27 Mae 2026 da 17:45 UTCidentified

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

3. 27 Mae 2026 da 21:55 UTCmonitoring

   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.

4. 27 Mae 2026 da 23:33 UTCresolved

   This incident has been resolved.

1. 19 Mae 2026 da 16:50 UTCinvestigating

   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.

2. 19 Mae 2026 da 17:27 UTCinvestigating

   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.

3. 19 Mae 2026 da 17:33 UTCmonitoring

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

4. 19 Mae 2026 da 19:06 UTCresolved

   This incident has now been fully resolved.

1. 19 Mae 2026 da 10:24 UTCidentified

   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.

2. 19 Mae 2026 da 13:51 UTCidentified

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

3. 19 Mae 2026 da 14:08 UTCidentified

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

4. 26 Mae 2026 da 06:43 UTCresolved

   This incident has been resolved.

1. 13 Mae 2026 da 13:29 UTCinvestigating

   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.

2. 13 Mae 2026 da 14:18 UTCinvestigating

   We are continuing to investigate this issue.

3. 13 Mae 2026 da 16:06 UTCinvestigating

   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.

4. 13 Mae 2026 da 18:37 UTCidentified

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

5. 13 Mae 2026 da 19:28 UTCmonitoring

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

6. 13 Mae 2026 da 22:21 UTCresolved

   We consider this issue fully resolved.

1. 8 Mae 2026 da 17:05 UTCinvestigating

   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.

2. 8 Mae 2026 da 17:58 UTCidentified

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

3. 8 Mae 2026 da 18:24 UTCmonitoring

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

4. 8 Mae 2026 da 19:09 UTCresolved

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

1. 13 Ebrel 2026 da 21:31 UTCinvestigating

   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.

2. 13 Ebrel 2026 da 23:16 UTCidentified

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

3. 14 Ebrel 2026 da 06:39 UTCidentified

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

4. 14 Ebrel 2026 da 06:39 UTCresolved

   This incident has been resolved.

1. 18 Meurzh 2026 da 12:50 UTCinvestigating

   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.

2. 18 Meurzh 2026 da 13:02 UTCidentified

   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.

3. 18 Meurzh 2026 da 13:05 UTCresolved

   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.

1. 12 Meurzh 2026 da 14:49 UTCinvestigating

   We are currently investigating an issue where no recipients are found when attempting to send an email update for feedback items or ideas in Pendo Listen. This includes items submitted within the last 30 days.

2. 12 Meurzh 2026 da 15:28 UTCidentified

   We are currently resolving a technical mismatch between our database and the user interface that is preventing some email information from appearing correctly. A fix is being tested now.

3. 12 Meurzh 2026 da 18:07 UTCresolved

   Following testing, we have deployed a fix and email information is now appearing as expected and we consider the issue resolved.

1. 5 Cʼhwevrer 2026 da 12:21 UTCinvestigating

   We are investigating a potential issue affecting Guides and the Resource Center. Some users may notice unexpected behavior with Guide statuses (Draft, Staging, Production) and may be unable to view or edit the Resource Center modules. We are working to understand the scope and impact and will share updates as we learn more.

2. 5 Cʼhwevrer 2026 da 14:04 UTCinvestigating

   Our teams are in deep-dive mode and still investigating.

3. 5 Cʼhwevrer 2026 da 14:43 UTCinvestigating

   We are continuing to investigate this issue.

4. 5 Cʼhwevrer 2026 da 16:00 UTCinvestigating

   Our investigation into the root cause of this issue is ongoing.

5. 5 Cʼhwevrer 2026 da 17:21 UTCinvestigating

   Our team is still actively investigating and is drawing closer to remediation.

6. 5 Cʼhwevrer 2026 da 19:01 UTCinvestigating

   We are continuing to work through resolving and remediating this issue.

7. 5 Cʼhwevrer 2026 da 21:42 UTCinvestigating

   Our investigation is still ongoing.

8. 5 Cʼhwevrer 2026 da 23:35 UTCmonitoring

   We have rolled out a fix for an issue impacting Resource Center Guide Modules where guide module changes could not be accessed via the VDS or edited. As part of this fix, we did not automatically apply Resource Center state changes made after February 4 at 4:00 PM, to avoid making assumptions about intended configurations. Customers who updated Resource Center states after this time will need to re-publish their Resource Center from Draft to Production to ensure their desired configuration is reflected. We will continue to monitor the situation. Additionally, as an extra precaution our team will be conducting a full review of guide statuses to ensure all guides reflect their intended state and content. We do not expect further impact, but will provide updates if anything unexpected is identified. We will continue to monitor closely and provide updates if needed.

9. 8 Cʼhwevrer 2026 da 14:57 UTCresolved

   After monitoring guide and resource center behavior and conducting a review of all guide statuses, we consider this issue fully resolved.

1. 4 Cʼhwevrer 2026 da 21:48 UTCinvestigating

   Our team is currently investigating an issue impacting guides created in the Visual Design Studio. Some users may be unable to launch existing guides in the UI, and blank steps may appear in the designer. Guides that are affected will also be unavailable in Production and Staging environments. When launching the Visual Design Studio, the experience may time out or fail entirely, and all guide steps may be missing, with related errors appearing in the browser console.

2. 4 Cʼhwevrer 2026 da 23:30 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 Cʼhwevrer 2026 da 23:40 UTCidentified

   We have identified the issue and are actively testing a fix to both rendering guides in production and staging as well as restore user access to the Visual Design Studio.

4. 5 Cʼhwevrer 2026 da 00:13 UTCidentified

   Our team is currently in the final stages of validating our fix and are hopeful to have resolution shortly.

5. 5 Cʼhwevrer 2026 da 00:44 UTCidentified

   We are continuing to validate our final testing and will have an update as soon as possible.

6. 5 Cʼhwevrer 2026 da 01:20 UTCidentified

   The majority of impacted guides have been restored to their expected state with the Visual Designer Studio loading and functioning. However, a small subset of guides (about 2%) remains impacted, and guides within Resource Center Guide Modules are still experiencing issues. Our team is actively working on these remaining guides as well as resolving the Resource Center Guide Module issue. We’ll continue to provide updates as progress is made.

7. 5 Cʼhwevrer 2026 da 01:54 UTCidentified

   Guide deliverability and functionality have been fully restored with the exception of Resource Center Guide Modules. All other guides are loading and functioning as expected across environments. We are continuing to work on an issue impacting Resource Center Guide Modules, which remain nonfunctional at this time. Our team is actively addressing this and will provide further updates as progress is made.

8. 5 Cʼhwevrer 2026 da 02:17 UTCidentified

   Guide functionality and deliverability have been restored, with the exception of accessing Resource Center Guide Modules. As part of the restoration process, impacted guides were temporarily moved to a Draft state. Our team is actively working to return these guides to their previous status where applicable. No guide content was lost. We are continuing to work on resolving the Resource Center Guide Module issue and will provide further updates as progress is made.

9. 5 Cʼhwevrer 2026 da 04:45 UTCresolved

   Guide functionality and deliverability have been fully restored. All guides that were temporarily moved to a Draft state have now been returned to their previous status. We believe Resource Center Guide Modules were not impacted in Production or Staging environments. An issue impacting the ability to edit some guides within RC Guide Modules while in Draft state was identified and is being addressed separately. Some guides may appear to still be in a Draft state due to browser caching. Logging out and back into Pendo will refresh the UI and reflect the correct guide status. This incident is now resolved.

1. 9 Genver 2026 da 20:46 UTCinvestigating

   Our Support Bot vendor is currently experiencing latency issues and are currently investigating the cause. If you are experiencing issues with our product and need to create a support ticket, please use our support request form in the meantime: https://support.pendo.io/hc/en-us/requests/new Thank you for your patience!

2. 9 Genver 2026 da 21:18 UTCresolved

   The latency issue with our Support Bot vendor has been resolved. The Support Bot is now operating normally. Thank you for your patience while this was investigated.