Operational Smartsheet status
smartsheet.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
No sign of a widespread Smartsheet problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Sheets
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 87 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: postmortem on “Intermittent Cell Link and Cross Sheet Reference delays/failures”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside Smartsheet's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “postmortem”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
We don't map other services that depend on Smartsheet. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Smartsheet, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers Smartsheet may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Smartsheet. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Intermittent Cell Link and Cross Sheet Reference delays/failures
minor postmortem · started · resolved
6 updates
- investigating
We are investigating delays or failures impacting Cell Links and Cross Sheet References. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.
- investigating
We are still investigating this issue. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.
- identified
This issue has been identified and a fix is being implemented.
- monitoring
A fix has been implemented and we are monitoring the service for ensured stability.
- resolved
This incident has been resolved.
- postmortem
Between August 24 and August 28, 2026, a performance optimization caused certain formulas and cross-sheet references to evaluate incorrectly or produce errors following row insertions or deletions. The root cause was an asynchronous calculation change that performed partial data loads, omitting dependent cells and silently persisting inaccurate formula values. The issue was mitigated on August 27 at 11:25 AM PDT by disabling the optimization flags, with full data restoration completed on August 28 after recalculating approximately all affected known sheets. Preventive measures include enforcing dependency coverage safeguards and adding automated test suites for structural sheet edits. Another event also caused the same issues. On August 25, 2026 \(starting at ~19:43 UTC\), an unprecedented update fanout from a single high-connectivity source sheet overwhelmed the backend Grid Service wit
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.