Tableau Cloud incident
We've confirmed a remediation path, and are applying the fix to the small subset of customers still experiencing a read-only state. We'll provide an update in 60 minutes or sooner if additional inform
Tableau Cloud experienced a major incident on May 8, 2026 affecting HEROKUVIRGINIA, lasting 15h 3m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 08, 2026, 03:54 AM UTC
Degradation Started: herokuServiceDegradation
- monitoring May 08, 2026, 04:14 AM UTC
Beginning at 12:25 UTC on May 08, 2026, a partial outage in an upstream service provider began impacting a subset of customers in the US region. Affected customers may be experiencing intermittent connectivity, elevated DB latency, or degraded performance with third-party add-on providers. Affected customers may wish to trigger database failovers as a mitigation.
- monitoring May 08, 2026, 04:33 AM UTC
e
- monitoring May 08, 2026, 05:18 AM UTC
Engineers are working to restore impacted resources. While the partial outage from the upstream service provider is ongoing, some customers are observing signs of recovery. Upstream resources remain impacted, and our team continues to work toward full resolution.
- monitoring May 08, 2026, 05:56 AM UTC
Engineers are working to restore impacted resources. While the partial outage from the upstream service provider is ongoing, the majority of customers are observing recovery. Upstream resources remain impacted, and our team continues to work toward full resolution. We will post another update in approximately 2 hours.
- monitoring May 08, 2026, 08:18 AM UTC
Engineers continue working on restoring impacted resources. While the partial outage from the upstream service provider is ongoing, we are seeing little customer impact. Upstream resources remain impacted, and our team continues to work toward full resolution.
- monitoring May 08, 2026, 10:22 AM UTC
Engineers continue working on restoring impacted resources. While the partial outage from the upstream service provider is ongoing, we are seeing little customer impact. Upstream resources remain impacted, and our team continues to work toward full resolution. We will post an update in approximately 2 hours, or if anything changes sooner.
- monitoring May 08, 2026, 12:15 PM UTC
The issue is now resolved.
- monitoring May 08, 2026, 03:44 PM UTC
We’ve completed the migration to a new availability zone, and the Heroku-hosted web applications and customer databases are now fully operational. We apologize for how this incident affected you and your business. We'll undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
- monitoring May 08, 2026, 03:59 PM UTC
Engineers continue working on restoring impacted resources. While the partial outage from the upstream service provider is ongoing, we are seeing little customer impact. Upstream resources remain impacted, and our team continues to work toward full resolution. We will post an update in approximately 2 hours, or if anything changes sooner.
- monitoring May 08, 2026, 05:24 PM UTC
We've confirmed a remediation path, and are applying the fix to the small subset of customers still experiencing a read-only state. We'll provide an update in 60 minutes or sooner if additional information becomes available.