Smartsheet experienced a minor incident on September 9, 2025 affecting Sheets, lasting 22h 21m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 09, 2025, 03:09 AM UTC
We're currently investigating intermittent reports of occasional issues loading or saving sheets
- investigating Sep 09, 2025, 04:07 AM UTC
We are continuing to investigate this issue.
- investigating Sep 09, 2025, 06:04 AM UTC
We are continuing to investigate with our upstream network providers.
- investigating Sep 09, 2025, 08:08 AM UTC
We are continuing to investigate with our upstream network providers.
- investigating Sep 09, 2025, 10:07 AM UTC
We are continuing to investigate with our upstream network providers.
- investigating Sep 09, 2025, 12:38 PM UTC
We are continuing to investigate with our upstream network providers.
- investigating Sep 09, 2025, 02:40 PM UTC
We are continuing to investigate with our upstream network providers.
- investigating Sep 09, 2025, 04:38 PM UTC
We are continuing to investigate with our upstream network providers.
- monitoring Sep 09, 2025, 05:28 PM UTC
We’re monitoring some customer reports from Australia and New Zealand regions with intermittent networking issues between their ISPs and US-based web applications. If you’re experiencing these issues, please contact your ISP to investigate.
- resolved Sep 10, 2025, 01:30 AM UTC
This incident has been resolved
- postmortem Sep 10, 2025, 03:09 AM UTC
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.