{
"vendor": "Smartsheet",
"slug": "smartsheet",
"platform": "statuspage",
"status_url": "https://status.smartsheet.com",
"last_checked": "2026-09-16T12:28:20Z",
"last_state": "degraded",
"history_backfilled": true,
"first_watched": "2026-09-04T07:06:16Z",
"incidents": [
{
"body": "This issue has been identified and a fix is being implemented in coordination with our partners.",
"first_seen": "2026-09-16T12:28:20Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"started_at": "2026-09-16T03:36:37.181-07:00",
"state": "identified",
"title": "Salesforce connector is experiencing intermittent issues",
"updated_at": "2026-09-16T04:27:52.788-07:00",
"url": "https://stspg.io/p2bsj2rqyxx9"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-12T12:30:15Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-09-11T16:29:54.581-07:00",
"resolved_inferred": false,
"started_at": "2026-09-11T13:20:28.379-07:00",
"state": "resolved",
"title": "Smartsheet and Smartsheet Login Unavailable for Smartsheet US",
"updated_at": "2026-09-11T16:29:54.598-07:00",
"url": "https://stspg.io/rljmp4ztkybb"
},
{
"body": "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.\n\nThe 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 \u2014 which is what caused the login and access errors customers experienced.\n\nOur 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 \u2014 the feature-setting change \u2014 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.\n\nTo 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-27T08:53:21.635-07:00",
"resolved_inferred": false,
"started_at": "2026-08-27T06:33:29.675-07:00",
"state": "postmortem",
"title": "Unexpected HTTP response code affecting login, sheet access, Control Center, Dynamic View and other premium apps",
"updated_at": "2026-09-10T21:20:07.702-07:00",
"url": "https://stspg.io/y1r6gdt3yg08"
},
{
"body": "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.\n\nThe 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 \u2014 which is what caused the login and access errors customers experienced.\n\nOur 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 \u2014 the feature-setting change \u2014 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.\n\nTo 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-26T11:23:43.006-07:00",
"resolved_inferred": false,
"started_at": "2026-08-26T06:28:27.287-07:00",
"state": "postmortem",
"title": "Sheets in Smartsheet US are failing to load",
"updated_at": "2026-09-10T21:19:45.248-07:00",
"url": "https://stspg.io/9cmq02rdjgvb"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-25T17:23:03.265-07:00",
"resolved_inferred": false,
"started_at": "2026-08-25T13:45:29.799-07:00",
"state": "resolved",
"title": "Intermittent Cell Link and Cross Sheet Reference delays/failures",
"updated_at": "2026-08-25T17:23:03.295-07:00",
"url": "https://stspg.io/9sqz47rrrh2c"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-11T16:20:07.426-07:00",
"resolved_inferred": false,
"started_at": "2026-08-11T12:51:45.273-07:00",
"state": "postmortem",
"title": "Sheets, Reports, and Workflow Services Are Impacted",
"updated_at": "2026-08-19T15:39:11.802-07:00",
"url": "https://stspg.io/vrp68skyl8qq"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-30T10:41:40.968-07:00",
"resolved_inferred": false,
"started_at": "2026-07-30T07:54:23.720-07:00",
"state": "postmortem",
"title": "Smartsheet Slowness and Timeout Errors",
"updated_at": "2026-08-20T10:24:14.181-07:00",
"url": "https://stspg.io/hl4qwzynvx74"
},
{
"body": "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.  \nDuring this period, affected requests may have failed. The issue was identified and corrected, and normal operation was restored.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-15T02:55:36.715-07:00",
"resolved_inferred": false,
"started_at": "2026-07-15T02:23:07.351-07:00",
"state": "postmortem",
"title": "Smartsheet US is not loading",
"updated_at": "2026-07-16T18:22:41.126-07:00",
"url": "https://stspg.io/w4z44rdbk7fp"
},
{
"body": "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\u2014all 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-24T22:45:27.383-07:00",
"resolved_inferred": false,
"started_at": "2026-06-24T14:51:24.289-07:00",
"state": "postmortem",
"title": "Investigating missing or delayed Update / Approval Requests notifications and emails",
"updated_at": "2026-07-17T16:16:56.706-07:00",
"url": "https://stspg.io/wv3g5tdz1jqd"
},
{
"body": "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.\n\nOnce 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.\n\nIf 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 \u201creport abuse\u201d 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).\n\nWe 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.\n\nWe 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 \u2014 and your continued trust in Smartsheet \u2014 depends on it.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-08T13:46:37.985-07:00",
"resolved_inferred": false,
"started_at": "2026-06-18T14:42:11.112-07:00",
"state": "postmortem",
"title": "Increased spam activity with Smartsheet Forms",
"updated_at": "2026-07-17T16:16:25.584-07:00",
"url": "https://stspg.io/0kkdfjb9pnyp"
},
{
"body": "**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 \u2014 no customer data was lost.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-11T04:02:55.489-07:00",
"resolved_inferred": false,
"started_at": "2026-06-10T15:21:49.071-07:00",
"state": "postmortem",
"title": "Smartsheet add-ons for Google is not working",
"updated_at": "2026-08-14T11:54:29.794-07:00",
"url": "https://stspg.io/7s12m1dw8035"
},
{
"body": "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.\n\nOur 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.\n\nWe 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-05T16:53:42.652-07:00",
"resolved_inferred": false,
"started_at": "2026-06-03T13:28:16.873-07:00",
"state": "postmortem",
"title": "Investigating assets unexpectedly moved from Folders to the Parent Workspace",
"updated_at": "2026-06-09T16:08:54.337-07:00",
"url": "https://stspg.io/47sb3df10lvy"
},
{
"body": "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.\n\nTo prevent recurrence, we are implementing changes to:\n\n* Redesign how column option data is fetched to reduce load.\n* Better distributing database traffic and protecting database capacity during periods of high usage.\n* Improving monitoring and tooling to detect and respond to issues faster.\n\nWe 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\u2014and your continued trust in Smartsheet\u2014depends on it.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-27T17:51:22.778-07:00",
"resolved_inferred": false,
"started_at": "2026-05-27T10:50:07.515-07:00",
"state": "postmortem",
"title": "Sheets Not Loading/Opening \u2013 \"Trouble Reaching Smartsheet\" Error",
"updated_at": "2026-06-23T16:35:54.168-07:00",
"url": "https://stspg.io/61pn0mr7ks4s"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-22T12:20:06.215-07:00",
"resolved_inferred": false,
"started_at": "2026-04-22T09:45:46.295-07:00",
"state": "postmortem",
"title": "Investigating Workspace panel not opening or closing unexpectedly",
"updated_at": "2026-04-29T08:52:42.721-07:00",
"url": "https://stspg.io/8mm5692kl3jr"
},
{
"body": "This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-17T17:07:22.518-07:00",
"resolved_inferred": false,
"started_at": "2026-04-17T12:23:40.421-07:00",
"state": "resolved",
"title": "Smartsheet's Resource Management Integration Loading Issues",
"updated_at": "2026-04-17T17:07:22.538-07:00",
"url": "https://stspg.io/fdr449sfg01c"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-13T13:46:58.843-07:00",
"resolved_inferred": false,
"started_at": "2026-04-13T09:33:38.682-07:00",
"state": "postmortem",
"title": "Failures during Form Submissions",
"updated_at": "2026-04-14T07:27:19.156-07:00",
"url": "https://stspg.io/r2bsl4ll5n5y"
},
{
"body": "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\n\nTo prevent recurrence, we are conducting a post-incident review focused on improving monitoring and alerting for licensing issues as well bolstering deployment stability.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-31T15:01:16.145-07:00",
"resolved_inferred": false,
"started_at": "2026-03-31T11:53:41.706-07:00",
"state": "postmortem",
"title": "Proof Performance and Watermarks",
"updated_at": "2026-04-13T16:13:27.406-07:00",
"url": "https://stspg.io/t6x0vn34jryk"
},
{
"body": "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 \u2014 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.\n\nTo 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-24T11:30:07.060-07:00",
"resolved_inferred": false,
"started_at": "2026-03-24T08:16:51.905-07:00",
"state": "postmortem",
"title": "User & Group Management",
"updated_at": "2026-04-03T16:21:03.369-07:00",
"url": "https://stspg.io/npqm0b0cf12v"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-04T15:42:29.443-08:00",
"resolved_inferred": false,
"started_at": "2026-03-03T09:16:41.432-08:00",
"state": "postmortem",
"title": "Form Submissions issue",
"updated_at": "2026-03-25T16:17:57.410-07:00",
"url": "https://stspg.io/f33vwbhhblqt"
},
{
"body": "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.\n\nEngineering 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.\n\nTo 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-24T10:57:19.514-07:00",
"resolved_inferred": false,
"started_at": "2026-02-27T13:55:31.941-08:00",
"state": "postmortem",
"title": "Brandfolder Monthly Reports Delayed",
"updated_at": "2026-03-24T20:06:24.075-07:00",
"url": "https://stspg.io/9k6zbycs4m07"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-22T06:45:19.514-08:00",
"resolved_inferred": false,
"started_at": "2026-02-22T04:17:38.179-08:00",
"state": "postmortem",
"title": "PROD-AU home not loading",
"updated_at": "2026-03-06T17:02:36.514-08:00",
"url": "https://stspg.io/h5f0xrc3rrwd"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-17T10:55:12.302-08:00",
"resolved_inferred": false,
"started_at": "2026-02-17T08:08:19.905-08:00",
"state": "postmortem",
"title": "Resource Management Advanced reports failing to create and refresh.",
"updated_at": "2026-02-19T05:50:07.309-08:00",
"url": "https://stspg.io/xdfyr06f5jkd"
},
{
"body": "Starting on Monday, February 9th, 2026 at 12:00PM Pacific Time, users experienced blank pages when accessing some Proof generated links. Our engineering team identified a regression. A fix was fully deployed and full proof functionality was restored for all customers on February 10th, 2026 at 11:00AM Pacific Time. We are reviewing our deployment processes to help prevent similar incidents in the future.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-10T14:17:06.638-08:00",
"resolved_inferred": false,
"started_at": "2026-02-10T11:06:03.659-08:00",
"state": "postmortem",
"title": "Proof links returning a blank screen",
"updated_at": "2026-02-17T16:36:26.834-08:00",
"url": "https://stspg.io/tkjbhv6b2lb3"
},
{
"body": "Around 7:45pm Pacific Time, our engineering team identified errors when accessing Smartsheet or making changes to assets. We made changes to our infrastructure and and observed gradual recovery. Smartsheet fully recovered at 9:33pm Pacific Time.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-01-17T21:36:08.760-08:00",
"resolved_inferred": false,
"started_at": "2026-01-17T21:09:22.503-08:00",
"state": "postmortem",
"title": "Errors Accessing Smartsheet",
"updated_at": "2026-01-17T21:41:39.933-08:00",
"url": "https://stspg.io/ty2q42g3yvvk"
},
{
"body": "On Thursday, December 4th 2025 at 8:08am, users experienced delays in Document Generation requests to download generated documents or attach them to rows. The issue occurred due to increased load on the back end service following a recent code change and was resolved by 11:30am Pacific Time.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-04T13:26:39.791-08:00",
"resolved_inferred": false,
"started_at": "2025-12-04T10:55:33.000-08:00",
"state": "postmortem",
"title": "Document Generation Request Delays",
"updated_at": "2025-12-04T13:31:59.805-08:00",
"url": "https://stspg.io/71303cjzk4qr"
},
{
"body": "On December 2, 2025, at approximately 4:36 AM PST, our primary US email sending account with Sparkpost/Bird was suspended, causing all outgoing email to be held. US customers who rely on email for security and access, specifically those needing to perform password resets or log in using Time-based One-Time Password \\(TOTP\\), were unable to complete these actions. This issue resulted in the delay of over a million emails. The incident was declared at 6:04 AM PST, and the issue was resolved and the held email queue was processed by 8:14 AM PST. The account suspension was triggered by our vendor's compliance team due to reported email abuse originating from a compromised customer account on our platform. The immediate resolution was achieved by rapidly escalating the matter through our direct contacts and commercial legal team, who secured the reactivation of the Sparkpost account. We are implementing several key changes to address the underlying issues:\u00a0\n\n1. Fixing the issue that caused the vendor's critical suspension warning emails to be mistakenly sent to our spam folder, ensuring immediate staff awareness in the future;\u00a0\n\n1. Upgrading our monitoring to immediately detect if emails are queued or held by the vendor, even when our system receives a 'success' confirmation\n\n1. Strengthening user security protocols to prevent compromised accounts from being used for large-scale abuse, including stricter review policies for suspicious user activity.\n\nWe continue to prioritize investments to scale our networking, compute, security, and other infrastructure, as well as our technical management processes that enable us to consistently deliver great experiences for our customers.\n\nWe 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\u2014and your continued trust in Smartsheet\u2014depends on it.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-02T10:40:11.652-08:00",
"resolved_inferred": false,
"started_at": "2025-12-02T06:35:44.421-08:00",
"state": "postmortem",
"title": "Resolved Emails From Smartsheet Not Delivered",
"updated_at": "2025-12-11T14:02:10.772-08:00",
"url": "https://stspg.io/v492zb95q09m"
},
{
"body": "On Monday, November 10th, between 12:35 PM and 5:09 PM PST, some users experienced delays in receiving emails. This issue was identified as a regression caused by a recent deployment to our mailing service.We have rolled back the deployment, and email delivery has fully recovered. All queued emails are now being processed.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-10T17:22:29.894-08:00",
"resolved_inferred": false,
"started_at": "2025-11-10T16:19:30.781-08:00",
"state": "postmortem",
"title": "A few Smartsheet services are not sending out emails",
"updated_at": "2025-11-19T13:25:21.747-08:00",
"url": "https://stspg.io/2yfmys2kbxqb"
},
{
"body": "Beginning at approximately 1:56 PM PDT on October 29, 2025, some customers began experiencing issues accessing https://help.smartsheet.com, due to a disruption with our third-party hosting provider. The fix was fully deployed and service was restored for all customers at approximately 2:50PM PDT.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-29T16:49:15.929-07:00",
"resolved_inferred": false,
"started_at": "2025-10-29T14:17:18.093-07:00",
"state": "postmortem",
"title": "help.smartsheet.com connectivity errors.",
"updated_at": "2025-11-04T09:57:28.779-08:00",
"url": "https://stspg.io/909db0xrw64d"
},
{
"body": "Beginning on October 29th, 2025, from 8:41AM PDT, users experienced Azure/Microsoft login issues. The issue occurred due to a 3rd party authentication service provider. This was resolved by 5:05PM PDT.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-29T18:24:04.274-07:00",
"resolved_inferred": false,
"started_at": "2025-10-29T09:56:00.000-07:00",
"state": "postmortem",
"title": "Investigating errors using Login with Microsoft",
"updated_at": "2025-11-18T12:52:05.634-08:00",
"url": "https://stspg.io/vy4lpw3xg0v3"
},
{
"body": "Starting at approximately 4:41 AM PT on October 27, 2025, some Brandfolder customers experienced intermittent delays in receiving system-generated email notifications, including invitations and notifications, due to a disruption with our third-party email processing provider. \n\nDuring this period, emails may not have been delivered immediately. The issue was quickly identified and resolved, and all services were confirmed fully operational by 6:13 AM PT. Any delayed messages are being delivered, and we do not expect further impact.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-27T07:56:52.410-07:00",
"resolved_inferred": false,
"started_at": "2025-10-27T05:51:38.628-07:00",
"state": "postmortem",
"title": "Brandfolder: SendGrid notifications not processing \"Your account was frozen due to unpaid invoices\"",
"updated_at": "2025-10-29T04:15:50.336-07:00",
"url": "https://stspg.io/xjzs23y82n14"
},
{
"body": "On October 20, 2025, between 12:03 AM and 3:39 PM PDT, Smartsheet customers were unable to access the platform due to an AWS service outage in the US-EAST-1 region. This incident caused a full disruption of Smartsheet services, preventing users from logging in or accessing core features such as sheets, reports, and dashboards.\n\n**Incident Timeline**\n\n* **12:03 AM PDT**: Smartsheet engineering first alerted by system errors\n* **12:11 AM PDT:** AWS announced their investigation of the increased error rates\n* **2:24 AM PDT**: Initial signs of AWS recovery observed; Smartsheet attempts service restoration.\n* **7:14 AM PDT**: AWS experienced a secondary disruption, delaying recovery efforts.\n* **3:01 PM PDT:** AWS services returned to normal operations; Smartsheet begins service restoration.\n* **3:39 PM PDT**: Smartsheet access and functionality restored across all services.\u00a0\n* **6:45 PM PDT**: Smartsheet services stability confirmed and incident resolved.\n\n**Root cause**\n\nInvestigation revealed the root cause to be AWS DNS resolution issues for regional DynamoDB service endpoints in the US-EAST-1 region, which also led to impairment of the EC2 service. This issue disrupted the ability of Smartsheet services to access core platform data, leading to the service interruption experienced by customers.\n\nThe Smartsheet team acted immediately to stabilize the platform once the issue was detected. To maintain performance and prevent further disruption, we temporarily paused core services linked to the affected AWS region while restoration efforts were underway. As AWS services stabilized at 3:01 PM PDT, Smartsheet gradually restored all functionality to ensure a reliable and consistent user experience.\u00a0\n\n**Corrective and preventive actions**\n\nWe understand how critical Smartsheet is to your operations and sincerely apologize for any disruption this incident may have caused. We\u2019re committed to learning from this event and driving improvements to strengthen our reliability. To help prevent similar issues in the future, we are:\n\n* **Evaluating a US cross-region active/passive setup** to enable failover and maintain service availability during infrastructure outages.\n* **Enhancing our notification system** to operate independently from core services, ensuring timely updates and more granular visibility during incidents.\n\nThe delivery timeline for these improvements is currently being finalized.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-20T18:45:54.076-07:00",
"resolved_inferred": false,
"started_at": "2025-10-20T02:53:42.883-07:00",
"state": "postmortem",
"title": "Resolved Connectivity Issue Due to AWS outage",
"updated_at": "2025-10-22T08:32:33.070-07:00",
"url": "https://stspg.io/svzcvzn78l5k"
},
{
"body": "Beginning at approximately 8:44 AM PDT on October 14, 2025, some customers began experiencing issues accessing attachments and rendering previously set conditional formatting or filters. Our engineering team identified that a recent code change was the cause of the issue and deployed a fix. The fix was fully deployed and service was restored for all customers at approximately 9:57 AM PDT. We are reviewing our deployment processes to help prevent similar incidents in the future.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-14T14:10:05.839-07:00",
"resolved_inferred": false,
"started_at": "2025-10-14T09:39:34.428-07:00",
"state": "postmortem",
"title": "Attachments Disabled Message",
"updated_at": "2025-10-28T10:43:55.044-07:00",
"url": "https://stspg.io/ddkknd8cyn5t"
},
{
"body": "**Post Incident Summary:** Beginning at approximately 12:52 PM PDT on October 9, 2025, some customers began experiencing issues uploading attachments through WorkApps. Our engineering team identified that a recent code change was the cause of the issue and deployed a fix. The fix was fully deployed and service was restored for all customers at approximately 10:00 PM PDT. We are reviewing our deployment processes to help prevent similar incidents in the future.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-10T00:31:43.302-07:00",
"resolved_inferred": false,
"started_at": "2025-10-09T17:28:26.254-07:00",
"state": "postmortem",
"title": "Issues Uploading Attachments Through WorkApps",
"updated_at": "2025-10-10T01:35:33.004-07:00",
"url": "https://stspg.io/w1gtb68r8xxx"
},
{
"body": "Table View is a recently launched view within Smartsheet, and we have identified that Workflows and Webhooks where the trigger event is an attachment or comment added on Table View will not run. We are working to build this capability. In the interim, using Grid View will mitigate the issue.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-01T02:53:41.514-07:00",
"resolved_inferred": false,
"started_at": "2025-10-01T02:05:38.718-07:00",
"state": "postmortem",
"title": "Workflows and Webhooks not triggering on attachments or comments",
"updated_at": "2025-10-01T02:54:38.106-07:00",
"url": "https://stspg.io/639xlb2fjjwh"
},
{
"body": "Starting at approximately 9:00 PM PT on September 7, 2025, we began receiving reports of AJAX errors when users attempted to save sheets. The issue was reproducible only for users whose ISPs were located in APAC regions. Monitoring of other regions \\(US, EU\\) did not show similar behavior. A status message was posted to indicate we were investigating potential upstream provider issues. We recommend that users in affected regions check with their ISP, as the issue was not isolated to our service. We continued monitoring throughout the evening of September 8 and during the day on September 9. Reports gradually decreased, and status page traffic also declined. By 6:30 PM PT on September 9, with reports subsiding and no new impact observed, we removed the status message and closed out the incident.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-09T18:30:55.870-07:00",
"resolved_inferred": false,
"started_at": "2025-09-08T20:09:27.668-07:00",
"state": "postmortem",
"title": "Sheet Loading and Saving",
"updated_at": "2025-09-09T20:09:33.802-07:00",
"url": "https://stspg.io/17bt7lg0n0qg"
},
{
"body": "On Wednesday, August 27, 2025, from 6:11 a.m. PDT to 7:47 a.m. PDT, some customers may have experienced slow loading and unresponsiveness within the Data Shuttle UI.\n\nOur engineering teams were immediately alerted and began investigating the issue. They were able to identify and resolve the problem, and full service was restored at 7:47 a.m. PDT.\n\nWe are making improvements based on our learnings from the incident to avoid similar incidents in the future.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-08-27T10:44:02.861-07:00",
"resolved_inferred": false,
"started_at": "2025-08-27T06:43:13.276-07:00",
"state": "postmortem",
"title": "Data Shuttle",
"updated_at": "2025-08-27T10:44:57.775-07:00",
"url": "https://stspg.io/cm7h1dx3ps2n"
},
{
"body": "On August 8th, 2025, starting at 5:15 PM PST, users began experiencing errors and difficulties accessing Smartsheet. By 5:56 PM PST, full service was confirmed to be restored for all users.\n\nOur engineering teams quickly determined that a recent internal service deployment was the cause of Smartsheet's unavailability.\n\nA rollback of this deployment was initiated, and full service was restored by approximately 5:56 PM PST. We are currently reviewing our deployment processes and internal service dependencies to prevent similar issues in the future.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-08-25T20:01:05.364-07:00",
"resolved_inferred": false,
"started_at": "2025-08-25T17:34:46.641-07:00",
"state": "postmortem",
"title": "Smartsheet App Unavailable",
"updated_at": "2025-08-25T20:07:07.926-07:00",
"url": "https://stspg.io/vpx69lvq2nrr"
}
]
}