Smartsheet Outage History

Smartsheet experienced an issue where the Workspace panel would not open or close as expected, affecting the Search functionality. The problem was identified and a fix was implemented, with service stability restored after 2.6 hours. The incident was fully resolved with normal Workspace panel functionality confirmed.

Smartsheet experienced intermittent loading issues with its Resource Management module integration for 4.8 hours. Users could access the standalone Resource Management site at rm.smartsheet.com as a workaround during the outage. The issue was resolved after implementing a fix and monitoring the results.

Smartsheet experienced a major incident where a subset of users encountered failures when submitting forms through the Forms component. The issue affected form submissions for 4.3 hours before being identified and resolved. The service returned to normal operation with ongoing monitoring to prevent recurrence.

Smartsheet's Document Proofing service experienced an issue causing 'EVALUATION MODE' watermarks to appear on proofs and slow loading performance. The problem affected users' ability to properly view and work with document proofs for 3.2 hours. The issue was identified, a fix was implemented and monitored, and the incident was fully resolved.

Smartsheet's User & Group Management pages in Admin Center displayed blank results for 3.3 hours, preventing administrators from accessing user and group information. The issue was identified and resolved with a fix implementation. Users may need to refresh their browser or clear cache to see the full resolution.

Smartsheet experienced a 30.5-hour incident where form submissions failed to propagate to their corresponding sheets, affecting the Forms component. The issue was identified and fixed for new submissions, while failed submissions during the outage window were manually replayed. The service was fully restored and returned to normal operation.

Smartsheet proactively paused the release of February Brandfolder monthly reports due to a data synchronization issue that could have affected report accuracy. The incident lasted approximately 25 days while the team worked to resolve the synchronization problem and ensure data integrity. The issue was fully fixed and monitoring confirmed stability before the incident was resolved.