Smartsheet Outage History

On October 1, 2026, a deployment issue caused automated and manual approval workflows to fail across our US, EU, and AU regions for approximately 4.5 hours \(our Government cloud region was unaffected throughout\). Our team restored normal workflow execution within about an hour of the incident being declared. During recovery, the backlog of requests that had built up caused a smaller, secondary issue: some customers experienced delayed approval/update request notifications. We've since recovered the vast majority of affected notifications and are implementing safeguards to prevent a similar deployment issue from recurring, along with improvements to how our systems handle request backlogs so that delayed notifications are retried automatically rather than silently dropped.

On September 11th, 2026, starting at 12:47 PM PDT, users in the US began experiencing errors logging in to and accessing Smartsheet. Users in the EU and AU regions were not affected. By approximately 1:38 PM PDT, full service was confirmed to be restored. Our engineering teams quickly determined that a routine internal configuration change was the cause of Smartsheet's unavailability. The change was corrected, and full service was restored by approximately 1:38 PM PDT. We are currently reviewing our configuration management and change review processes, along with our internal monitoring, to prevent similar issues in the future.

On August 11 from approximately 7:00 AM to 4:20 PM PDT, some customers experienced timeouts or failures when loading sheets and reports, as well as automation workflow failures that caused some workflows to disable due to elevated error rates. The incident was caused by a database query-routing issue related to the conditions behind recent service disruptions, where certain reads were routed to primary write servers and an edge case involving sheet synchronization amplified the resulting load. We stabilized the service by 3:20 PM PDT and confirmed full recovery by 4:20 PM PDT after scaling affected services and failing over database servers to increase capacity. We identified and deployed a permanent code fix to correct the query routing. We are also improving monitoring and safeguards to detect and mitigate similar conditions earlier.

On July 30, 2026, between approximately 11:00 and 15:57 UTC, some customers could not load sheets and experienced API timeouts. This also affected Control Center, Table View, Timeline and Board views, Reports, Dashboards, Forms, Dynamic View, and Bridge integrations. The cause was a backend service that came under heavy CPU load during the morning traffic ramp-up. Its automated health checks began removing overloaded instances faster than replacements could come online, and the service's minimum capacity setting was too low to absorb the loss. Our engineers resolved the issue by raising the service's capacity limits, which restored healthy capacity and returned performance to normal within minutes. No data was lost. We have permanently raised the capacity floor, and we are tuning the health checks, adding earlier infrastructure-level monitoring, and building a runbook to prevent and speed recovery from similar issues.

Starting at approximately 1:44 AM PT on July 15, 2026, some customers may have experienced errors when performing actions that rely on Smartsheet's authorization checks, such as access checks on assets. This was caused by a temporary issue during a routine system update that briefly caused a portion of requests to be directed to an unavailable part of our infrastructure. During this period, affected requests may have failed. The issue was identified and corrected, and normal operation was restored.

On June 24, 2026, an automated workflow generated an unusually large volume of update requests in a short period, which temporarily disrupted the internal event-processing infrastructure responsible for delivering notification emails and in-app alerts. This caused approximately 85% of update request and approval request notifications to be delayed for roughly 13 hours. No data was lost—all notifications were ultimately delivered once the system recovered. We have since implemented automated recovery mechanisms and are adding safeguards to prevent oversized requests from impacting the notification pipeline in the future.

**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.

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.

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.

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.

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.