Brandfolder incident

Sheets in Smartsheet US are failing to load

Critical Resolved View vendor source →

Brandfolder experienced a critical incident on August 26, 2026 affecting AI Tools, lasting 4h 55m. The incident has been resolved; the full update timeline is below.

Started
Aug 26, 2026, 01:28 PM UTC
Resolved
Aug 26, 2026, 06:23 PM UTC
Duration
4h 55m
Detected by Pingoru
Aug 26, 2026, 01:28 PM UTC

Affected components

AI Tools

Update timeline

  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.