Histórico de interrupções do Smartsheet

1. 27 Eost 2026 da 13:33 UTCinvestigating

   Estamos investigando uma falha impactando login, acesso a planilhas, Centro de Controle e Visualização Dinâmica. A nossa equipa está totalmente empenhada em resolver a situação. Forneceremos atualizações frequentes até chegarmos a um estado de monitoramento.

2. 27 Eost 2026 da 13:52 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 27 Eost 2026 da 15:53 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 26 Eost 2026 da 13:28 UTCinvestigating

   Estamos a investigar um problema em que algumas folhas na instância Smartsheet dos EUA não estão a carregar. A nossa equipa está totalmente empenhada em resolver a situação. Forneceremos atualizações frequentes até chegarmos a um estado de monitoramento.

2. 26 Eost 2026 da 14:39 UTCinvestigating

   Ainda estamos a investigar um problema em que algumas folhas na instância Smartsheet dos EUA não estão a carregar. A nossa equipa está totalmente empenhada em resolver a situação. Forneceremos atualizações frequentes até chegarmos a um estado de monitoramento.

3. 26 Eost 2026 da 15:17 UTCinvestigating

   Ainda estamos a investigar um problema em que algumas folhas na instância Smartsheet dos EUA não estão a carregar. Este problema também está impactando Relatórios e Dashboards, bem como aplicativos Premium, incluindo Dynamic View, WorkApps e Gestão de Recursos. A nossa equipa continua totalmente empenhada em abordar a situação. Continuaremos a fornecer atualizações frequentes até chegarmos a um status de monitoramento.

4. 26 Eost 2026 da 15:47 UTCinvestigating

   Continuamos a investigar esta questão.

5. 26 Eost 2026 da 16:08 UTCidentified

   Implementamos uma correção para mitigar o problema, fazendo com que folhas na instância Smartsheet dos EUA não sejam carregadas, bem como o impacto nos relatórios, painéis e aplicativos Premium (Dynamic View, WorkApps, Gestão de Recursos e Centro de Controle). As métricas do sistema estão atualmente mostrando recuperação, e nossa equipe está monitorando ativamente o serviço para garantir total estabilidade. Publicaremos novas atualizações até que o incidente esteja totalmente resolvido.

6. 26 Eost 2026 da 16:22 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

7. 26 Eost 2026 da 18:23 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 25 Eost 2026 da 20:45 UTCinvestigating

   Estamos investigando atrasos ou falhas impactando Links de Células e Referências Cruzadas. A nossa equipa está totalmente empenhada em resolver a situação. Forneceremos atualizações frequentes até chegarmos a um estado de monitoramento.

2. 25 Eost 2026 da 21:25 UTCinvestigating

   Ainda estamos a investigar esta questão. A nossa equipa está totalmente empenhada em resolver a situação. Forneceremos atualizações frequentes até chegarmos a um estado de monitoramento.

3. 25 Eost 2026 da 22:09 UTCidentified

   Esta questão foi identificada e está a ser implementada uma solução.

4. 25 Eost 2026 da 22:23 UTCmonitoring

   Foi implementada uma solução e estamos a monitorizar o serviço para garantir a estabilidade.

5. 26 Eost 2026 da 00:23 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 11 Eost 2026 da 19:51 UTCinvestigating

   Estamos investigando problemas com Folhas, Relatórios e Fluxos de Trabalho. A nossa equipa está totalmente empenhada em resolver a situação. Forneceremos atualizações frequentes até chegarmos a um estado de monitoramento.

2. 11 Eost 2026 da 20:26 UTCinvestigating

   Estamos continuando a olhar para isso e estamos trabalhando para uma mitigação que esperamos ter no lugar em breve.

3. 11 Eost 2026 da 21:02 UTCmonitoring

   Uma mitigação está agora em vigor, e estamos a ver uma forte recuperação. Continuaremos a acompanhar de perto para confirmar que a questão está totalmente resolvida.

4. 11 Eost 2026 da 23:20 UTCresolved

   Este incidente foi resolvido.

5. 19 Eost 2026 da 22:38 UTCpostmortem

   Em 11 de agosto, de aproximadamente 7:00 a 4:20 PM PDT, alguns clientes experimentaram timeouts ou falhas ao carregar folhas e relatórios, bem como falhas no fluxo de trabalho de automação que causaram alguns fluxos de trabalho para desativar devido a taxas de erro elevadas. O incidente foi causado por um problema de encaminhamento de consulta de banco de dados relacionado às condições por trás de recentes interrupções de serviço, onde determinadas leituras foram encaminhadas para servidores de gravação primários e uma caso de borda envolvendo sincronização de planilha amplificada a carga resultante. Estabilizou-se o serviço até 3:20 PM PDT e confirmou-se a recuperação completa até 4:20 PM PDT após a escalação dos serviços afetados e falha em aumentar a capacidade dos servidores de banco de dados. Identificamos e implantamos uma correção de código permanente para corrigir o roteamento da consulta. Estamos também a melhorar o controlo e as salvaguardas para detectar e mitigar condições semelhantes anteriormente.

Traduzido automaticamente da atualização oficial do incidente.

1. 30 Gouere 2026 da 14:54 UTCinvestigating

   Estamos investigando a lentidão e os erros de timeout em Smartsheet, folhas de impacto, aplicativos premium, conectores e API. A nossa equipa está totalmente empenhada em resolver a situação. Forneceremos atualizações frequentes até chegarmos a um estado de monitoramento.

2. 30 Gouere 2026 da 15:26 UTCidentified

   Identificamos o problema responsável pelo problema de lentidão e timeout Smartsheet e estamos implementando uma correção. Forneceremos atualizações frequentes até chegarmos a um estado de monitoramento.

3. 30 Gouere 2026 da 15:40 UTCmonitoring

   Estamos observando estabilidade sendo restaurada para Smartsheet, aplicativos Premium, conectores e API. Continuamos a monitorá-lo de perto para confirmar a estabilidade total do serviço. Apresentaremos uma actualização uma vez confirmada a resolução.

4. 30 Gouere 2026 da 15:42 UTCmonitoring

   Continuamos monitorando quaisquer outros problemas.

5. 30 Gouere 2026 da 17:41 UTCresolved

   Este incidente foi resolvido.

6. 20 Eost 2026 da 17:23 UTCpostmortem

   Em 30 de julho de 2026, entre cerca de 11:00 e 15:57 UTC, alguns clientes não puderam carregar folhas e experientes timeouts API. Isso também afetou as integrações Centro de Controle, Vista de Mesa, Linha de Tempo e Conselho, Relatórios, Painéis, Formulários, Visão Dinâmica e Ponte. A causa foi um serviço de backend que veio sob carga de CPU pesada durante a rampa de tráfego matinal. Suas verificações de saúde automatizadas começaram a remover instâncias sobrecarregadas mais rápido do que as substituições poderiam vir on-line, e o ajuste de capacidade mínima do serviço foi muito baixo para absorver a perda. Nossos engenheiros resolveram o problema elevando os limites de capacidade do serviço, o que restaurou a capacidade saudável e voltou ao normal em poucos minutos. Nenhum dado foi perdido. Nós elevamos permanentemente o piso de capacidade, e estamos ajustando os controlos de saúde, adicionando monitoramento de nível de infraestrutura anterior, e construindo um livro de execução para evitar e acelerar a recuperação de questões semelhantes.

Traduzido automaticamente da atualização oficial do incidente.

1. 15 Gouere 2026 da 09:23 UTCinvestigating

   Estamos atualmente investigando um problema impedindo o carregamento com sucesso do Smartsheet US. Tentativas de login em Smartsheet EUA ou itens de acesso podem resultar em telas de carregamento que não completam. Forneceremos uma atualização em 30 minutos.

2. 15 Gouere 2026 da 09:38 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 15 Gouere 2026 da 09:44 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 15 Gouere 2026 da 09:55 UTCresolved

   Este incidente foi resolvido.

5. 17 Gouere 2026 da 01:22 UTCpostmortem

   A partir de aproximadamente 1:44 AM PT no dia 15 de julho de 2026, alguns clientes podem ter experimentado erros ao realizar ações que dependem das verificações de autorização da Smartsheet, como as verificações de acesso aos ativos. Isso foi causado por um problema temporário durante uma atualização do sistema de rotina que brevemente fez com que uma parte das solicitações fossem direcionadas para uma parte indisponível da nossa infraestrutura. Durante este período, os pedidos afectados podem ter falhado. A questão foi identificada e corrigida e restabelecida a operação normal.

Traduzido automaticamente da atualização oficial do incidente.

1. 24 Mezheven 2026 da 21:51 UTCinvestigating

   Estamos investigando relatórios de falta ou atraso de atualização / aprovação Solicita notificações e e-mails via fluxo de trabalho automatizado, bem como gatilho manual. A nossa equipa está totalmente empenhada em resolver a situação. Forneceremos atualizações frequentes até chegarmos a um estado de monitoramento.

2. 24 Mezheven 2026 da 23:04 UTCidentified

   O problema que causa falta ou atraso Atualizar / aprovar Solicita notificações e e-mails foi identificado. A nossa equipa está a implementar uma solução. Forneceremos atualizações frequentes até chegarmos a um estado de monitoramento.

3. 25 Mezheven 2026 da 00:43 UTCmonitoring

   Uma correção foi implementada para resolver os pedidos de atualização / aprovação perdidos ou atrasados de notificações e e-mails e estamos monitorando os resultados.

4. 25 Mezheven 2026 da 05:45 UTCresolved

   Este incidente foi resolvido.

5. 17 Gouere 2026 da 23:16 UTCpostmortem

   Em 24 de junho de 2026, um fluxo de trabalho automatizado gerou um volume anormalmente grande de solicitações de atualização em um curto período, que interrompeu temporariamente a infraestrutura interna de processamento de eventos responsável pela entrega de e-mails de notificação e alertas no aplicativo. Isso fez com que aproximadamente 85% das notificações de pedido de atualização e de aprovação fossem adiadas por cerca de 13 horas. Nenhum dado foi perdido – todas as notificações foram finalmente entregues uma vez que o sistema recuperado. Desde então, implementámos mecanismos automatizados de recuperação e estamos a acrescentar salvaguardas para evitar que os pedidos exagerados tenham impacto no gasoduto de notificação no futuro.

Traduzido automaticamente da atualização oficial do incidente.

1. 18 Mezheven 2026 da 21:42 UTCidentified

   Estamos cientes de que alguns clientes estão recebendo um volume aumentado de submissões de spam indesejados através de formulários Smartsheet públicos, mesmo com o reCAPTCHA habilitado. Nossas equipes têm investigado ativamente e implantado proteções adicionais. Estamos observando uma diminuição na atividade de spam enquanto continuamos aplicando e avaliando mitigação adicional. Quem é afectado: Clientes que usam formulários públicos que não requerem login.

2. 23 Mezheven 2026 da 07:44 UTCmonitoring

   Implementamos medidas para abordar o aumento da atividade de spam com formulários públicos Smartsheet. Continuaremos a acompanhar e a efectuar novos ajustamentos, conforme necessário. Se você está continuando a ver uma alta taxa de envios de spam, entre em contato com nossa equipe de suporte para que possamos investigar mais.

3. 8 Gouere 2026 da 20:46 UTCresolved

   Isto está agora resolvido. Ainda estamos monitorando ativamente os níveis de spam como uma estratégia contínua e em evolução. Encorajamos todos os clientes a enviar tickets de suporte para qualquer spam residual que apareça para que possamos continuar a sintonizar nossas soluções.

4. 17 Gouere 2026 da 23:14 UTCpostmortem

   A partir do final de maio, observamos um acentuado aumento de volume e sofisticação de submissões de spam para o público Smartsheet Forms \(formulários disponíveis para o público em geral e não exigindo um login Smartsheet\), mesmo com a configuração Captcha habilitada. Isso resultou em alguns clientes experimentando um aumento no conteúdo indesejado de spam, frequentemente contendo links criptomoeda ou phishing, entregues em suas folhas. A atividade foi gerada por bots automatizados operando através de redes anônimas e serviços proxy. Isto teve um impacto primordial, mas não se limitou à região dos EUA. Uma vez identificado o abuso, avaliamos, implementamos, testamos e afinamos uma série de medidas de proteção nas semanas seguintes. Como esse tipo de abuso automatizado se adapta ao longo do tempo, endereçá-lo requer uma abordagem iterativa: nós embutimos múltiplas proteções em ambas as formas, o serviço captcha, e a infra-estrutura subjacente, avaliamos sua eficácia contra o tráfego vivo, e os aperfeiçoamos conforme aprendemos mais, ajustando ou substituindo medidas que se mostraram menos eficazes. Ao longo desse processo, também monitoramos e trabalhamos para corrigir qualquer impacto não intencional para apresentação de formulários legítimos que possam ter ocorrido durante esse período. Spam automatizado é agora substancialmente bloqueado para baixo para virtualmente zero passar através da taxa e com mínimo ou nenhum impacto em submissões legítimas. Também estamos ativamente trazendo proteções semelhantes para o ambiente Smartsheet Gov. A partir de 1:46PT, 8 de julho, marcamos esta questão como resolvida. Se você ainda estiver observando submissões de spam, por favor, primeiro certifique-se de ter o Captcha habilitado no formulário. Se o Captcha estiver habilitado e você ainda estiver vendo spam, por favor envie um relatório usando o link “abuso de relatório” em seu formulário. Recomendamos sempre aplicar o [nível mais elevado de restrições de segurança de formulários] (https://help.smartsheet.com/artigos/2481836-manage-form-display-and-submission-options#toc-security) compatível com a sua solução e, se necessário, aplicar [form security from the admin center](https://help.smartsheet.com/artigos/2483290-aply-settings-forms). Continuaremos a acompanhar, sintonizar e reforçar estas proteções em curso. Isso inclui alterações para ter o Captcha habilitado por padrão para todos os novos formulários e novos controles administrativos que se desenrolam para os administradores do sistema para ter a capacidade de impor o Captcha para os formulários gerenciados por seu plano. Sabemos como nossos serviços são críticos para nossos clientes e pedimos desculpas por qualquer impacto que este incidente possa ter tido em você e em seu negócio. Prometemos que faremos tudo o que pudermos para aprender com este evento e usá-lo para impulsionar melhorias em nossos serviços para garantir que o Smartsheet é um parceiro que pode ser contado para entregar. Sabemos que o seu sucesso — e a sua confiança contínua no Smartsheet — depende disso.

Traduzido automaticamente da atualização oficial do incidente.

1. 10 Mezheven 2026 da 22:21 UTCinvestigating

   We are investigating the Smartsheet add-ons for Google which is currently not available. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. 11 Mezheven 2026 da 00:51 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 11 Mezheven 2026 da 03:30 UTCmonitoring

   The Smartsheet and Brandfolder add-ons for Google Docs, Sheets, and Slides were unavailable due to a Google platform change that required all affected add-ons to be redeployed. Our team has applied the necessary fixes and we are currently monitoring to confirm full stability.

4. 11 Mezheven 2026 da 11:02 UTCresolved

   This incident has been resolved.

5. 14 Eost 2026 da 18:51 UTCpostmortem

   **The Smartsheet Merge add-on for Google Docs stopped working after Google removed support for an older runtime environment that the add-on depended on, causing the add-on to fail entirely for all users \(~234,000 affected\).** The issue was resolved on June 11, 2026, by updating the add-on's code and deployment configuration to be compatible with Google's current platform — no customer data was lost.

1. 3 Mezheven 2026 da 20:28 UTCinvestigating

   We are investigating an issue with assets moving from Folders to the Parent Workspace. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. 3 Mezheven 2026 da 21:41 UTCidentified

   We have identified the issue responsible for the assets unexpectedly moved from Folders to the Parent Workspace and implemented a fix. We will provide frequent updates until we reach a monitoring status.

3. 3 Mezheven 2026 da 22:16 UTCidentified

   We are continuing our investigation into an issue with assets moving from Folders to the Parent Workspace. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status. Components: Core App - Sheets, Reports, Dashboards - Degraded

4. 3 Mezheven 2026 da 22:59 UTCinvestigating

   We are continuing our investigation into an issue with assets moving from Folders to the Parent Workspace. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

5. 4 Mezheven 2026 da 00:06 UTCidentified

   We have identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Currently, assets that were moved as a result of this issue cannot be moved by users, and we are diligently working to restore them to their original location. We will provide frequent updates until we reach a monitoring status.

6. 4 Mezheven 2026 da 02:14 UTCidentified

   We have identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Currently, assets that were moved as a result of this issue cannot be moved by users. We are continuing to work diligently to restore them to their original location. We will provide frequent updates until we reach a monitoring status.

7. 4 Mezheven 2026 da 12:25 UTCidentified

   We have identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Currently, assets that were moved as a result of this issue cannot be moved by users. We are continuing to work diligently to restore them to their original location. We will provide updates until we reach a monitoring status.

8. 4 Mezheven 2026 da 15:44 UTCidentified

   We have identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Currently, assets that were moved as a result of this issue cannot be moved by users. We are continuing to work on restoring assets to their original location, and some customers should begin to see assets restored to their original locations. Once assets have been restored to their original location, users will be able to move them. We will provide updates until we reach a monitoring status.

9. 4 Mezheven 2026 da 21:26 UTCidentified

   We identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Assets that were moved to the Parent Workspace as a result of this issue cannot be moved by users. We are continuing to restore assets to their original location, and some customers should begin to see assets in the correct folder structure. Once assets have been restored to their original location, users will be able to move them. We will provide updates until we reach a monitoring status.

10. 4 Mezheven 2026 da 23:01 UTCidentified

    We identified the issue responsible for the assets moving from Folders to the Parent Workspace and implemented a fix. Assets that were moved to the Parent Workspace as a result of this issue cannot be moved by users. We have restored some assets to their original locations, and some customers should begin to see assets in the correct folder structure. We are continuing to restore assets to their previous locations. Once assets have been restored to their original location, users will be able to move them. We will provide updates until we reach a monitoring status.

11. 5 Mezheven 2026 da 02:07 UTCidentified

    We identified and fixed an issue that caused assets to move from Folders to the Parent Workspace. Users will be unable to move affected assets until we restore them to their original locations. We have processed some of the affected assets, and some customers will see they have been restored to their prior locations. We continue to work on restoring assets to their original locations, and we will provide updates until we reach a monitoring status.

12. 5 Mezheven 2026 da 10:15 UTCidentified

    We identified and fixed an issue that caused assets to move from Folders to the Parent Workspace. Users cannot move affected assets until they are restored to their original locations. We have processed some of the affected assets, and some customers will see they have been restored to their prior locations. We are continuing to work on restoring assets to their original locations, and we will provide updates until we reach a monitoring status.

13. 5 Mezheven 2026 da 12:34 UTCidentified

    We identified and fixed an issue that caused assets to move from Folders to the Parent Workspace. Users cannot move affected assets until they are restored to their original locations. We have processed the majority of affected assets, and the customers will see they have been restored to their prior locations. We are continuing to work on restoring the remaining assets to their original locations, and we will provide updates until we reach a monitoring status.

14. 5 Mezheven 2026 da 19:53 UTCmonitoring

    We've identified and fixed the root cause of assets moving from Folders to the Parent Workspace. Our restoration process is complete and we have confirmed 99.98% of the affected assets have been returned to their correct locations. If you find any misplaced assets, you have two options: 1. Move them manually – items can be repositioned directly within the platform. 2. Open a support ticket – if you encounter errors or high volume, reply to an existing ticket or open a new one to engage our support team When contacting support, please include: • Workspace ID • Sheet ID(s) of affected assets • Reference: INC-1089 We apologize for the disruption and appreciate your patience.

15. 5 Mezheven 2026 da 23:53 UTCresolved

    We've identified and fixed the root cause of assets moving from Folders to the Parent Workspace. Our restoration process is complete and we have confirmed 99.98% of the affected assets have been returned to their correct locations. If you find any misplaced assets, you have two options: 1. Move them manually – items can be repositioned directly within the platform. 2. Open a support ticket – if you encounter errors or high volume, reply to an existing ticket or open a new one to engage our support team When contacting support, please include: • Workspace ID • Sheet ID(s) of affected assets • Reference: INC-1089 We apologize for the disruption and appreciate your patience.

16. 9 Mezheven 2026 da 23:07 UTCpostmortem

    On Wednesday, June 3, beginning at approximately 11:15 AM PDT, a platform configuration change caused sheets, reports, dashboards, and folders to be unexpectedly moved from their original folder locations to the top level of the workspace. Affected assets could not be manually moved by users during this period. The issue was identified at 1:28 PM PDT and the root cause was isolated and remediated at 2:10 PM PDT, stopping any further impact. The issue affected customers across North America, European Union, and Australia regions. Our engineering team worked to identify and restore all affected assets back to their original folder structure. The restoration process was completed on June 5, at 12:53 PM PDT, with 99.98% of affected assets successfully returned to their correct locations. For any remaining items that may still appear out of place, they can safely be moved manually as needed. If you encounter issues when attempting to move items, need guidance, or if the volume is too large to address manually, please open a Support case at [https://supportportal.smartsheet.com](https://supportportal.smartsheet.com) referencing "INC-1089" and our team will assist with restoration directly. We sincerely apologize for the disruption this caused. We are making improvements based on our learnings from this incident to prevent similar issues in the future.

1. 27 Mae 2026 da 17:50 UTCinvestigating

   We are currently investigating reports of sheets failing to open and displaying the error "We're having trouble reaching Smartsheet right now." Our team is actively working to resolve the issue and will provide frequent updates until we reach a monitoring status.

2. 27 Mae 2026 da 20:37 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 27 Mae 2026 da 20:39 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 28 Mae 2026 da 00:51 UTCresolved

   This incident has been resolved.

5. 23 Mezheven 2026 da 23:35 UTCpostmortem

   On May 27, 2026, from approximately 8:30 AM to 2:00 PM PDT, some customers were unable to load sheets, receiving the error, "We're having trouble reaching Smartsheet right now." This was caused by an unexpectedly high volume of simultaneous database requests triggered when loading configuration data for sheets with forms containing numerous column options. Under elevated traffic, this pattern generated hundreds of parallel queries, overwhelming the affected database cluster's read capacity. We resolved the issue by scaling database read capacity and routing traffic away from the affected infrastructure. To prevent recurrence, we are implementing changes to: * Redesign how column option data is fetched to reduce load. * Better distributing database traffic and protecting database capacity during periods of high usage. * Improving monitoring and tooling to detect and respond to issues faster. We know how critical our services are to our customers and apologize for any impact this incident may have had on you and your business. We promise that we will do everything we can to learn from this event and use it to drive improvement across our services to ensure that Smartsheet is a partner that can be counted on to deliver. We know that your success—and your continued trust in Smartsheet—depends on it.

1. 22 Ebrel 2026 da 16:45 UTCinvestigating

   We are investigating reports of the Workspace panel not opening or closing unexpectedly. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. 22 Ebrel 2026 da 17:01 UTCidentified

   We have identified the issue responsible for the Workspace panel not opening or closing unexpectedly and are implementing a fix. We will provide frequent updates until we reach a monitoring status.

3. 22 Ebrel 2026 da 17:09 UTCmonitoring

   We are observing stability being restored for Workspace panel not opening or closing unexpectedly. We are continuing to monitor it closely to confirm full service stability. We will provide frequent updates until we reach a resolved status.

4. 22 Ebrel 2026 da 19:20 UTCresolved

   Workspace panel functionality has been fully restored and is operating normally. The incident is now resolved.

5. 29 Ebrel 2026 da 15:48 UTCpostmortem

   Between 22:40 UTC on April 21 and 19:21 UTC on April 22, the Workspace Panel was not rendering consistently for users. Regardless of whether they had toggled it on or off, the panel did not appear. The issue was particularly present for non-Enterprise users \(Business and Pro accounts\). The impact was limited to the panel and did not affect any other UI flows within the Smartsheet app. The incident was resolved by rolling back the affected Workspace Panel to a previous known good version.

1. 17 Ebrel 2026 da 19:23 UTCinvestigating

   We are currently experiencing intermittent loading issues with the Resource Management module within Smartsheet. Please note that the standalone site at rm.smartsheet.com is working normally and can be used as a workaround while we resolve the integration issues.

2. 17 Ebrel 2026 da 19:35 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 18 Ebrel 2026 da 00:07 UTCresolved

   This incident has been resolved.

1. 13 Ebrel 2026 da 16:33 UTCinvestigating

   We are currently investigating an issue affecting Smartsheet Forms where a subset of users are experiencing failures when submitting forms.

2. 13 Ebrel 2026 da 17:52 UTCinvestigating

   We are continuing to investigate this issue.

3. 13 Ebrel 2026 da 18:31 UTCmonitoring

   The issue has been identified, Form submissions are operating normally now. Our team will continue to monitor the service and implement the necessary changes to prevent recurrence.

4. 13 Ebrel 2026 da 20:46 UTCresolved

   Forms Submissions are operating normally. The incident is now resolved.

5. 14 Ebrel 2026 da 14:26 UTCpostmortem

   On Monday, April 13, between 7:00 AM and 11:30 AM PST, some users experienced failures when submitting Smartsheet forms. The issue was isolated to CAPTCHA-enabled forms and was caused by a problem with our reCAPTCHA verification endpoint. Error rates declined significantly by mid-morning and the incident was fully resolved by 11:30 AM PST. All form submissions are operating normally.

1. 31 Meurzh 2026 da 18:53 UTCinvestigating

   We are currently investigating an issue causing 'EVALUATION MODE' watermarks and slow loading on proofs. We will provide an update in 30 minutes.

2. 31 Meurzh 2026 da 19:35 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 31 Meurzh 2026 da 20:11 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 31 Meurzh 2026 da 22:01 UTCresolved

   This incident has been resolved.

5. 13 Ebrel 2026 da 23:13 UTCpostmortem

   On March 30, 2026, at approximately 10:55 PM PDT, the Proofing service encountered issue where users encountered watermarks on all legacy proofs. The outage was caused by a licensing issue and was also compounded by an internal configuration issue causing a full proofing outage. The incident was mitigated by March 31, 2026 at 1:15PM PDT To prevent recurrence, we are conducting a post-incident review focused on improving monitoring and alerting for licensing issues as well bolstering deployment stability.

1. 24 Meurzh 2026 da 15:16 UTCinvestigating

   We are investigating blank results showing on User & Group Management pages in Admin Center. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. 24 Meurzh 2026 da 16:07 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 24 Meurzh 2026 da 16:08 UTCmonitoring

   We are observing stability being restored for the User & Group Management pages in Admin Center. A page refresh or clearing of cache from this page from your browser might be necessary for full resolution. We are continuing to monitor it closely to confirm full service stability.

4. 24 Meurzh 2026 da 18:30 UTCresolved

   This incident has been resolved.

5. 3 Ebrel 2026 da 23:20 UTCpostmortem

   On March 24, 2026, at approximately 07:55 UTC, the Admin Center Client experienced an issue where users were unable to view user groups in the Group Management view and users in the User Management page in certain cases — instead seeing an infinite loading screen. The issue was caused by a recent update to a shared part of the Admin Center interface that controls how loading indicators are shown during searching. In the Group Management area and UserView, this change accidentally made the page think it was always still loading, so users saw a never-ending loading screen and couldn't view groups \(and in some cases users\). The problem was fixed by rolling back that change, which finalized at 09:06 UTC. To prevent recurrence, we are conducting a post-incident review focused on improving monitoring and alerting for failed page renders in key Admin Center views, adding automated synthetic tests, and documenting recovery runbooks to reduce future resolution time.

1. 3 Meurzh 2026 da 17:16 UTCinvestigating

   We've investigating an issue with Form Submissions propagating to the sheet. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. 3 Meurzh 2026 da 17:47 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 3 Meurzh 2026 da 17:52 UTCidentified

   This issue has been identified and a fix has been implemented for new form submissions. For previous form submissions that failed in this window, a manual replay will be ran. Please do not re-submit these form submissions.

4. 3 Meurzh 2026 da 18:19 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 4 Meurzh 2026 da 23:42 UTCresolved

   Forms Submissions has been fully restored and is operating normally. The incident is now resolved.

6. 13 Meurzh 2026 da 23:53 UTCpostmortem

   On 4:47PM Pacific Standard Time, March 2nd, 2026, a code regression impacted a subset of Form Submissions to propagate to the underlying sheets and some API requests. Service was restored by rolling back to the last known stable deployment. A manual scale up was applied to meet the demands of the queues. Issue was successfully resolved by 9:53AM PST March 3rd, 2026. All previously failed form submissions were successfully replayed by 12:20PM PST, March 4th, 2026.

1. 27 Cʼhwevrer 2026 da 21:55 UTCidentified

   We have proactively paused the release of our February reports to ensure the highest level of data accuracy. Our team is currently resolving a synchronization issue, and we expect the corrected reports to be available shortly. We apologize for the inconvenience and appreciate your patience while we ensure your data is 100% correct.

2. 3 Meurzh 2026 da 15:55 UTCidentified

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

3. 9 Meurzh 2026 da 16:38 UTCidentified

   We are continuing to work on restoring full service.

4. 12 Meurzh 2026 da 21:08 UTCidentified

   A fix is being implemented. An update will be shared once completed.

5. 16 Meurzh 2026 da 19:05 UTCidentified

   We are finalizing the fix for this issue and will have an update shortly.

6. 24 Meurzh 2026 da 15:02 UTCmonitoring

   We have implemented the fix fully and we are monitoring for stability.

7. 24 Meurzh 2026 da 17:57 UTCresolved

   This incident has been resolved.

8. 25 Meurzh 2026 da 03:05 UTCpostmortem

   On February 25, 2026, a data synchronization issue was identified in Brandfolder's reporting infrastructure. The logical replication pipeline between the production database and the analytics data layer fell out of sync, which caused stale or missing data in Insights dashboards, subscription page metrics, and the Insights Data Connector. Standard monthly reports were proactively paused on February 27 to prevent delivery of inaccurate data, and a partial outage was posted to the status page. Engineering began rebuilding the replication pipeline, but encountered multiple failures during the data catch-up process due to the volume of data \(~5TB\) and recurring initialization errors. The replication pipeline was stabilized on March 16 and data began flowing to the analytics layer. The team then identified and resolved gaps in session data for specific dates, re-ran the affected data pipeline jobs, and verified data parity between the production database and analytics systems. Standard reporting was resumed on March 24, 2026, and the incident was resolved the same day. All previously missed reports have been generated and delivered. To prevent recurrence, we are conducting a post-incident review focused on improving monitoring and alerting for the replication pipeline, adding automated data health checks, and documenting recovery runbooks to reduce future resolution time.

1. 22 Cʼhwevrer 2026 da 12:17 UTCinvestigating

   We are investigating the home page error message "Something went wrong". Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. 22 Cʼhwevrer 2026 da 12:40 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 22 Cʼhwevrer 2026 da 14:45 UTCresolved

   This incident has been resolved.

4. 7 Meurzh 2026 da 01:02 UTCpostmortem

   Approximately on 3:15AM Pacific Standard Time February 22nd, 2026 in our Australia region, a deployment was performed to resolve a performance issue. However, a configuration required to validate session cookies was incorrectly specified, which caused the web app to become inaccessible after successful login. The issue was mitigated within 80 minutes by toggling a feature flag to reroute traffic back to a stable service and full functionality was restored by 4:35AM Pacific Standard Time February 22nd, 2026.

1. 17 Cʼhwevrer 2026 da 16:08 UTCinvestigating

   We are investigating Advanced Reports not being able to create new ones and also failing to refresh. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. 17 Cʼhwevrer 2026 da 16:29 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 17 Cʼhwevrer 2026 da 18:55 UTCresolved

   This incident has been resolved.

4. 19 Cʼhwevrer 2026 da 13:49 UTCpostmortem

   On February 17th, 2026, a failure in the service linking Resource Management Workflows to the main Data Shuttle engine resulted in a service disruption for the Resource Management Advanced Reporting feature in the US Production environment. Service was restored by rolling back the most recent Data Shuttle deployment \(originally released five days prior\). While this action immediately resolved the issue, preliminary analysis indicates the root cause was likely a memory exhaustion issue within the service, rather than a defect in the deployment itself. The rollback effectively reset the service state, clearing the error. A comprehensive RCA is currently underway to pinpoint the source of the outage.