Smartsheet: Smartsheet Application & API
Timeline of updates
- resolved
Our caching system was halted due to system memory pressure caused by an unrelated OS component. The cache was automatically restarted, but there is no mechanism in place to automatically attempt to reload the caches after a restart. The cache load began at 0620 PST and continued until 0850 when we reached our minimum safe levels. In the interim our application operated in a degraded state. Recent infrastructure improvements delivered with the data center flip allowed the continued use and operation of the platform. Once we had achieved an expected minimum safe level of cache readiness we recovered the application servers from their degraded "failsafe" state, and the application recovered within seconds.
From Smartsheet’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.smartsheet.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Smartsheet, started 2016-02-22 15:27 UTC, resolved after 11 h, 1 update(s).
- Title
- Smartsheet Application & API
- Vendor
- Smartsheet
- Date
- URL
- https://rewindex.com/company/smartsheet/incidents/bnllpggcbblp
Smartsheet profileRecent Smartsheet incidentsAll outages on February 22, 2016Smartsheet in February 2016MarkdownJSON