Smartsheet Outage History

Started Oct 01, 2026, 05:03 PM UTC· resolved Oct 01, 2026, 10:26 PM UTC

1. identified Oct 01, 2026, 05:03 PM UTC

   We have identified issues impacting both automated and manual approval workflows. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. identified Oct 01, 2026, 06:20 PM UTC

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

3. identified Oct 01, 2026, 07:49 PM UTC

   The initial root cause of the issue has been identified and is now resolved. We are working through a backlog of update and approval workflow creations so there may continue to be a delay in delivery.

4. monitoring Oct 01, 2026, 08:14 PM UTC

   The outage is resolved, and new update and approval requests are processing normally. A small delay may persist while backlogged requests from the past two hours finish processing.

5. resolved Oct 01, 2026, 10:26 PM UTC

   This incident has been fully resolved, and all backlogged requests have been processed and sent.

6. postmortem Oct 13, 2026, 04:44 AM UTC

   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.

Read the full incident report →

Started Sep 21, 2026, 10:21 PM UTC· resolved Sep 22, 2026, 03:43 AM UTC

1. investigating Sep 21, 2026, 10:21 PM UTC

   We are investigating an issue where some customers encounter an intermittent blank page or the error "upstream request timeout" attempting to access the Smartsheet Login page at app.smartsheet.com. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. monitoring Sep 21, 2026, 10:40 PM UTC

   We are observing stability being restored for Smartsheet Login. We are continuing to monitor it closely to confirm full service stability. We will provide frequent updates until we reach a resolved status.

3. resolved Sep 22, 2026, 03:43 AM UTC

   Smartsheet Login functionality has been fully restored and is operating normally. The incident is now resolved.

4. postmortem Oct 06, 2026, 03:44 PM UTC

   On September 21, 2026, Smartsheet experienced intermittent login page loading issues across three regions between 11:42 AM and 3:30 PM PDT, impacting Australia from 11:42 AM to 12:34 PM PDT, Europe from 2:05 PM to 3:00 PM PDT, and the United States from 2:05 PM to 3:30 PM PDT. The issue was triggered during scheduled security maintenance on egress firewalls, where default load balancer routing maintained long-lived proxy connections to rebooting appliances rather than resetting and redirecting them immediately to healthy instances. Consequently, approximately 12% to 20% of users attempting to load the login page during these regional windows experienced intermittent timeouts, while existing authenticated user sessions remained unaffected and no data integrity was compromised. Service fully recovered across all regions by 3:30 PM PDT as connections refreshed, and automated TCP connection-reset configurations are being enabled on load balancers to ensure seamless failover during any future appliance maintenance.

Read the full incident report →

Started Sep 16, 2026, 10:36 AM UTC· resolved Sep 16, 2026, 09:02 PM UTC

1. investigating Sep 16, 2026, 10:36 AM UTC

   We are currently investigating this issue. Services related to Support ticket creation may also expericence issues. Our team is actively working on a resolution and will share updates until the issue reaches monitoring status.

2. identified Sep 16, 2026, 11:27 AM UTC

   This issue has been identified and a fix is being implemented in coordination with our partners.

3. monitoring Sep 16, 2026, 12:40 PM UTC

   A fix rollout is in progress. We will continue to provide updates as we monitor impact.

4. monitoring Sep 16, 2026, 03:31 PM UTC

   We are observing stability being restored for the Salesforce Connector and creating Support Cases through the Customer Support Portal. We are continuing to monitor it closely to confirm full service stability. We will provide frequent updates until we reach a resolved status.

5. monitoring Sep 16, 2026, 06:51 PM UTC

   We are observing continued stability for the Salesforce Connector and Customer Support Portal. We will continue to monitor it closely to confirm full service stability. We will provide frequent updates until we reach a resolved status.

6. resolved Sep 16, 2026, 09:02 PM UTC

   The Salesforce Connector and Customer Support Portal functionality have been fully restored and are operating normally. The incident is now resolved.

7. postmortem Sep 23, 2026, 04:50 PM UTC

   On September 16th, 2026, starting at approximately 3:36 AM PDT, customers began experiencing intermittent errors with the Salesforce Connector and with creating cases through the Customer Support Portal. The issue was caused by a widespread outage at our upstream CRM service provider, which affected instance stability and API availability across multiple regions. Our team began monitoring the provider's status closely once impact was confirmed and worked in parallel with them as they rolled out a fix fleetwide. The rollout proceeded in stages and needed to be reapplied to a subset of instances before it fully took hold, which is why customers continued to see intermittent errors throughout the morning even as conditions improved. By 11:51 AM PDT we were observing sustained stability, and our upstream provider confirmed full resolution on their end at approximately 11:59 AM PDT. We confirmed the Salesforce Connector and Customer Support Portal were fully restored and operating normally by 2:02 PM PDT. Some customers who had connectors actively refreshing credentials during the outage window may have been left with an expired authentication token as a residual effect, since our provider's authentication endpoint was also impacted. Affected customers can resolve this by reconnecting the Salesforce Connector to obtain a fresh token and re-enabling any workflows that were disabled as a result.

Read the full incident report →

Started Sep 11, 2026, 08:20 PM UTC· resolved Sep 11, 2026, 11:29 PM UTC

1. investigating Sep 11, 2026, 08:20 PM UTC

   We're currently investigating reports of login and access failures affecting all users, with the app displaying the error "We're having trouble reaching Smartsheet right now." Our team is actively working on a resolution and will share frequent updates until the issue reaches monitoring status.

2. identified Sep 11, 2026, 08:50 PM UTC

   We've identified the issue and implemented a change, which has resulted in Smartsheet loading and users being able to log in successfully. However, an error message is still appearing on the home screen during a hard refresh. Our team is continuing to investigate this remaining issue and will provide updates as we work toward full resolution.

3. monitoring Sep 11, 2026, 09:24 PM UTC

   The change we implemented has resolved the login and access issues, and Smartsheet is now loading successfully for all users. Things appear stable at this time. We are continuing to monitor the situation closely and will provide an update once we've confirmed full resolution.

4. resolved Sep 11, 2026, 11:29 PM UTC

   This incident has been resolved.

5. postmortem Sep 18, 2026, 03:14 PM UTC

   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.

Read the full incident report →

Started Sep 11, 2026, 08:18 PM UTC· resolved Sep 11, 2026, 08:33 PM UTC

1. investigating Sep 11, 2026, 08:18 PM UTC

   We are currently investigating reports of login failing for all users, showing an 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. investigating Sep 11, 2026, 08:21 PM UTC

   We are continuing to investigate this issue.

Read the full incident report →

Started Aug 27, 2026, 01:33 PM UTC· resolved Aug 27, 2026, 03:53 PM UTC

1. investigating Aug 27, 2026, 01:33 PM UTC

   We are investigating an outage impacting login, sheet access, Control Center, and Dynamic View. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. monitoring Aug 27, 2026, 01:52 PM UTC

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

3. resolved Aug 27, 2026, 03:53 PM UTC

   This incident has been resolved.

4. postmortem Sep 11, 2026, 04:20 AM UTC

   Between August 26 and August 28, 2026, customers experienced intermittent issues logging in to Smartsheet and loading sheets, Dashboards, Reports, and certain premium applications, including Control Center, Dynamic View, WorkApps, and Resource Management. The most significant disruption occurred on August 26, lasting approximately 3 hours and 56 minutes, from 12:21 to 16:17 UTC. A shorter recurrence affected customers for approximately 47 minutes on August 27, from 13:03 to 13:50 UTC. A smaller number of customers in our European region experienced a brief period of similar impact on August 28, lasting under 30 minutes, before the issue was fully and permanently resolved. Customers in our Australia and Government regions were not affected at any point during this incident. The underlying cause traced back to a routine change to an internal feature setting. That change had an unintended side effect: it exposed a software defect that caused customers' browsers to send a large, unexpected volume of diagnostic messages back to our servers. Because each of these messages required a standard identity check, they placed significant additional strain on the systems responsible for verifying that users were properly logged in. The sudden surge overwhelmed the systems and as a result, verification requests began timing out — which is what caused the login and access errors customers experienced. Our engineering teams responded quickly by adding capacity to the affected systems between 14:55 and 15:45 UTC on August 26, which restored access by 16:17 UTC that same day. However, that added capacity was not preserved in our standard configuration, so a routine software deployment at approximately 06:11 UTC on August 27 reset it, allowing the same conditions to briefly recur beginning at 13:03 UTC that day; we again resolved it by restoring capacity, with service fully stable by 13:50 UTC. On August 28, at approximately 08:50 UTC, we identified the true root cause — the feature-setting change — and deployed a permanent fix by 13:00 UTC that corrected the underlying defect, fully resolving the issue across all regions by 14:51 UTC. To prevent a recurrence, we are hardening our authentication subsystem to handle such request spikes with autoscaling, faster failure detection, request throttling and load-shedding. We are also strengthening our internal review process for feature-related changes to catch this class of issue before it reaches production. We know how disruptive this incident was, and we sincerely apologize for the impact on you and your business. We remain committed to learning from this event and continuing to invest in the reliability our customers depend on.

Read the full incident report →

Started Aug 26, 2026, 01:28 PM UTC· resolved Aug 26, 2026, 06:23 PM UTC

1. investigating Aug 26, 2026, 01:28 PM UTC

   We're investigating an issue where some sheets in the US Smartsheet instance are failing to load. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. investigating Aug 26, 2026, 02:39 PM UTC

   We're still investigating an issue where some sheets in the US Smartsheet instance are failing to load. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

3. investigating Aug 26, 2026, 03:17 PM UTC

   We're still investigating an issue where some sheets in the US Smartsheet instance are failing to load. This issue is also impacting Reports and Dashboards, as well as Premium Apps including Dynamic View, WorkApps, and Resource Management. Our team remains fully engaged in addressing the situation. We will continue to provide frequent updates until we reach a monitoring status.

4. investigating Aug 26, 2026, 03:47 PM UTC

   We are continuing to investigate this issue.

5. identified Aug 26, 2026, 04:08 PM UTC

   We have implemented a fix to mitigate the issue causing sheets in the US Smartsheet instance to fail to load, as well as the impact on Reports, Dashboards, and Premium Apps (Dynamic View, WorkApps, Resource Management, and Control Center). System metrics are currently showing recovery, and our team is actively monitoring the service to ensure full stability. We will post further updates until the incident is fully resolved.

6. monitoring Aug 26, 2026, 04:22 PM UTC

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

7. resolved Aug 26, 2026, 06:23 PM UTC

   This incident has been resolved.

8. postmortem Sep 11, 2026, 04:19 AM UTC

   Between August 26 and August 28, 2026, customers experienced intermittent issues logging in to Smartsheet and loading sheets, Dashboards, Reports, and certain premium applications, including Control Center, Dynamic View, WorkApps, and Resource Management. The most significant disruption occurred on August 26, lasting approximately 3 hours and 56 minutes, from 12:21 to 16:17 UTC. A shorter recurrence affected customers for approximately 47 minutes on August 27, from 13:03 to 13:50 UTC. A smaller number of customers in our European region experienced a brief period of similar impact on August 28, lasting under 30 minutes, before the issue was fully and permanently resolved. Customers in our Australia and Government regions were not affected at any point during this incident. The underlying cause traced back to a routine change to an internal feature setting. That change had an unintended side effect: it exposed a software defect that caused customers' browsers to send a large, unexpected volume of diagnostic messages back to our servers. Because each of these messages required a standard identity check, they placed significant additional strain on the systems responsible for verifying that users were properly logged in. The sudden surge overwhelmed the systems and as a result, verification requests began timing out — which is what caused the login and access errors customers experienced. Our engineering teams responded quickly by adding capacity to the affected systems between 14:55 and 15:45 UTC on August 26, which restored access by 16:17 UTC that same day. However, that added capacity was not preserved in our standard configuration, so a routine software deployment at approximately 06:11 UTC on August 27 reset it, allowing the same conditions to briefly recur beginning at 13:03 UTC that day; we again resolved it by restoring capacity, with service fully stable by 13:50 UTC. On August 28, at approximately 08:50 UTC, we identified the true root cause — the feature-setting change — and deployed a permanent fix by 13:00 UTC that corrected the underlying defect, fully resolving the issue across all regions by 14:51 UTC. To prevent a recurrence, we are hardening our authentication subsystem to handle such request spikes with autoscaling, faster failure detection, request throttling and load-shedding. We are also strengthening our internal review process for feature-related changes to catch this class of issue before it reaches production. We know how disruptive this incident was, and we sincerely apologize for the impact on you and your business. We remain committed to learning from this event and continuing to invest in the reliability our customers depend on.

Read the full incident report →

Started Aug 25, 2026, 08:45 PM UTC· resolved Aug 26, 2026, 12:23 AM UTC

1. investigating Aug 25, 2026, 08:45 PM UTC

   We are investigating delays or failures impacting Cell Links and Cross Sheet References. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. investigating Aug 25, 2026, 09:25 PM UTC

   We are still investigating this issue. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

3. identified Aug 25, 2026, 10:09 PM UTC

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

4. monitoring Aug 25, 2026, 10:23 PM UTC

   A fix has been implemented and we are monitoring the service for ensured stability.

5. resolved Aug 26, 2026, 12:23 AM UTC

   This incident has been resolved.

6. postmortem Sep 17, 2026, 11:30 PM UTC

   Between August 24 and August 28, 2026, a performance optimization caused certain formulas and cross-sheet references to evaluate incorrectly or produce errors following row insertions or deletions. The root cause was an asynchronous calculation change that performed partial data loads, omitting dependent cells and silently persisting inaccurate formula values. The issue was mitigated on August 27 at 11:25 AM PDT by disabling the optimization flags, with full data restoration completed on August 28 after recalculating approximately all affected known sheets. Preventive measures include enforcing dependency coverage safeguards and adding automated test suites for structural sheet edits. Another event also caused the same issues. On August 25, 2026 \(starting at ~19:43 UTC\), an unprecedented update fanout from a single high-connectivity source sheet overwhelmed the backend Grid Service with approximately update attempts in the thousands, leading to database connection spikes and 502 Bad Gateway errors that left destination sheets with stale cell links and cross-sheet references. Engineering mitigated the propagation by blocking the problematic source sheet on August 26, 2026. A comprehensive, two-phase bulk inbound refresh was subsequently executed across affected unique destination sheets starting on August 26 at 19:14 UTC and successfully concluding on August 27, 2026 at 11:07 UTC, restoring live link consistency across active sheets. We continue to prioritize investments to scale our networking, compute, security, and other infrastructure, and in the technical management processes that enable us to consistently deliver against that commitment. While we cannot promise a future free of any technical challenges, we promise that we will do whatever it takes 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.

Read the full incident report →

Started Aug 11, 2026, 07:51 PM UTC· resolved Aug 11, 2026, 11:20 PM UTC

1. investigating Aug 11, 2026, 07:51 PM UTC

   We are investigating issues with Sheets, Reports, and Workflows. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. investigating Aug 11, 2026, 08:26 PM UTC

   We're continuing to look into this and are working toward a mitigation that we expect to have in place soon.

3. monitoring Aug 11, 2026, 09:02 PM UTC

   A mitigation is now in place, and we're seeing a strong recovery. We'll continue monitoring closely to confirm the issue is fully resolved.

4. resolved Aug 11, 2026, 11:20 PM UTC

   This incident has been resolved.

5. postmortem Aug 19, 2026, 10:38 PM UTC

   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.

Read the full incident report →

Started Jul 30, 2026, 02:54 PM UTC· resolved Jul 30, 2026, 05:41 PM UTC

1. investigating Jul 30, 2026, 02:54 PM UTC

   We are investigating slowness and timeout errors in Smartsheet, impacting sheets, premium apps, connectors, and API. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. identified Jul 30, 2026, 03:26 PM UTC

   We have identified the issue responsible for the Smartsheet slowness and timeout issue and are implementing a fix. We will provide frequent updates until we reach a monitoring status.

3. monitoring Jul 30, 2026, 03:40 PM UTC

   We are observing stability being restored for Smartsheet, Premium Apps, Connectors, and API. We are continuing to monitor it closely to confirm full service stability. We will provide an update once resolution is confirmed.

4. monitoring Jul 30, 2026, 03:42 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Jul 30, 2026, 05:41 PM UTC

   This incident has been resolved.

6. postmortem Aug 20, 2026, 05:23 PM UTC

   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.

Read the full incident report →

Started Jul 15, 2026, 09:23 AM UTC· resolved Jul 15, 2026, 09:55 AM UTC

1. investigating Jul 15, 2026, 09:23 AM UTC

   We are currently investigating an issue preventing Smartsheet US from successfully loading. Attempts to log in to Smartsheet US or access items may result in loading screens that do not complete. We will provide an update in 30 minutes.

2. identified Jul 15, 2026, 09:38 AM UTC

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

3. monitoring Jul 15, 2026, 09:44 AM UTC

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

4. resolved Jul 15, 2026, 09:55 AM UTC

   This incident has been resolved.

5. postmortem Jul 17, 2026, 01:22 AM UTC

   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.

Read the full incident report →

Started Jun 24, 2026, 09:51 PM UTC· resolved Jun 25, 2026, 05:45 AM UTC

1. investigating Jun 24, 2026, 09:51 PM UTC

   We are investigating reports of missing or delayed Update / Approval Requests notifications and emails via Automated Workflows as well as manual trigger. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

2. identified Jun 24, 2026, 11:04 PM UTC

   The issue causing missing or delayed Update / Approval Requests notifications and emails has been identified. Our team is implementing a fix. We will provide frequent updates until we reach a monitoring status.

3. monitoring Jun 25, 2026, 12:43 AM UTC

   A fix has been implemented to resolve the missing or delayed Update / Approval Requests notifications and emails and we are monitoring the results.

4. resolved Jun 25, 2026, 05:45 AM UTC

   This incident has been resolved.

5. postmortem Jul 17, 2026, 11:16 PM UTC

   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.

Read the full incident report →

Started Jun 18, 2026, 09:42 PM UTC· resolved Jul 08, 2026, 08:46 PM UTC

1. identified Jun 18, 2026, 09:42 PM UTC

   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.

2. monitoring Jun 23, 2026, 07:44 AM UTC

   We have implemented measures to address the increased spam activity with Smartsheet public forms. We will continue monitoring and make further adjustments as needed. If you are continuing to see a high rate of spam submissions, please contact our support team so that we can investigate further.

3. resolved Jul 08, 2026, 08:46 PM UTC

   This is now resolved. We are still actively monitoring spam levels as an ongoing and evolving strategy. We encourage all customers to submit support tickets for any residual spam coming through so we can continue to fine tune our solutions.

4. postmortem Jul 17, 2026, 11:14 PM UTC

   Starting in late May, we observed a marked increase in volume and sophistication of spam submissions to public Smartsheet Forms \(forms available to the general public and not requiring a Smartsheet login\), even with the Captcha setting enabled. This resulted in some customers experiencing an increase in unwanted spam content, frequently containing cryptocurrency or phishing links, delivered into their sheets. The activity was generated by automated bots operating through anonymized networks and proxy services. This primarily impacted but was not limited to the US region. Once the abuse was identified, we evaluated, deployed, tested, and tuned a series of protective measures over the following weeks. Because automated abuse of this kind adapts over time, addressing it requires an iterative approach: we layered multiple protections in both forms, captcha service, and the underlying infrastructure, evaluated their effectiveness against live traffic, and refined them as we learned more, adjusting or replacing measures that proved less effective. Throughout this process we also monitored and worked to correct any unintended impact to legitimate form submissions which may have occurred during this period. Automated spam is now substantially blocked down to virtually zero pass through rate and with minimal or no impact on legitimate submissions. We are also actively bringing similar protections into the Smartsheet Gov environment. As of 1:46PT, July 8th, we marked this issue as resolved. If you are still observing spam submissions please first ensure you have Captcha enabled on the form. If Captcha is enabled and you are still seeing spam, please submit a report using the “report abuse” link on your form. We always recommend applying the [highest level of forms security restriction](https://help.smartsheet.com/articles/2481836-manage-form-display-and-submission-options#toc-security) compatible with your solution and if necessary enforce [form security from the admin center](https://help.smartsheet.com/articles/2483290-apply-security-settings-forms). We will continue to monitor, tune, and strengthen these protections ongoing. This includes changes to have Captcha enabled by default for all new forms and new administrative controls rolling out for system admins to have the ability to enforce Captcha for forms managed by their plan. 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.

Read the full incident report →

Started Jun 10, 2026, 10:21 PM UTC· resolved Jun 11, 2026, 11:02 AM UTC

1. investigating Jun 10, 2026, 10:21 PM UTC

   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. identified Jun 11, 2026, 12:51 AM UTC

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

3. monitoring Jun 11, 2026, 03:30 AM UTC

   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. resolved Jun 11, 2026, 11:02 AM UTC

   This incident has been resolved.

5. postmortem Aug 14, 2026, 06:51 PM UTC

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

Read the full incident report →

Started Jun 03, 2026, 08:28 PM UTC· resolved Jun 05, 2026, 11:53 PM UTC

1. investigating Jun 03, 2026, 08:28 PM UTC

   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. investigating Jun 03, 2026, 09:10 PM UTC

   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.

3. identified Jun 03, 2026, 09:41 PM UTC

   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.

4. identified Jun 03, 2026, 10:16 PM UTC

   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

5. investigating Jun 03, 2026, 10:26 PM UTC

   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.

6. investigating Jun 03, 2026, 10:59 PM UTC

   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.

7. identified Jun 03, 2026, 11:36 PM UTC

   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.

8. identified Jun 04, 2026, 12:06 AM UTC

   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.

9. identified Jun 04, 2026, 12:47 AM UTC

   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.

10. identified Jun 04, 2026, 01:16 AM UTC

    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.

11. identified Jun 04, 2026, 01:45 AM UTC

    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.

12. identified Jun 04, 2026, 02:14 AM UTC

    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.

13. identified Jun 04, 2026, 12:25 PM UTC

    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.

14. identified Jun 04, 2026, 03:44 PM UTC

    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.

15. identified Jun 04, 2026, 09:26 PM UTC

    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.

16. identified Jun 04, 2026, 11:01 PM UTC

    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.

17. identified Jun 05, 2026, 02:07 AM UTC

    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.

18. identified Jun 05, 2026, 04:15 AM UTC

    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.

19. identified Jun 05, 2026, 08:15 AM UTC

    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.

20. identified Jun 05, 2026, 10:15 AM UTC

    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.

21. identified Jun 05, 2026, 12:34 PM UTC

    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.

22. monitoring Jun 05, 2026, 07:53 PM UTC

    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.

23. resolved Jun 05, 2026, 11:53 PM UTC

    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.

24. postmortem Jun 09, 2026, 11:07 PM UTC

    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.

Read the full incident report →

Started May 27, 2026, 05:50 PM UTC· resolved May 28, 2026, 12:51 AM UTC

1. investigating May 27, 2026, 05:50 PM UTC

   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. monitoring May 27, 2026, 08:37 PM UTC

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

3. monitoring May 27, 2026, 08:39 PM UTC

   We are continuing to monitor for any further issues.

4. resolved May 28, 2026, 12:51 AM UTC

   This incident has been resolved.

5. postmortem Jun 23, 2026, 11:35 PM UTC

   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.

Read the full incident report →

Started Apr 22, 2026, 04:45 PM UTC· resolved Apr 22, 2026, 07:20 PM UTC

1. investigating Apr 22, 2026, 04:45 PM UTC

   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. identified Apr 22, 2026, 05:01 PM UTC

   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. monitoring Apr 22, 2026, 05:09 PM UTC

   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. resolved Apr 22, 2026, 07:20 PM UTC

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

5. postmortem Apr 29, 2026, 03:48 PM UTC

   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.

Read the full incident report →

Started Apr 17, 2026, 07:23 PM UTC· resolved Apr 18, 2026, 12:07 AM UTC

1. investigating Apr 17, 2026, 07:23 PM UTC

   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. monitoring Apr 17, 2026, 07:35 PM UTC

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

3. resolved Apr 18, 2026, 12:07 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 13, 2026, 04:33 PM UTC· resolved Apr 13, 2026, 08:46 PM UTC

1. investigating Apr 13, 2026, 04:33 PM UTC

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

2. investigating Apr 13, 2026, 05:06 PM UTC

   We are continuing to investigate this issue.

3. investigating Apr 13, 2026, 05:52 PM UTC

   We are continuing to investigate this issue.

4. monitoring Apr 13, 2026, 06:31 PM UTC

   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.

5. resolved Apr 13, 2026, 08:46 PM UTC

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

6. postmortem Apr 14, 2026, 02:26 PM UTC

   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.

Read the full incident report →

Started Mar 31, 2026, 06:53 PM UTC· resolved Mar 31, 2026, 10:01 PM UTC

1. investigating Mar 31, 2026, 06:53 PM UTC

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

2. identified Mar 31, 2026, 07:35 PM UTC

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

3. monitoring Mar 31, 2026, 08:11 PM UTC

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

4. resolved Mar 31, 2026, 10:01 PM UTC

   This incident has been resolved.

5. postmortem Apr 13, 2026, 11:13 PM UTC

   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.

Read the full incident report →

Started Mar 24, 2026, 03:16 PM UTC· resolved Mar 24, 2026, 06:30 PM UTC

1. investigating Mar 24, 2026, 03:16 PM UTC

   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. identified Mar 24, 2026, 04:07 PM UTC

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

3. monitoring Mar 24, 2026, 04:08 PM UTC

   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. resolved Mar 24, 2026, 06:30 PM UTC

   This incident has been resolved.

5. postmortem Apr 03, 2026, 11:20 PM UTC

   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.

Read the full incident report →

Started Mar 03, 2026, 05:16 PM UTC· resolved Mar 04, 2026, 11:42 PM UTC

1. investigating Mar 03, 2026, 05:16 PM UTC

   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. identified Mar 03, 2026, 05:47 PM UTC

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

3. identified Mar 03, 2026, 05:52 PM UTC

   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. monitoring Mar 03, 2026, 06:19 PM UTC

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

5. resolved Mar 04, 2026, 11:42 PM UTC

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

6. postmortem Mar 13, 2026, 11:53 PM UTC

   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.

Read the full incident report →

Started Feb 27, 2026, 09:55 PM UTC· resolved Mar 24, 2026, 05:57 PM UTC

1. identified Feb 27, 2026, 09:55 PM UTC

   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. identified Mar 03, 2026, 03:55 PM UTC

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

3. identified Mar 09, 2026, 04:38 PM UTC

   We are continuing to work on restoring full service.

4. identified Mar 12, 2026, 09:08 PM UTC

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

5. identified Mar 16, 2026, 07:05 PM UTC

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

6. monitoring Mar 24, 2026, 03:02 PM UTC

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

7. resolved Mar 24, 2026, 05:57 PM UTC

   This incident has been resolved.

8. postmortem Mar 25, 2026, 03:05 AM UTC

   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.

Read the full incident report →

Started Feb 22, 2026, 12:17 PM UTC· resolved Feb 22, 2026, 02:45 PM UTC

1. investigating Feb 22, 2026, 12:17 PM UTC

   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. monitoring Feb 22, 2026, 12:40 PM UTC

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

3. resolved Feb 22, 2026, 02:45 PM UTC

   This incident has been resolved.

4. postmortem Mar 07, 2026, 01:02 AM UTC

   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.

Read the full incident report →

Started Feb 17, 2026, 04:08 PM UTC· resolved Feb 17, 2026, 06:55 PM UTC

1. investigating Feb 17, 2026, 04:08 PM UTC

   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. monitoring Feb 17, 2026, 04:29 PM UTC

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

3. resolved Feb 17, 2026, 06:55 PM UTC

   This incident has been resolved.

4. postmortem Feb 19, 2026, 01:49 PM UTC

   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.

Read the full incident report →