CHYP.ai · ORBIT // Cloudy_Day Security Suite

Productivity & files

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 vs. reality: Vendor status and outside signals roughly agree

Regions mentioned: In App Workflows

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started51 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the changenot seenn/a

Evidence

  • Official page: Operational (“All Systems Operational”). evidence confidence: high
  • Vendor stage: postmortem on “Both automated and manual approval workflows are currently failing to execute”. 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

Both automated and manual approval workflows are currently failing to execute

minor postmortem · started · resolved

6 updates

  1. identified

    We have identified issues impacting both automated and manual approval workflows. Our team is fully engaged in addressing the situation. We will provide frequent updates until we reach a monitoring status.

  2. identified

    We are continuing to work on a fix for this issue.

  3. identified

    The initial root cause of the issue has been identified and is now resolved. We are working through a backlog of update and approval workflow creations so there may continue to be a delay in delivery.

  4. monitoring

    The outage is resolved, and new update and approval requests are processing normally. A small delay may persist while backlogged requests from the past two hours finish processing.

  5. resolved

    This incident has been fully resolved, and all backlogged requests have been processed and sent.

  6. postmortem

    On October 1, 2026, a deployment issue caused automated and manual approval workflows to fail across our US, EU, and AU regions for approximately 4.5 hours \(our Government cloud region was unaffected throughout\). Our team restored normal workflow execution within about an hour of the incident being declared. During recovery, the backlog of requests that had built up caused a smaller, secondary issue: some customers experienced delayed approval/update request notifications. We've since recovered the vast majority of affected notifications and are implementing safeguards to prevent a similar deployment issue from recurring, along with improvements to how our systems handle request backlogs so that delayed notifications are retried automatically rather than silently dropped.

Official incident page ↗

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.

Where to next