Smartsheet Status

We are aware that some customers are receiving an increased volume of unwanted spam submissions through public Smartsheet forms, even with reCAPTCHA enabled. Our teams have been actively investigating and deploying additional protections. We are observing a decrease in spam activity as we continue applying and evaluating further mitigations. Who is affected: Customers who use public forms that do not require login.

This incident has been resolved.

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.

This incident has been resolved.

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.

This incident has been resolved.

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.

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.

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.

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.

The scheduled maintenance has been completed.

As part of Smartsheet’s commitment to providing the highest quality product, Brandfolder occasionally does maintenance to support new features and improvements. On February 14th from 8:00PM PT / 4:00AM UTC to 11:00pm PT / 7:00am UTC, the Brandfolder platform underwent maintenance and was offline from 8:02pm PT to 8:17pm PT. After completing the changes, we verified that all components were operational, and the Brandfolder platform was stable. We will continue to make improvements to ensure the continued stability of our platforms.

The scheduled maintenance has been completed.

As part of Smartsheet’s commitment to providing the highest quality product, Brandfolder occasionally does maintenance in order to support new features and improvements. The recent work to implement these improvements has been completed, and the Brandfolder platform is fully operational.

As part of Smartsheet’s commitment to providing the highest quality product, Brandfolder occasionally does maintenance in order to support new features and improvements. The recent work to implement these improvements has been completed, and the Brandfolder platform is fully operational.

The scheduled maintenance has been completed.

The recent schedule maintenance for Legacy Resource Management has been completed, and the service is now available again.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.