Outages · Productivity & files
Operational Smartsheet outage dossier
smartsheet.com · Official status page (Statuspage-compatible JSON)
Official status now
Operational Operational
checked 0 min ago How we score status
All Systems Operational
Read just now from: Official status page (Statuspage-compatible JSON) · official page ↗
ORBIT score
Clear skies: official status: Operational
At a glance
90-day timeline (1 day tracked)
Each bar is a day. Green: our checks found no official incident. Amber/red: the provider reported one. Grey: before ORBIT started tracking this service. This is "share of our checks with no official incident", not the provider's SLA.
Official incidents per week
Impact mix, 90 d
- 3 minor
- 3 major
- 2 critical
Visitor reports, last 24 h
Unverified reports from ORBIT visitors, in 15-minute buckets. Add yours.
Incident history
- → resolved · lasted 10.8 hOptimizely Security Incidentminor resolved · official notice ↗ · replay & discuss
- → resolved · lasted 5.4 hBoth automated and manual approval workflows are currently failing to executeminor postmortem · In App Workflows · official notice ↗ · replay & discuss
- → resolved · lasted 5.4 hInvestigating blank page or error on Smartsheet Loginmajor postmortem · Smartsheet Login · official notice ↗ · replay & discuss
- → resolved · lasted 10.4 hSalesforce connector is experiencing intermittent issuesmajor postmortem · Salesforce Connector, Customer Support Portal · official notice ↗ · replay & discuss
- → resolved · lasted 3.2 hSmartsheet and Smartsheet Login Unavailable for Smartsheet USmajor postmortem · Smartsheet Login, Single Sign On ( Company Credentials ), Sheets, Forms · official notice ↗ · replay & discuss
- → resolved · lasted 2.3 hUnexpected HTTP response code affecting login, sheet access, Control Center, Dynamic View and other premium appscritical postmortem · Calendar, Smartsheet Login, Control Center, Sheets · official notice ↗ · replay & discuss
- → resolved · lasted 4.9 hSheets in Smartsheet US are failing to loadcritical postmortem · Resource Management, Control Center, AI Tools, Sheets · official notice ↗ · replay & discuss
- → resolved · lasted 3.6 hIntermittent Cell Link and Cross Sheet Reference delays/failuresminor postmortem · Sheets · official notice ↗ · replay & discuss
Related services
- no official feedMicrosoft 365no official feed→
- OperationalGoogle WorkspaceOperational→
- OperationalGoogle DriveOperational→
- OperationalNotionOperational→
- OperationalAirtableOperational→
- OperationalFigmaOperational→
- OperationalCanvaOperational→
- OperationalDropboxOperational→
"Runs on" links are inferred from public information and may be outdated.
How we score status
- Source. Every reading comes from the provider's own public status page or status API (Statuspage, Instatus, incident.io-style JSON, or the provider's RSS/JSON). ORBIT never pings or scans the service.
- Scope. For each open incident we count the regions or components it names against the total the provider publishes, and label it global, multi-region, 1 region or n of N components.
- Age. Incidents are new (under 1 hour), active, long-running (open more than 48 hours) or stale (no provider update for 24 hours or more).
- Headline. The headline colour comes from current incidents only. A single-region or small-scope incident caps the headline at "Degraded"; a global or widespread one keeps the provider's impact. Long-running or stale issues limited to one region or a few components get a known long-running issue badge and don't set the headline colour.
- Transparency. The provider's own page-level status is always shown next to ORBIT's headline, with a link to the official page. When they differ, the provider's page is the authority on what it says.
Where this data comes from. "Official status" is read from each provider's own public status page or status API (the same JSON or RSS their status page publishes), cached for a minute or more. ORBIT never pings, scans or probes the provider's systems. "Our checks" and history are ORBIT's own record of those readings, kept in our database. Visitor reports are unverified. Headlines are matched by name and shown for context: coincidence, not causation. Cloudy_Day is independent and not an official source for any company listed.
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.