Skip to main content
Smartsheet logo

Is Smartsheet Down?

No — Smartsheet is up

Reachable from all 8 checked regions

Average response time: 1652ms

Last checked · checks run every 6 hours

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

Smartsheet uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
1839ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 33 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

33-day clean streak
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 31 checks
Sep 16: 100.00% uptime, 30 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 31 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 30 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 31 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: no data
Sep 13 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.

arn
1902ms
DNS 0ms TCP 109ms TLS 219ms TTFB 1902ms
cdg
1933ms
DNS 0ms TCP 109ms TLS 219ms TTFB 1933ms
dfw
724ms
DNS 0ms TCP 31ms TLS 64ms TTFB 724ms
ewr
326ms
DNS 0ms TCP 7ms TLS 15ms TTFB 326ms
fra
1675ms
DNS 0ms TCP 92ms TLS 186ms TTFB 1675ms
gru
2361ms
DNS 0ms TCP 124ms TLS 250ms TTFB 2361ms
iad
143ms
DNS 1ms TCP 4ms TLS 6ms TTFB 142ms
jnb
4155ms
DNS 0ms TCP 235ms TLS 472ms TTFB 4155ms

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 up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Monday.com
Monday.com
Asana
Asana
Airtable
Airtable
Miro
Miro

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 — the most recent check ran from 8 of them.
  • 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.

Get alerted when Smartsheet goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required