Live  /  Tableau  /  Incident

Tableau: Degradation: LoadaView (21 instances)

Tableau · tableau.comMinor incidentResolved2026-10-17 04:29 UTC
Public — what happened

Summary

Tableau said a subset of its Tableau Cloud customers were affected by a problem that began after a recent release, first noted on 2026-10-16 around 20:47 UTC. The company reported that people using extract-based data sources might find calculated fields renamed, which could cause workbooks and dashboards relying on them to display incorrectly. Tableau suggested switching to a live connection as a workaround and pointed to a Known Issue article. By 04:29 UTC on 2026-10-17 it said a fix had passed testing in a lower environment with positive early results and was being rolled out to remaining production instances, and the incident was still listed as under investigation.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Tableau against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Tableau: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Tableau report →

More from Tableau

Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.

The full archive is on the Tableau status & history page.

Related: Tableau status & history. SquidGrid is not affiliated with Tableau.