Smartsheet Outage History

Smartsheet experienced missing or delayed Update / Approval Requests notifications and emails, affecting Automated Workflows and manual triggers. This meant users could miss timely updates or confirmations for pending updates and approvals. The disruption began at 9:53 PM UTC and persisted for several hours as the team investigated the root cause.

Official updates show the issue was identified at 11:09 PM UTC and a fix was implemented. By 12:49 AM UTC, the Notifications / Email Notifications and Notifications / In App Notifications components were back to normal.

Smartsheet is experiencing a disruption affecting Brandfolder monthly reports. The outage began at Feb 27, 2026 9:58 PM UTC when the status changed from up to down, with Brandfolder Monthly Reports paused to ensure data accuracy due to a synchronization issue. The team said corrected reports would be available shortly.

A follow-up update at Feb 28, 2026 3:03 AM UTC confirmed the issue persisted and the affected Brandfolder components were moved to degraded states: Digital Asset Management (Brandfolder) / Insights transitioned from up to warn, and Advance Capabilities / Control Center moved from up to maintenance. The overall incident remains marked as down.

Smartsheet experienced a PROD-AU outage that prevented the home page from loading and impacted core applications. The issue began at 12:18 PM UTC in the Australia production environment, with the home page showing an error and multiple components listed as down, including Advance Capabilities / Dynamic View, Core Application / Reports, Core Application / Dashboards, and Core Application / Sheets. The outage lasted approximately 2 hours and 30 minutes, with resolution announced later in the day at Feb 22, 2026 2:48 PM UTC.

During the incident, Smartsheet published three status updates. At 12:43 PM UTC a fix was implemented and monitoring began. All four affected components returned to normal by Feb 22, 2026 2:48 PM UTC. The outage was regional to PROD-AU, affecting the home page and access to core apps in that region.

The Smartsheet Resource Management feature for Advanced Reports experienced an outage, preventing users from creating new advanced reports and refreshing existing ones. The issue began at 4:08 PM UTC and was resolved by 7:33 PM UTC, with a mid-incident transition to a degraded state at 6:58 PM UTC. This disrupted reporting workflows for teams relying on Resource Management, potentially impacting planning and decision‑making until full restoration.

Smartsheet's status page documented the investigation and updates as engineers worked to restore functionality. The Resource Management component moved from down to warn and back to up, with three official status updates issued during the incident.

Smartsheet experienced a brief issue where Proof links loaded with a blank screen, impacting users trying to access proof-related content. The incident began at Feb 10, 2026 7:13 PM UTC and was resolved by Feb 10, 2026 10:18 PM UTC, lasting about 3 hours and 5 minutes. During this period Smartsheet listed a degraded experience for Proof links.

Smartsheet communicated the incident via two status updates. The initial update noted a fix had been implemented and monitoring results were being observed, and the follow-up update confirmed the service had returned to normal after the fix was validated.

Smartsheet experienced a brief incident with errors accessing and loading the Smartsheet application, impacting multiple core components. Users attempting to sign in or load features such as Reports, Dashboards, Sheets, and the Smartsheet Login may have encountered failures or timeouts. The outage began at Jan 18, 2026 5:13 AM UTC and was resolved by Jan 18, 2026 5:29 AM UTC, lasting approximately 16 minutes. The issue affected five core components: Reports, Dashboards, Single Sign On (Company Credentials), Sheets, and Smartsheet Login. During the incident, Smartsheet posted two status updates detailing the investigation and the recovery.

Smartsheet experienced a brief outage in the Documents / Document Builder component, causing delays for document generation requests and impacting both automated workflows and manual document creation. Users attempting to generate documents during the incident likely faced slower responses or failures.

The outage began at 6:58 PM UTC and was resolved by 7:38 PM UTC, lasting roughly 40 minutes. The provider issued 3 official updates during the incident, with the status transitioning from down to degraded (warn) at Dec 4, 2025 7:33 PM UTC as the issue was identified and a fix prepared. The issue affected 1 component: Documents / Document Builder.

During the incident, Smartsheet experienced an outage where emails were not delivered, affecting automated workflows and TOTP login emails. This impacted Core Application / Smartsheet Login and Notifications / Email Notifications. The outage began at Dec 2, 2025 2:38 PM UTC and was resolved by Dec 2, 2025 4:33 PM UTC, lasting about 1 hour and 55 minutes.

Smartsheet posted two official status updates to communicate the investigation and recovery. User reports were limited, with some users noting login-related issues during the incident. All affected components returned to normal operation after the incident was resolved.

A brief outage affected Smartsheet's email notification delivery. The Notifications / Email Notifications component stopped sending emails for a short period, impacting users who rely on email alerts. The incident began at 12:24 AM UTC and was resolved by 12:38 AM UTC, lasting about 14 minutes. The status page recorded two updates during the incident and indicated the issue was resolved quickly. The impact was limited to email notification delivery, with other features remaining available.

Smartsheet experienced an incident affecting Microsoft login authentication and access to the Help Center. The outage began at 4:59 PM UTC when an Azure-related authentication issue was reported, with the Core Application / Single Sign On component entering a degraded state. At 9:18 PM UTC help.smartsheet.com became inaccessible, blocking access to support tickets and self-service help. A fix began around 9:48 PM UTC and was implemented by 9:53 PM UTC, with monitoring continuing as services progressed toward recovery. The Core SSO service returned to normal by 11:33 PM UTC while Help Center access had already recovered earlier in the window.