Historial de interrupciones de Smartsheet

1. 27 de agosto de 2026 a las 13:33 UTCinvestigating

   Estamos investigando un outage impactante login, acceso a la hoja, Centro de Control y Vista Dinámica. Nuestro equipo está plenamente comprometido con la situación. Proporcionaremos actualizaciones frecuentes hasta que alcancemos un estado de monitoreo.

2. 27 de agosto de 2026 a las 13:52 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. 27 de agosto de 2026 a las 15:53 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 26 de agosto de 2026 a las 13:28 UTCinvestigating

   Estamos investigando un problema donde algunas hojas en la instancia de Smartsheet de EE.UU. no están cargando. Nuestro equipo está plenamente comprometido con la situación. Proporcionaremos actualizaciones frecuentes hasta que alcancemos un estado de monitoreo.

2. 26 de agosto de 2026 a las 14:39 UTCinvestigating

   Todavía estamos investigando un problema donde algunas hojas en la instancia de Smartsheet de los Estados Unidos no están cargando. Nuestro equipo está plenamente comprometido con la situación. Proporcionaremos actualizaciones frecuentes hasta que alcancemos un estado de monitoreo.

3. 26 de agosto de 2026 a las 15:17 UTCinvestigating

   Todavía estamos investigando un problema donde algunas hojas en la instancia de Smartsheet de los Estados Unidos no están cargando. Este tema también está impactando Reportes y Paneles, así como aplicaciones Premium incluyendo Vista Dinámica, WorkApps y Gestión de Recursos. Nuestro equipo sigue plenamente comprometido con la situación. Seguiremos proporcionando actualizaciones frecuentes hasta que alcancemos un estado de monitoreo.

4. 26 de agosto de 2026 a las 15:47 UTCinvestigating

   Seguimos investigando esta cuestión.

5. 26 de agosto de 2026 a las 16:08 UTCidentified

   Hemos implementado una solución para mitigar el problema causando que las hojas en la instancia Smartsheet de EE.UU. no se carguen, así como el impacto en Informes, Paneles y Aplicaciones Premium (Dynamic View, WorkApps, Resource Management y Control Center). Las métricas del sistema están mostrando recuperación, y nuestro equipo está monitoreando activamente el servicio para asegurar la plena estabilidad. Publicaremos nuevas actualizaciones hasta que el incidente se resuelva completamente.

6. 26 de agosto de 2026 a las 16:22 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

7. 26 de agosto de 2026 a las 18:23 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 25 de agosto de 2026 a las 20:45 UTCinvestigating

   Estamos investigando retrasos o fallos que afectan a Enlaces Celulares y Referencias de hoja cruzada. Nuestro equipo está plenamente comprometido con la situación. Proporcionaremos actualizaciones frecuentes hasta que alcancemos un estado de monitoreo.

2. 25 de agosto de 2026 a las 21:25 UTCinvestigating

   Todavía estamos investigando este tema. Nuestro equipo está plenamente comprometido con la situación. Proporcionaremos actualizaciones frecuentes hasta que alcancemos un estado de monitoreo.

3. 25 de agosto de 2026 a las 22:09 UTCidentified

   Esta cuestión ha sido identificada y se está aplicando una solución.

4. 25 de agosto de 2026 a las 22:23 UTCmonitoring

   Se ha implementado una solución y estamos monitoreando el servicio para asegurar la estabilidad.

5. 26 de agosto de 2026 a las 0:23 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 11 de agosto de 2026 a las 19:51 UTCinvestigating

   Estamos investigando problemas con hojas, informes y flujos de trabajo. Nuestro equipo está plenamente comprometido con la situación. Proporcionaremos actualizaciones frecuentes hasta que alcancemos un estado de monitoreo.

2. 11 de agosto de 2026 a las 20:26 UTCinvestigating

   Continuamos investigando esto y estamos trabajando para una mitigación que esperamos tener en su lugar pronto.

3. 11 de agosto de 2026 a las 21:02 UTCmonitoring

   Ahora está en marcha una mitigación, y estamos viendo una fuerte recuperación. Seguiremos monitoreando de cerca para confirmar que el problema está totalmente resuelto.

4. 11 de agosto de 2026 a las 23:20 UTCresolved

   Este incidente ha sido resuelto.

5. 19 de agosto de 2026 a las 22:38 UTCpostmortem

   El 11 de agosto de aproximadamente 7:00 AM a 4:20 PM PDT, algunos clientes experimentaron timeouts o fallos al cargar hojas e informes, así como fallas de flujo de trabajo de automatización que causaron que algunos flujos de trabajo desactivaran debido a tasas de error elevadas. El incidente fue causado por un problema de búsqueda de la base de datos relacionado con las condiciones detrás de las recientes interrupciones del servicio, donde ciertas lecturas fueron enrutadas a servidores de escritura primaria y un caso de borde que implica sincronización de hojas amplifica la carga resultante. Estabilizamos el servicio por 3:20 PM PDT y confirmamos la recuperación total por 4:20 PM PDT después de escalar los servicios afectados y fallar sobre los servidores de bases de datos para aumentar la capacidad. Identificamos y desplegamos un código permanente para corregir la routa de la consulta. También estamos mejorando la vigilancia y las salvaguardias para detectar y mitigar condiciones similares antes.

Traducido automáticamente desde la actualización oficial del incidente.

1. 30 de julio de 2026 a las 14:54 UTCinvestigating

   Estamos investigando errores de lentitud y de tiempo en Smartsheet, hojas de impacto, aplicaciones premium, conectores y API. Nuestro equipo está plenamente comprometido con la situación. Proporcionaremos actualizaciones frecuentes hasta que alcancemos un estado de monitoreo.

2. 30 de julio de 2026 a las 15:26 UTCidentified

   Hemos identificado el problema responsable de la lentitud de la hoja inteligente y la cuestión del tiempo de salida y estamos implementando una solución. Proporcionaremos actualizaciones frecuentes hasta que alcancemos un estado de monitoreo.

3. 30 de julio de 2026 a las 15:40 UTCmonitoring

   Estamos observando la estabilidad restaurada para Smartsheet, Premium Apps, Connectors y API. Seguimos monitoreándolo de cerca para confirmar la plena estabilidad del servicio. Proporcionaremos una actualización una vez que se confirme la resolución.

4. 30 de julio de 2026 a las 15:42 UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

5. 30 de julio de 2026 a las 17:41 UTCresolved

   Este incidente ha sido resuelto.

6. 20 de agosto de 2026 a las 17:23 UTCpostmortem

   El 30 de julio de 2026, entre aproximadamente las 11:00 y las 15:57 UTC, algunos clientes no podían cargar hojas y experimentar los timeouts de API. Esto también afectó al Centro de Control, Vista de Tablas, Horarios y Vistas a la Junta, Informes, Paneles, Formas, Vista Dinámica e integraciones del Puente. La causa fue un servicio de backend que vino bajo carga pesada de CPU durante la rampa de tráfico de la mañana. Sus cheques automatizados de salud comenzaron a eliminar instancias sobrecargadas más rápido de lo que los reemplazos podían venir en línea, y el ajuste de la capacidad mínima del servicio era demasiado bajo para absorber la pérdida. Nuestros ingenieros resolvieron el tema al elevar los límites de capacidad del servicio, que restauró la capacidad sana y devolvió el rendimiento a la normalidad en minutos. No se perdieron datos. Hemos levantado permanentemente el nivel de capacidad, y estamos afinando los controles de salud, añadiendo monitoreos a nivel de infraestructura anteriores, y construyendo un manual para prevenir y acelerar la recuperación de problemas similares.

Traducido automáticamente desde la actualización oficial del incidente.

1. 15 de julio de 2026 a las 9:23 UTCinvestigating

   Actualmente estamos investigando un problema que impide que Smartsheet US se cargue con éxito. Los intentos de iniciar sesión en Smartsheet US o los elementos de acceso pueden resultar en la carga de las pantallas que no se completan. Proporcionaremos una actualización en 30 minutos.

2. 15 de julio de 2026 a las 9:38 UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. 15 de julio de 2026 a las 9:44 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. 15 de julio de 2026 a las 9:55 UTCresolved

   Este incidente ha sido resuelto.

5. 17 de julio de 2026 a las 1:22 UTCpostmortem

   A partir de aproximadamente 1:44 AM PT el 15 de julio de 2026, algunos clientes pueden haber experimentado errores al realizar acciones que dependen de las comprobaciones de autorización de Smartsheet, como cheques de acceso en activos. Esto fue causado por una cuestión temporal durante una actualización del sistema de rutina que brevemente causó que una parte de las solicitudes fueran dirigidas a una parte indisponible de nuestra infraestructura. Durante este período, las solicitudes afectadas pueden haber fracasado. La cuestión fue identificada y corregida, y se restableció la operación normal.

Traducido automáticamente desde la actualización oficial del incidente.

1. 24 de junio de 2026 a las 21:51 UTCinvestigating

   Estamos investigando informes de falta o retraso Actualización / Aprobación Solicita notificaciones y correos electrónicos a través de flujos de trabajo automatizados, así como el gatillo manual. Nuestro equipo está plenamente comprometido con la situación. Proporcionaremos actualizaciones frecuentes hasta que alcancemos un estado de monitoreo.

2. 24 de junio de 2026 a las 23:04 UTCidentified

   Se ha identificado el problema que causa falta o retraso Actualización / Solicitudes de aprobación notificaciones y correos electrónicos. Nuestro equipo está implementando una solución. Proporcionaremos actualizaciones frecuentes hasta que alcancemos un estado de monitoreo.

3. 25 de junio de 2026 a las 0:43 UTCmonitoring

   Se ha implementado una solución para resolver las notificaciones y correos electrónicos de Actualización o Aprobación Desaparecidas y estamos monitoreando los resultados.

4. 25 de junio de 2026 a las 5:45 UTCresolved

   Este incidente ha sido resuelto.

5. 17 de julio de 2026 a las 23:16 UTCpostmortem

   El 24 de junio de 2026, un flujo de trabajo automatizado generó un volumen inusualmente grande de solicitudes de actualización en un breve período, que interrumpió temporalmente la infraestructura interna de procesamiento de eventos responsable de enviar correos electrónicos de notificación y alertas en aplicación. Esto causó que aproximadamente el 85% de las notificaciones de solicitud de actualización y solicitud de aprobación se retrasaran aproximadamente 13 horas. No se perdieron datos; todas las notificaciones se entregaron en última instancia una vez que el sistema se recuperó. Desde entonces hemos implementado mecanismos automatizados de recuperación y estamos agregando salvaguardias para evitar que las solicitudes sobredimensionadas impacten el oleoducto de notificación en el futuro.

Traducido automáticamente desde la actualización oficial del incidente.

1. 18 de junio de 2026 a las 21:42 UTCidentified

   Somos conscientes de que algunos clientes reciben un mayor volumen de envíos no deseados de spam a través de formularios de Smartsheet públicos, incluso con reCAPTCHA habilitado. Nuestros equipos han estado investigando e implementando protecciones adicionales. Estamos observando una disminución de la actividad de spam mientras seguimos aplicando y evaluando nuevas mitigacións. Quién es afectado: Clientes que usan formularios públicos que no requieren login.

2. 23 de junio de 2026 a las 7:44 UTCmonitoring

   Hemos implementado medidas para abordar el aumento de la actividad de spam con formas públicas Smartsheet. Seguiremos vigilando y realizaremos nuevos ajustes según sea necesario. Si continúa viendo una alta tasa de envíos de spam, póngase en contacto con nuestro equipo de soporte para que podamos investigar más adelante.

3. 8 de julio de 2026 a las 20:46 UTCresolved

   Esto ya está resuelto. Todavía estamos monitoreando activamente los niveles de spam como una estrategia en curso y en evolución. Alentamos a todos los clientes a enviar entradas de soporte para cualquier spam residual que venga a través de para que podamos seguir sintonizando nuestras soluciones.

4. 17 de julio de 2026 a las 23:14 UTCpostmortem

   A partir de finales de mayo, observamos un marcado aumento del volumen y la sofisticación de los envíos de spam al público Smartsheet Forms \(formas disponibles para el público en general y no requieren un login Smartsheet\), incluso con el ajuste Captcha habilitado. Esto dio lugar a que algunos clientes experimentaran un aumento del contenido no deseado de spam, con frecuencia conteniendo criptomonedas o enlaces de phishing, entregados en sus hojas. La actividad fue generada por bots automatizados que operan a través de redes anónimos y servicios proxy. Esto impactó principalmente, pero no se limitó a la región estadounidense. Una vez identificado el abuso, evaluamos, implementamos, probamos y sintonizamos una serie de medidas de protección durante las semanas siguientes. Debido a que el abuso automatizado de este tipo se adapta a lo largo del tiempo, abordarlo requiere un enfoque iterativo: encuadramos múltiples protecciones en ambas formas, el servicio captcha y la infraestructura subyacente, evaluamos su eficacia contra el tráfico en vivo, y las refinamos como aprendimos más, ajustando o reemplazando medidas que resultaron menos eficaces. A lo largo de este proceso también monitoreamos y trabajamos para corregir cualquier impacto no deseado a las presentaciones legítimas de forma que hayan ocurrido durante este período. El spam automatizado ahora está bloqueado substancialmente a prácticamente cero paso a través de la tasa y con un impacto mínimo o no en las presentaciones legítimas. También estamos llevando protecciones similares al entorno Smartsheet Gov. Al 1:46PT, 8 de julio, marcamos esta cuestión como resuelta. Si usted todavía está observando los envíos de spam por favor primero asegúrese de tener Captcha habilitado en el formulario. Si Captcha está habilitado y todavía está viendo spam, envíe un informe usando el enlace “abusivo de informes” en su forma. Siempre recomendamos aplicar [el nivel más alto de las formas de restricción de seguridad](https://help.smartsheet.com/articles/2481836-manage-form-display-and-submission-options#toc-security) compatible con su solución y si es necesario ejecute [form security from the admin center](https://help.smartsheet.com/articles/2483290-appse-security). Seguiremos vigilando, sintonizando y fortaleciendo estas protecciones en curso. Esto incluye cambios para tener Captcha habilitado por defecto para todas las nuevas formas y nuevos controles administrativos que se desenrollan para que los administradores del sistema tengan la capacidad de hacer cumplir Captcha para los formularios gestionados por su plan. Sabemos lo crítico que nuestros servicios son para nuestros clientes y nos disculpamos por cualquier impacto que este incidente pueda haber tenido en usted y su negocio. Prometemos que haremos todo lo que podamos para aprender de este evento y utilizarlo para impulsar la mejora a través de nuestros servicios para asegurar que Smartsheet sea un socio que se pueda contar para ofrecer. Sabemos que su éxito —y su confianza continua en Smartsheet— depende de ello.

Traducido automáticamente desde la actualización oficial del incidente.

1. 10 de junio de 2026 a las 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 de junio de 2026 a las 0:51 UTCidentified

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

3. 11 de junio de 2026 a las 3: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 de junio de 2026 a las 11:02 UTCresolved

   Este incidente ha sido resuelto.

5. 14 de agosto de 2026 a las 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.

Traducido automáticamente desde la actualización oficial del incidente.

1. 3 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 0: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 de junio de 2026 a las 2: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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 2: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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 20:37 UTCmonitoring

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

3. 27 de mayo de 2026 a las 20:39 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 28 de mayo de 2026 a las 0:51 UTCresolved

   This incident has been resolved.

5. 23 de junio de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 19:20 UTCresolved

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

5. 29 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 19:35 UTCmonitoring

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

3. 18 de abril de 2026 a las 0:07 UTCresolved

   This incident has been resolved.

1. 13 de abril de 2026 a las 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 de abril de 2026 a las 17:52 UTCinvestigating

   We are continuing to investigate this issue.

3. 13 de abril de 2026 a las 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 de abril de 2026 a las 20:46 UTCresolved

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

5. 14 de abril de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 19:35 UTCidentified

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

3. 31 de marzo de 2026 a las 20:11 UTCmonitoring

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

4. 31 de marzo de 2026 a las 22:01 UTCresolved

   This incident has been resolved.

5. 13 de abril de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 16:07 UTCidentified

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

3. 24 de marzo de 2026 a las 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 de marzo de 2026 a las 18:30 UTCresolved

   This incident has been resolved.

5. 3 de abril de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 17:47 UTCidentified

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

3. 3 de marzo de 2026 a las 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 de marzo de 2026 a las 18:19 UTCmonitoring

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

5. 4 de marzo de 2026 a las 23:42 UTCresolved

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

6. 13 de marzo de 2026 a las 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 de febrero de 2026 a las 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 de marzo de 2026 a las 15:55 UTCidentified

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

3. 9 de marzo de 2026 a las 16:38 UTCidentified

   We are continuing to work on restoring full service.

4. 12 de marzo de 2026 a las 21:08 UTCidentified

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

5. 16 de marzo de 2026 a las 19:05 UTCidentified

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

6. 24 de marzo de 2026 a las 15:02 UTCmonitoring

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

7. 24 de marzo de 2026 a las 17:57 UTCresolved

   This incident has been resolved.

8. 25 de marzo de 2026 a las 3: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 de febrero de 2026 a las 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 de febrero de 2026 a las 12:40 UTCmonitoring

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

3. 22 de febrero de 2026 a las 14:45 UTCresolved

   This incident has been resolved.

4. 7 de marzo de 2026 a las 1: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 de febrero de 2026 a las 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 de febrero de 2026 a las 16:29 UTCmonitoring

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

3. 17 de febrero de 2026 a las 18:55 UTCresolved

   This incident has been resolved.

4. 19 de febrero de 2026 a las 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.