1. Home
  2. Services
  3. Email, files & productivity
  4. Tableau
Tableau tableau.com Live · Operational

Is Tableau down right now? Live status and outage tracker

No, Tableau is up.

No outage detected, and no user reports in the last hour.

Reports, last hour
0
Usual at this hour
Almost none
Vs the hour before
–

User reports, last 24 hours, one bar per 15 minutes. Dashed line: the usual level. 96 normal · 0 elevated · 0 outage

Last spike · · Data refreshes every 5 minutes

01 · User reports
0 reports in the last hour

From a public outage-reporting feed, counted in 15-minute windows. The verdict above is based on these.

02 · Our check, Frankfurt
Answered in 84 ms

Our server loaded www.tableau.com 7 h ago. Behind Akamai.

03 · 12 cities, check-host.net
12 of 12 got an answer

Fastest from Frankfurt (53 ms), slowest from Paris (800 ms). 7 h ago.

04 · Tableau's own status page

Not read by this site. The quickest way to confirm a cause and see when a fix is expected.

Last 24 hours

Tableau outages and problems

User reports, last 24 hours

4 reports in total, counted in 15-minute windows

No problem reports came in for Tableau in the last hour, and at this time of day there are usually almost none. Over the last 24 hours there were 4 reports. Worldwide, most recent reports were about automation & workflows (50%) and website (25%). The last spike in reports was 77 h ago and lasted 15 min. These are user reports from the US, where most people report Tableau problems.

Around the world right now: normal in 71 other countries. By country

In the past 24 hours, 4 user reports came in for Tableau. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day. The busiest 15-minute window had 1 report, about 24 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
  • NormalClose to the usual level24 h · 4 reports
  • ElevatedMore than 1.5 times the usual levelNone in this chart
  • OutageMore than twice the usual level and far above the day's averageNone in this chart
  • Usual levelWhat a usual day sees at that timeAlmost none at this time of day
Reports, last hour
0
Quiet
Uptime, 24 h
100.00%
No outage windows
Last outage
None
In the last 24 hours
Busiest 15 minutes
1
1 report, 24 h ago
Tableau status card: No, Tableau is up. User reports over the last 24 hours.
Share this statusThe picture people see when this page is shared: the answer and the last 24 hours of reports.

In the past 24 hours, 4 user reports came in for Tableau. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.

The busiest 15-minute window had 1 report, about 24 hours ago. That stays below our outage threshold, so it doesn't count as downtime.

No problems detected in the last 24 hoursReports for Tableau stayed at their usual level the whole time.
This month

Tableau in November 2026

Problem reports in November
185

Monthly report for November 2026

What went wrong

What people said was wrong in recent problem reports for Tableau worldwide.

  1. Automation & Workflows50%
  2. Website25%
  3. App25%

Share of 4 recent reports that said what was wrong, from every country listed below.

World map

Tableau reports around the world

In the last 24 hours, 7 problem reports about Tableau came in from 3 countries. Right now reports are at the usual level in every country.

  • Outage now
  • Problems now
  • Normal
Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.
CountryNowLast hour24 hours
The US numbers above Normal 04
The UK Normal 02
India Normal 01
Mexico Normal 00
The Netherlands Normal 00
Germany Normal 00
Belgium Normal 00
France Normal 00
Russia Normal 00
Italy Normal 00
Spain Normal 00
Canada Normal 00

Each country's status compares its reports with the usual level there. 60 more countries had 0 reports in the last 24 hours. Map outlines: Natural Earth.

Last 30 days

Tableau problem spikes, last 30 days

Since 28 October, Tableau had 1 outage spike and 1 period of elevated reports. The longest lasted 26 min, on 2 November.

  • Sun 18 Oct: no data
  • Mon 19 Oct: no data
  • Tue 20 Oct: no data
  • Wed 21 Oct: no data
  • Thu 22 Oct: no data
  • Fri 23 Oct: no data
  • Sat 24 Oct: no data
  • Sun 25 Oct: no data
  • Mon 26 Oct: no data
  • Tue 27 Oct: no data
  • Wed 28 Oct: 11 reports
  • Thu 29 Oct: 9 reports
  • Fri 30 Oct: 8 reports
  • Sat 31 Oct: 2 reports
  • Sun 1 Nov: 0 reports
  • Mon 2 Nov: 40 reports (outage spike that day)
  • Tue 3 Nov: 2 reports
  • Wed 4 Nov: 10 reports
  • Thu 5 Nov: 3 reports
  • Fri 6 Nov: 3 reports
  • Sat 7 Nov: 0 reports
  • Sun 8 Nov: 1 report
  • Mon 9 Nov: 11 reports
  • Tue 10 Nov: 2 reports
  • Wed 11 Nov: 9 reports
  • Thu 12 Nov: 52 reports (elevated reports that day)
  • Fri 13 Nov: 43 reports
  • Sat 14 Nov: 5 reports
  • Sun 15 Nov: 4 reports
  • Mon 16 Nov: 0 reports
  • Elevated reports
    Thu 12 Nov, 20:49–21:04
    Lasted 15 min
    10peak reports
  • Outage
    Mon 2 Nov, 14:29–14:55
    Lasted 26 min
    22peak reports

By country

In the last 19 days, most Tableau problem reports came from the US (205), the UK (12) and Japan (11). None of these countries had a day at outage level.

  • The US205
  • The UK12
  • Japan11
  • Canada8
  • India8
  • Germany5
  • Tunisia5
  • Brazil4
  • Outage spike
  • Elevated reports
  • Normal
  • No data yet

Each square is one day. It turns red when reports stayed at outage level for half an hour or more, and amber when they stayed above the usual level for an hour or more. The number on the right is the country's total since 29 October 2026, when country history starts. A wider gap marks a Monday. Point at a square, or tap it, for that day's numbers. Days run from midnight to midnight, Central European time.

A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 28 October 2026. Monthly reports for all services

Troubleshooting

How to fix Tableau not working

Tableau is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:

Your browser tries to reach tableau.com over your own connection, right now. Nothing is sent to us or stored.

  1. Reload the view and sign in again

    Click reload in your browser when a Cloud view sticks on Loading, then use Server > Sign In in Desktop if your session expired again. So you clear auth.

  2. Clear the Desktop cache

    Open Desktop and go to Help > Settings and Performance > Clear Cache when maps tile slow or old marks persist after a refresh. So you drop bad tiles and force fresh queries.

  3. Refresh the extract and fix credentials

    Select Data > Refresh All Extracts in Desktop after you republish or when filters show stale rows because the extract missed its update. Retype your password if it prompts you.

  4. Update drivers and repair the install

    Go to Settings > Apps in Windows to remove Desktop, then install a fresh copy with the database driver for your source. So you clear version skew and bad installs.

While it is down

While Tableau is down: what to use instead

  • Tableau Desktop with local files If your Cloud or Server site won't load, you can still open packaged workbooks and extracts saved on your machine and keep building until publishing works again.
  • Exported PDFs and subscription emails Check your inbox for the last scheduled subscription or any PDF you exported earlier, because those snapshots often cover a morning meeting.
  • Microsoft Power BI Teams that already pay for it can point it at the same database for a quick chart.
  • Excel or a SQL client When you need one specific number, query the source data directly; it takes longer to format, but the figures match what the dashboard would show once it is back.
Your device

Fix Tableau on Windows, Mac, Android and iPhone

Tableau on Windows

Fix
Clear your browser cache if Tableau Cloud is failing, or disable hardware acceleration in Tableau Desktop if it crashes. Ensure your firewall isn't blocking Tableau's outbound ports.
Check
Check the Tableau Trust status page to see if Tableau Cloud is down. You can also check your Windows Event Viewer for application errors related to Tableau Desktop.
Command Prompt
ping tableau.comTest whether Tableau's servers reply
nslookup tableau.comCheck that Tableau's DNS resolves
tracert tableau.comTrace where the connection drops
ipconfig /flushdnsClear the DNS cache, then reload

Tableau on Mac

Fix
Force quit Tableau Desktop and clear your browser cache if accessing Tableau Cloud. Ensure the app has necessary disk access permissions in your macOS System Settings.
Check
Visit the Tableau Trust status page to check for active outages affecting Tableau Cloud. You can also test your internet connection or try loading Tableau in an Incognito window.
Terminal
ping -c 4 tableau.comTest whether Tableau's servers reply
nslookup tableau.comCheck that Tableau's DNS resolves
traceroute tableau.comTrace where the connection drops
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reload

Tableau on Android

Fix
Clear the Tableau Mobile app cache in your Android settings, or reinstall the app from the Google Play Store. Verify that your VPN is active if your organization requires it to access Tableau Server.
Check
Open the Tableau Mobile app to see if it displays connection timeout errors or fails to load your dashboards. You can also check the Google Play Store to see if an update is available.

Tableau on iPhone and iPad

Fix
Restart the Tableau Mobile app or reinstall it from the App Store. Ensure your iOS device is connected to your corporate VPN if accessing a private Tableau Server.
Check
Check if the Tableau Mobile app fails to authenticate or displays server connection errors on your iPhone or iPad. You can also check the Tableau Trust page using Safari.
Same time

Problems at the same time as Tableau

Since 28 October, all 2 of Tableau's spikes in problem reports overlapped a spike at another service.

When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.

A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.

Busiest times

When people report Tableau problems

The busiest hour for reports about Tableau is 20:00 to 21:00 Central European time, and the busiest day is Thursday.

By hour of the day

  • 00:00 to 01:00: 0.23 reports on an average day
  • 01:00 to 02:00: 0.12 reports on an average day
  • 02:00 to 03:00: 0.19 reports on an average day
  • 03:00 to 04:00: 0.15 reports on an average day
  • 04:00 to 05:00: 0.01 reports on an average day
  • 05:00 to 06:00: 0 reports on an average day
  • 06:00 to 07:00: 0.03 reports on an average day
  • 07:00 to 08:00: 0.03 reports on an average day
  • 08:00 to 09:00: 0 reports on an average day
  • 09:00 to 10:00: 0 reports on an average day
  • 10:00 to 11:00: 0.02 reports on an average day
  • 11:00 to 12:00: 0.05 reports on an average day
  • 12:00 to 13:00: 0 reports on an average day
  • 13:00 to 14:00: 0.08 reports on an average day
  • 14:00 to 15:00: 0.13 reports on an average day
  • 15:00 to 16:00: 0.64 reports on an average day
  • 16:00 to 17:00: 0.28 reports on an average day
  • 17:00 to 18:00: 0.15 reports on an average day
  • 18:00 to 19:00: 0.37 reports on an average day
  • 19:00 to 20:00: 0.37 reports on an average day
  • 20:00 to 21:00: 0.78 reports on an average day
  • 21:00 to 22:00: 0.45 reports on an average day
  • 22:00 to 23:00: 0.42 reports on an average day
  • 23:00 to 00:00: 0.24 reports on an average day

By day of the week

  • Monday: 5.3 reports on an average Monday
  • Tuesday: 0.67 reports on an average Tuesday
  • Wednesday: 6 reports on an average Wednesday
  • Thursday: 12 reports on an average Thursday
  • Friday: 9.1 reports on an average Friday
  • Saturday: 1.1 reports on an average Saturday
  • Sunday: 0.83 reports on an average Sunday

Each bar is the average number of user reports in that hour, or on that day of the week, from 40 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.

About

What happens when Tableau goes down

Tableau is analytics software. Teams in finance and sales rely on it to share live dashboards on Cloud and Server, so when it fails you lose refreshes and views.

You hit refresh and your workbook spins without loading because extracts on Cloud or Server cannot finish. Filters and subscriptions stall next, while Desktop can still open saved shared workbooks even though new publishing and your sign in through Tableau login fail. Outages hit Cloud hardest. When one region has trouble, you see errors on Cloud while Server on your own network keeps running.

Servers and network

Tableau IP address, servers and network

IPv4 addresses
95.100.110.22
Show all 2
  • 95.100.110.7
IPv6
Not offered
Network
AS20940 · Akamai International B.V., registered in the Netherlands
Served through
Akamai
DNS hosted by
NS1
HTTPS certificate
Issued by Let's Encrypt, valid until 6 Feb 2027 (82 days)
HTTP/3
Not advertised
Our check
Answered in 84 ms (it turned away our automated check, which is common)

Checked from our server in Frankfurt, Germany, 7 h ago, for www.tableau.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.

Checked from 12 places around the world

All 12 locations got an answer from www.tableau.com. Fastest from Frankfurt (53 ms), slowest from Paris (800 ms). Every location connected through Akamai International B.V. (AS20940), using 12 different addresses.

LocationResultTimeAddress reached
FrankfurtGermanyUp53 ms184.86.103.220
ViennaAustriaUp323 ms104.83.4.17
MilanItalyUp350 ms2.19.124.148
ParisFranceUp800 ms23.204.132.194
AmsterdamNetherlandsUp513 ms2.21.23.218
MadridSpainUp330 ms23.211.15.150
WarsawPolandUp281 ms23.47.124.151
DallasUSAUp415 ms23.221.22.210
Los AngelesUSAUp182 ms23.210.216.139
São PauloBrazilUp59 ms2.16.169.19
SingaporeSingaporeUp756 ms23.32.39.132
TokyoJapanUp199 ms23.53.3.135

Checked with check-host.net from its servers in these cities 7 h ago, for www.tableau.com. Time is how long each server took to load the page.

Questions

Tableau FAQ

Is Tableau down right now?

The status at the top of this page shows whether problem reports for the service are above their usual level, counted in 15-minute windows over the last 24 hours. This site does not monitor anything itself, so that reading comes from other people's reports alone. For a second opinion, Tableau's official status page at https://trust.tableau.com/ is where the company posts incidents and maintenance. If the page loads on cellular data but not on your office network, or a colleague on a different connection opens the same workbook without trouble, the fault sits on your side.

Why can't I sign in to Tableau Cloud even with the right password?

Sign-in trouble usually starts on the identity side. If your company uses single sign-on, your identity provider has to be reachable before the app will let you in, and an expired session or a stale saved password gives you the same dead end. Try a private window with extensions off, then have a colleague on a different network try to sign in. When several people fail at once from unrelated connections, the service is the likely culprit.

Tableau Desktop can't connect to the server. Is that an outage?

Not always. The desktop app talks to your site over your network, so a VPN drop or a proxy block that swallows the connection stops it before anything reaches the server. Compare with a browser on the same machine: if the site loads there, your network is fine and the app's saved connection details are the likely cause. If the browser fails too, and other people report the same thing, the service becomes a fair suspect.

Why won't a published workbook load on Tableau Public?

Public runs on its own infrastructure, so it can fail while the rest of the platform works normally. A workbook that hangs on a blank frame or throws an error often has a broken data source behind it, or it was published from a desktop copy that leans on a local file nobody else can reach. Open another author's workbook first; if that one loads, the problem sits with your content rather than the site.

My extract refresh failed. Does that mean Tableau is down?

One dead extract usually means little. Saved credentials expire and source databases go unreachable from the machine that runs the refresh, all without the service noticing. If your other published views still open for you and for a colleague, the platform is probably fine. When every refresh across a site stops at the same minute, that pattern deserves a look at the reports coming in from other people.
Official channels

Contact Tableau support

Tip: when Tableau is down, its official status page is the quickest way to confirm the cause and see when a fix is expected.

About Tableau

Category
Online Service
For your site

Put the Tableau status on your site

Paste one of these into a web page, a blog post or a README: a small badge, or a card with the chart. Both show the same status as this page, based on user problem reports, and link back here.

Tableau status badge, as it looks now

HTML
<a href="https://isitdownrightnow.app/services/tableau/"><img src="https://isitdownrightnow.app/badge/tableau.svg" alt="Tableau status" height="20"></a>
Markdown, for README files
[![Tableau status](https://isitdownrightnow.app/badge/tableau.svg)](https://isitdownrightnow.app/services/tableau/)

A live card with the chart

The status, reports in the last hour and the last 24 hours, updated every 5 minutes. Use the frame, or the image where frames are not allowed, such as newsletters.

Frame
<iframe src="https://isitdownrightnow.app/embed/tableau/" title="Tableau status" width="100%" height="230" style="border:0;max-width:560px" loading="lazy"></iframe> <p><a href="https://isitdownrightnow.app/services/tableau/">Tableau status</a> from IsItDownRightNow.app</p>
Image, updated about every 10 minutes
<a href="https://isitdownrightnow.app/services/tableau/"><img src="https://isitdownrightnow.app/share/tableau.png" alt="Tableau status: problem reports over the last 24 hours" width="600" height="315" loading="lazy"></a>
Markdown image, for README files
[![Tableau status](https://isitdownrightnow.app/share/tableau.png)](https://isitdownrightnow.app/services/tableau/)

Badge, frame and image load no scripts from other sites and set no cookies; people who see them on your page load them from our server. More for journalists.

How we track Tableau

The status on this page comes from user-submitted problem reports for Tableau, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Tableau, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.

When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from Tableau's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.

Elsewhere

Check other services