Skip to main content

Is Smartsheet Down?

No — Smartsheet is up

We cannot measure Smartsheet directly — it blocks automated checks — but Smartsheet's own status page currently reports no issues.

Last checked · checks run every 6 hours

Official status page: https://status.smartsheet.com

Why there is no uptime figure on this page

The last time we fetched Smartsheet's page directly, our checks failed from every region we tried. On that evidence alone we cannot tell an origin refusing our automation from a service that is genuinely down — the two look identical to us — and we are not willing to call it an outage on a guess.

So we publish no uptime percentage for Smartsheet. What this page does show is each region's most recent result and Smartsheet's own status feed, which you can weigh yourself.

30-day history

Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: blocked from automated checks
Aug 7: blocked from automated checks
Aug 8: blocked from automated checks
Aug 9: blocked from automated checks
Aug 10: blocked from automated checks
Aug 11: blocked from automated checks
Aug 12: blocked from automated checks
Aug 13: blocked from automated checks
Aug 14: blocked from automated checks
Aug 15: blocked from automated checks
Aug 16: blocked from automated checks
Aug 17: blocked from automated checks
Aug 18: blocked from automated checks
Aug 19: blocked from automated checks
Aug 20: blocked from automated checks
Aug 21: blocked from automated checks
Aug 22: blocked from automated checks
Aug 23: blocked from automated checks
Aug 24: blocked from automated checks
Aug 25: blocked from automated checks
Aug 26: blocked from automated checks
Jul 28 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

dfw
edge reachable

A static asset loaded in 173ms. That proves the edge is up, but not that the site works.

ewr
edge reachable

A static asset loaded in 48ms. That proves the edge is up, but not that the site works.

fra
edge reachable

A static asset loaded in 441ms. That proves the edge is up, but not that the site works.

gru
edge reachable

A static asset loaded in 624ms. That proves the edge is up, but not that the site works.

iad
edge reachable

A static asset loaded in 23ms. That proves the edge is up, but not that the site works.

jnb
edge reachable

A static asset loaded in 1212ms. That proves the edge is up, but not that the site works.

lax
edge reachable

A static asset loaded in 308ms. That proves the edge is up, but not that the site works.

lhr
edge reachable

A static asset loaded in 422ms. That proves the edge is up, but not that the site works.

nrt
edge reachable

A static asset loaded in 814ms. That proves the edge is up, but not that the site works.

What Smartsheet does

Smartsheet is a work management platform built on a spreadsheet-style grid that also renders as Gantt charts, calendars, card boards and dashboards. Teams run project plans, intake forms, approvals and resource schedules on it, and it is often the system of record that PMO, finance and operations groups report from, with connectors pushing data to and from Jira, Salesforce and Tableau.

What an outage looks like

Sheets load blank or hang on a spinner, and saves return timeout errors while the row you edited stays unsaved. Forms submitted by people outside your organisation fail rather than writing a row. Dashboards render empty widgets, workflow emails and approval reminders stop arriving, and the mobile app shows cached data without flagging that the sync failed. API calls and webhooks can fail while the web app still loads.

What to do about it

Check status.smartsheet.com, which lists Core Application, Login, Sheets, Forms, Reports, Dashboards, Workflows, the REST API, webhooks and the mobile and desktop apps as separate components, so a partial incident is visible rather than guessed at. The Jira, Salesforce, ServiceNow, Tableau and Dynamics connectors are reported on their own. Avoid re-submitting a form repeatedly during an incident, because duplicate rows are harder to clean up than a missing one.

Is it down for everyone, or just you?

If this page says Smartsheet is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Smartsheet outage FAQ

Is Smartsheet down for everyone or just my account?
Smartsheet publishes one status page for the platform, but incidents are often scoped narrowly: an incident on 15 July 2026 was titled 'Smartsheet US is not loading', so a regional problem can leave other users working normally. If the page is green, open a different sheet to test whether one sheet is the problem, and ask a colleague on the same plan whether they see the same failure.
Will I lose the row I was editing when Smartsheet times out?
Usually not, but confirm rather than assume. Changes are written to the server as you make them, so an edit that returned a success indicator is stored. An edit that returned a timeout may never have committed. When the service recovers, reload the sheet and compare it against what you expected before retyping anything, because re-entering rows that did save leaves you with duplicates to unpick.
Do form submissions still arrive during an outage?
No. Forms is a separate component on the status page, and while it is degraded a submission errors instead of writing a row. External respondents see that failure themselves and usually retry or email instead. Treat anything sent during the incident window as missing rather than delayed, and confirm with the sender once the component is operational again.
Does a Smartsheet outage affect our Jira or Salesforce data?
Only the sync between them. The Jira, Salesforce, ServiceNow, Tableau and Dynamics connectors are separate components, so records already written into those systems are untouched while updates stop flowing in both directions. Expect a lag before the two sides agree again after the connector recovers, and check any automation that assumed a field would have been updated in the meantime.
Why does the mobile app show old data?
Because it keeps a local cache. During an incident the app renders the last data it downloaded without making it obvious that the sync failed, which makes the platform look healthy from a phone while the web app is timing out. Pull to refresh and watch for an error rather than trusting what is on screen. The mobile and desktop apps are reported as separate components.

How we measure this

  • We request Smartsheet's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Smartsheet publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it — and when Smartsheet blocks our checks entirely, we report the vendor's own status directly.

Get alerted when Smartsheet goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required