Unexpected HTTP response code affecting login, sheet access, Control Center, Dynamic View and other premium apps
Started August 27, 2026 at 1:33 PM UTC · 2h 20m
OutageCritical incident
Affected components
ReportsSmartsheet LoginDynamic ViewSheetsCalendarWorkAppsDashboardsControl Center
investigating
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.
monitoring
A fix has been implemented and we are monitoring the results.
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.
investigating
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.
investigating
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.
investigating
We are continuing to investigate this issue.
identified
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.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
This incident has been resolved.
Intermittent Cell Link and Cross Sheet Reference delays/failures
Started August 25, 2026 at 8:45 PM UTC · 3h 38m
IssuesMinor incident
Affected components
Sheets
investigating
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.
investigating
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.
identified
This issue has been identified and a fix is being implemented.
monitoring
A fix has been implemented and we are monitoring the service for ensured stability.
resolved
This incident has been resolved.
Sheets, Reports, and Workflow Services Are Impacted
Started August 11, 2026 at 7:51 PM UTC · 3h 28m
OutageCritical incident
Affected components
ReportsSheetsIn App Workflows
investigating
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.
investigating
We're continuing to look into this and are working toward a mitigation that we expect to have in place soon.
monitoring
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.
resolved
This incident has been resolved.
postmortem
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.
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.
identified
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.
monitoring
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.
monitoring
We are continuing to monitor for any further issues.
resolved
This incident has been resolved.
postmortem
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.
Smartsheet US is not loading
Started July 15, 2026 at 9:23 AM UTC · 32m
OutageMajor incident
Affected components
ReportsSmartsheet LoginFormsSheetsDashboardsSingle Sign On ( Company Credentials )
investigating
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.
identified
The issue has been identified and a fix is being implemented.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
This incident has been resolved.
postmortem
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.
Investigating missing or delayed Update / Approval Requests notifications and emails
Started June 24, 2026 at 9:51 PM UTC · 7h 54m
IssuesMinor incident
Affected components
In App NotificationsEmail Notifications
investigating
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.
identified
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.
monitoring
A fix has been implemented to resolve the missing or delayed Update / Approval Requests notifications and emails and we are monitoring the results.
resolved
This incident has been resolved.
postmortem
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.
Increased spam activity with Smartsheet Forms
Started June 18, 2026 at 9:42 PM UTC · 19d 23h
IssuesMinor incident
Affected components
Forms
identified
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.
monitoring
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.
resolved
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.
postmortem
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.
Smartsheet add-ons for Google is not working
Started June 10, 2026 at 10:21 PM UTC · 12h 41m
OutageMajor incident
Affected components
Third Party Integrations
investigating
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.
identified
The issue has been identified and a fix is being implemented.
monitoring
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.
resolved
This incident has been resolved.
postmortem
**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.
Investigating assets unexpectedly moved from Folders to the Parent Workspace
Started June 3, 2026 at 8:28 PM UTC · 2d 3h
Pending
Affected components
ReportsSheetsDashboards
investigating
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.
identified
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.
identified
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
investigating
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.
identified
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.
identified
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.
identified
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.
identified
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.
identified
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.
identified
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.
identified
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.
identified
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.
identified
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.
monitoring
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.
resolved
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.
postmortem
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.
Sheets Not Loading/Opening – "Trouble Reaching Smartsheet" Error
Started May 27, 2026 at 5:50 PM UTC · 7h 1m
IssuesMinor incident
Affected components
Sheets
investigating
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.
monitoring
A fix has been implemented and we are monitoring the results.
monitoring
We are continuing to monitor for any further issues.
resolved
This incident has been resolved.
postmortem
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.
Investigating Workspace panel not opening or closing unexpectedly
Started April 22, 2026 at 4:45 PM UTC · 2h 34m
IssuesMinor incident
Affected components
Search
investigating
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.
identified
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.
monitoring
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.
resolved
Workspace panel functionality has been fully restored and is operating normally. The incident is now resolved.
postmortem
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.
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.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
This incident has been resolved.
Failures during Form Submissions
Started April 13, 2026 at 4:33 PM UTC · 4h 13m
OutageMajor incident
Affected components
Forms
investigating
We are currently investigating an issue affecting Smartsheet Forms where a subset of users are experiencing failures when submitting forms.
investigating
We are continuing to investigate this issue.
monitoring
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.
resolved
Forms Submissions are operating normally. The incident is now resolved.
postmortem
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.
Proof Performance and Watermarks
Started March 31, 2026 at 6:53 PM UTC · 3h 8m
IssuesMinor incident
Affected components
Document Proofing
investigating
We are currently investigating an issue causing 'EVALUATION MODE' watermarks and slow loading on proofs. We will provide an update in 30 minutes.
identified
The issue has been identified and a fix is being implemented.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
This incident has been resolved.
postmortem
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.
User & Group Management
Started March 24, 2026 at 3:16 PM UTC · 3h 13m
OutageMajor incident
Affected components
User and Group Management
investigating
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.
identified
The issue has been identified and a fix is being implemented.
monitoring
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.
resolved
This incident has been resolved.
postmortem
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.
Form Submissions issue
Started March 3, 2026 at 5:16 PM UTC · 1d 6h
OutageMajor incident
Affected components
Forms
investigating
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.
identified
The issue has been identified and a fix is being implemented.
identified
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.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
Forms Submissions has been fully restored and is operating normally. The incident is now resolved.
postmortem
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.
Brandfolder Monthly Reports Delayed
Started February 27, 2026 at 9:55 PM UTC · 24d 20h
OutageMajor incident
Affected components
Insights
identified
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.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on restoring full service.
identified
A fix is being implemented. An update will be shared once completed.
identified
We are finalizing the fix for this issue and will have an update shortly.
monitoring
We have implemented the fix fully and we are monitoring for stability.
resolved
This incident has been resolved.
postmortem
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.
PROD-AU home not loading
Started February 22, 2026 at 12:17 PM UTC · 2h 28m
OutageCritical incident
Affected components
ReportsDynamic ViewSheetsDashboards
investigating
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.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
This incident has been resolved.
postmortem
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.
Resource Management Advanced reports failing to create and refresh.
Started February 17, 2026 at 4:08 PM UTC · 2h 47m
OutageMajor incident
Affected components
Resource Management
investigating
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.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
This incident has been resolved.
postmortem
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.
Smartsheet outage history and incident timeline | Uptimus