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: Salesforce Connector, Customer Support Portal
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 66 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 “Salesforce connector is experiencing intermittent issues”. 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
Salesforce connector is experiencing intermittent issues
major postmortem · started · resolved
7 updates
- investigating
We are currently investigating this issue. Services related to Support ticket creation may also expericence issues. Our team is actively working on a resolution and will share updates until the issue reaches monitoring status.
- identified
This issue has been identified and a fix is being implemented in coordination with our partners.
- monitoring
A fix rollout is in progress. We will continue to provide updates as we monitor impact.
- monitoring
We are observing stability being restored for the Salesforce Connector and creating Support Cases through the Customer Support Portal. We are continuing to monitor it closely to confirm full service stability. We will provide frequent updates until we reach a resolved status.
- monitoring
We are observing continued stability for the Salesforce Connector and Customer Support Portal. We will continue to monitor it closely to confirm full service stability. We will provide frequent updates until we reach a resolved status.
- resolved
The Salesforce Connector and Customer Support Portal functionality have been fully restored and are operating normally. The incident is now resolved.
- postmortem
On September 16th, 2026, starting at approximately 3:36 AM PDT, customers began experiencing intermittent errors with the Salesforce Connector and with creating cases through the Customer Support Portal. The issue was caused by a widespread outage at our upstream CRM service provider, which affected instance stability and API availability across multiple regions. Our team began monitoring the provider's status closely once impact was confirmed and worked in parallel with them as they rolled out a fix fleetwide. The rollout proceeded in stages and needed to be reapplied to a subset of instances before it fully took hold, which is why customers continued to see intermittent errors throughout the morning even as conditions improved. By 11:51 AM PDT we were observing sustained stability, and our upstream provider confirmed full resolution on their end at approximately 11:59 AM PDT. We confir
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.