Is Tableau Down?

No — Tableau is up

Reachable from all 8 checked regions

Average response time: 197ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://trust.salesforce.com

Tableau uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

268ms

Avg response, 30 days

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

30-day history

56-day clean streak

Sep 12 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.

ams

77ms

DNS 30ms TCP 9ms TLS 10ms TTFB 76ms

arn

210ms

DNS 122ms TCP 24ms TLS 24ms TTFB 209ms

cdg

120ms

DNS 78ms TCP 9ms TLS 12ms TTFB 120ms

dfw

245ms

DNS 145ms TCP 26ms TLS 28ms TTFB 245ms

ewr

125ms

DNS 39ms TCP 22ms TLS 25ms TTFB 125ms

fra

94ms

DNS 43ms TCP 1ms TLS 3ms TTFB 94ms

syd

460ms

DNS 265ms TCP 2ms TLS 4ms TTFB 460ms

yyz

247ms

DNS 137ms TCP 15ms TLS 19ms TTFB 247ms

What Tableau does

Tableau is a business intelligence tool for building dashboards on top of warehouses, spreadsheets and databases. Salesforce owns it, and Tableau Cloud is the hosted version that most teams reach at online.tableau.com. Finance and operations reporting tends to sit on it, so an outage stops the dashboards other people plan their day around rather than breaking a customer-facing system.

What an outage looks like

Dashboards fail to render, hang on a spinner, or load the frame with empty visualisations. Extract refreshes queue without completing, leaving views showing yesterday's numbers. Sign-in through your identity provider fails at the redirect back to Tableau. Published workbooks open while live connections to the underlying warehouse time out, which looks like a Tableau fault but is often the data source.

What to do about it

Salesforce publishes Tableau on trust.salesforce.com, where it appears under Analytics alongside the other clouds. Confirm there before restarting anything. If Tableau reports healthy, test the data source directly, since a warehouse or driver problem produces the same blank dashboard. Extract refreshes that failed during an incident normally need re-running by hand once service returns.

Is it down for everyone, or just you?

If this page says Tableau 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

Tableau outage FAQ

Is it Tableau or my data source that is broken?

Test the connection outside Tableau. A dashboard built on a live connection shows empty or erroring visualisations whenever the warehouse behind it is unavailable, and that looks identical to a Tableau fault. If the warehouse answers a query from another client and Salesforce reports Analytics healthy, the problem is more likely the connection credentials or the driver than the platform.

Does a Tableau outage affect Salesforce itself?

Not usually. Tableau runs as its own service under the Salesforce umbrella and appears as a separate product on the trust site, so CRM can be healthy while Tableau is degraded. The shared piece is authentication, and when Salesforce identity has an incident both stop accepting logins at once even though neither application is otherwise broken.

Will scheduled extract refreshes catch up on their own?

Some do and some do not. Schedules that come due after service returns run normally, but refreshes that failed during the incident are not automatically replayed, so a dashboard can sit on stale data until the next scheduled run or a manual refresh. Check the refresh history for failures once the incident closes and re-run the ones that matter.

Can I still use Tableau Desktop when Tableau Cloud is down?

Yes, for local work. Tableau Desktop opens workbooks and extracts stored on your machine without contacting Tableau Cloud, so building and editing continues. What stops is publishing, opening workbooks that live on the site, and anything that needs the site's permissions or shared data sources. Save locally and publish once the site is back.

How we measure this

We request Tableau'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 Tableau 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 Tableau 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