Smartsheet Outage History

Smartsheet is up right now

Pingoru has recorded 60 incidents for Smartsheet: 33 in the last 12 months and 10 in the last 90 days.

Source: status.smartsheet.com

60incidents recorded
33last 12 months
10last 90 days
39 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking Smartsheet in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026312 of 720 (2%)
May 202617 of 744 (1%)
June 20264354 of 720 (49%)
July 2026249 of 744 (7%)
August 2026414 of 744 (2%)
September 2026419 of 720 (3%)
October 202615 of 593 (1%)

Incidents, newest first

Major April 30, 2025 Smartsheet access issues and unexpected errors 2h 56m Email Notifications, REST API, Calendar, Smartsheet Login and 31 more

Started Apr 30, 2025, 05:37 AM UTC· resolved Apr 30, 2025, 08:34 AM UTC

  1. investigating Apr 30, 2025, 05:37 AM UTC

    We are currently investigating some customer reports of issues and unexpected errors while logging in to the app, accessing assets, and navigating the site. We will continue to provide frequent updates as we work towards resolution.

  2. identified Apr 30, 2025, 05:57 AM UTC

    We have identified mitigations for the issue and are taking action to resolve. The service is beginning to recover and we will continue to monitor. We will continue to provide frequent updates as we work towards resolution.

  3. monitoring Apr 30, 2025, 06:24 AM UTC

    A fix has been implemented and we are monitoring to ensure continued stability of this feature.

  4. resolved Apr 30, 2025, 08:34 AM UTC

    This incident has been resolved

  5. postmortem Apr 30, 2025, 08:58 AM UTC

    Starting at 10:15 PM Pacific Time on April 29th, 2025, some users experienced unexpected errors when logging in, navigating the application, or using the premium apps and API. Our engineering teams identified an issue with our load balancers and took mitigative action. The service fully recovered at 11:20 PM.

Read the full incident report →