Tableau Cloud Outage History
Tableau Cloud is up right nowPingoru has recorded 268 incidents for Tableau Cloud: 268 in the last 12 months and 105 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 10 | 96 of 720 (13%) |
| May 2026 | 47 | 178 of 744 (24%) |
| June 2026 | 59 | 412 of 720 (57%) |
| July 2026 | 54 | 287 of 744 (39%) |
| August 2026 | 37 | 410 of 744 (55%) |
| September 2026 | 35 | 496 of 720 (69%) |
| October 2026 | 26 | 155 of 589 (26%) |
Incidents, newest first
Major May 8, 2026 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 15h 3m HEROKUVIRGINIA
Started May 08, 2026, 03:54 AM UTC· resolved May 08, 2026, 06:58 PM UTC
- 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.
Minor May 8, 2026 We're aware of an issue impacting agent metadata services resulting in a subset of customers experiencing issues retrieving or deploying agent metadata. 1h 43m BRA2S, BRA4S, BRA54S, BRA6S and 377 more
Started May 08, 2026, 01:50 AM UTC· resolved May 08, 2026, 03:33 AM UTC
- identified May 08, 2026, 01:50 AM UTC
Degradation Started: agentforcePerformanceDegradation
- monitoring May 08, 2026, 01:50 AM UTC
We're aware of an issue impacting agent metadata services resulting in a subset of customers experiencing issues retrieving or deploying agent metadata. The team has identified and validated a fix, and are preparing for deployment to the impacted instances. We'll provide an update in 30 minutes or sooner if additional information becomes available.
Minor May 6, 2026 We’ve successfully validated the fix and are preparing to deploy it to all impacted environments. 7h 45m USA1036S, USA1062, USA1068S, USA1070S and 387 more
Started May 06, 2026, 04:40 PM UTC· resolved May 07, 2026, 12:26 AM UTC
- identified May 06, 2026, 04:40 PM UTC
Degradation Started: featureServiceDisruption
- monitoring May 06, 2026, 04:40 PM UTC
We are aware of an issue affecting Einstein Voice for Agentforce (AFV). As a result, customers are unable to create new voice sessions. We've identified a configuration issue and are working to deploy a fix on an expedited basis. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring May 06, 2026, 05:30 PM UTC
We continue to investigate an issue affecting Agentforce Voice where a subset of customers may be unable to initiate new voice sessions. We've identified an issue with metadata configuration and are working to deploy a fix which is expected to take several hours. We'll provide an update in 120 minutes or sooner if additional information becomes available.
- monitoring May 06, 2026, 06:04 PM UTC
Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove any instances that have not experienced an impact, and these will no longer receive communications about this incident going forward. Impacted instances will continue to be updated. We apologize for any inconvenience caused.
- monitoring May 06, 2026, 06:10 PM UTC
As we have confirmed this issue to only be impacting sandbox environments, all production instances have been removed from this post. We are continuing to work on the fix for this issue and will provide an update when additional information becomes available.
- monitoring May 06, 2026, 09:20 PM UTC
We’ve successfully validated the fix and are preparing to deploy it to all impacted environments. We’ll provide the next update as additional information becomes available.
Major May 5, 2026 herokuFeatureDisruption 1h 43m HEROKUDUBLIN, HEROKUEUROPE, HEROKUFRANKFURT, HEROKULONDON and 8 more
Started May 05, 2026, 02:56 PM UTC· resolved May 05, 2026, 04:39 PM UTC
- identified May 05, 2026, 02:56 PM UTC
Disruption Started: herokuFeatureDisruption
Major May 5, 2026 The rolling restart is currently underway for the remaining POD’s. We’re actively monitoring each environment post-restart to confirm full recovery. 1h 18m PDPUWAA, 10AYPD, 10AZPD, DUB01PD and 17 more
Started May 05, 2026, 04:55 AM UTC· resolved May 05, 2026, 06:13 AM UTC
- identified May 05, 2026, 04:55 AM UTC
Disruption Started: tableauServiceDisruption
- monitoring May 05, 2026, 04:57 AM UTC
At 03:13 UTC, May 5, 2026, we noted an issue impacting online Tableau Cloud services where multiple POD’s may be impacted due to Multi-Factor Authentication issues (MFA). Customers trying to log into their Tableau Cloud sites using MFA may have trouble with login issues. We're actively engaged and are exploring multiple paths to resolution. We’ll keep you posted in 30 minutes or sooner, once additional information is available.
- monitoring May 05, 2026, 05:23 AM UTC
Our initial investigation indicates that authentication requests to a backend verification service are failing with authorization errors preventing successful login attempts. We've initiated a rolling restart on one of the impacted PODs and initial testing looks positive. We're now proceeding with a rolling restart of services for the other impacted POD’s. We remain focused on stabilizing these services and are actively monitoring the environments. We’ll share the next update in 30 minutes or sooner, once additional information is available.
- monitoring May 05, 2026, 05:51 AM UTC
The rolling restart is currently underway for the remaining POD’s. We’re actively monitoring each environment post-restart to confirm full recovery. We’ll share the next update in 60 minutes or sooner as additional information is available.
Minor May 5, 2026 tableauFeatureDisruption 1h 6m 10AYPD
Started May 05, 2026, 02:44 AM UTC· resolved May 05, 2026, 03:51 AM UTC
- identified May 05, 2026, 02:44 AM UTC
Degradation Started: tableauPerformanceDegradation
Major May 5, 2026 We have determined that the issue is occurring due to insufficient infrastructure capacity. In collaboration with our third-party provider, we have rolled back a recent change, and are now monitoring 3h 9m BRA2S, BRA4S, BRA54S, BRA6S and 439 more
Started May 05, 2026, 01:00 AM UTC· resolved May 05, 2026, 04:10 AM UTC
- identified May 05, 2026, 01:00 AM UTC
Disruption Started: salesforceDataCloudFeatureDisruption
- monitoring May 05, 2026, 01:00 AM UTC
On May 1, 2026 at 15:15 UTC we detected a feature disruption impacting the Data Cloud CRM Connector. Customers may experience data stream jobs failing or getting stuck. We are investigating the issue to identify the cause and remediate the issue. We’ll provide an update in the next 60 minutes or sooner, if additional information becomes available.
- monitoring May 05, 2026, 01:54 AM UTC
We are continuing to work on identifying the cause of the issue, including partnering with our third-party provider to analyze logs to identify the cause of the errors. We’ll provide an update in the next 60 minutes or sooner, if additional information becomes available.
- monitoring May 05, 2026, 03:06 AM UTC
We have determined that the issue is occurring due to insufficient infrastructure capacity. In collaboration with our third-party provider, we have rolled back a recent change, and are now monitoring how jobs are performing. We’ll provide another update in the next 60 minutes or sooner, if additional information becomes available.
Major May 2, 2026 We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. 2h 40m POD276
Started May 02, 2026, 05:58 AM UTC· resolved May 02, 2026, 08:38 AM UTC
- identified May 02, 2026, 05:58 AM UTC
Degradation Started: performanceDegradation
- identified May 02, 2026, 06:30 AM UTC
Disruption Started: ccStorefrontSAndOrBusinessManagerUnavailable
- monitoring May 02, 2026, 06:30 AM UTC
This issue is impacting a subset of customers, and the service should be available for other users.
- monitoring May 02, 2026, 07:35 AM UTC
We identified the potential cause of the issue and are working on implementing a fix to resolve the impact to customers. We will provide an update in 30 minutes or sooner if we have more information.
Minor April 30, 2026 The rollback of the recent change is complete, however, an additional action to clear the org cache is required to bring customers out of impact. We're manually taking this step for all orgs on the im 6h 12m CAN2S, CAN70S, CAN86S, DEU6S and 8 more
Started Apr 30, 2026, 07:56 AM UTC· resolved Apr 30, 2026, 02:09 PM UTC
- identified Apr 30, 2026, 07:56 AM UTC
Degradation Started: featureServiceDisruption
- monitoring Apr 30, 2026, 08:22 AM UTC
We are investigating an issue affecting a subset of Industry Cloud customers using Vlocity Crisis Management Team (CMT) package features in sandbox environments who are unable to access those features and an error prompting them to contact an administrator. A recent managed package release is identified to be a potential trigger, and we’ve initiated a rollback on a test instance to validate whether this resolves the issue. That rollback is currently in progress. We will provide an update in 30 minutes or sooner if new information becomes available.
- monitoring Apr 30, 2026, 08:40 AM UTC
Further investigation shows the impact began earlier than initially understood. We have updated the Trust post to reflect the revised start time. We also identified a broader impact scope and updated the post to include additional impacted instances. Customers in these instances will receive ongoing communications for this incident. We will provide an update in 30 minutes or sooner if new information becomes available.
- monitoring Apr 30, 2026, 08:58 AM UTC
The rollback didn't fix the issue. We’ve identified a package licensing check is returning a false result. Investigations into the licensing and package issue are underway. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Apr 30, 2026, 09:45 AM UTC
We identified a broader impact scope than initially understood. We've updated the post to include the additional affected instances, and customers in those instances will receive ongoing incident communications.
- monitoring Apr 30, 2026, 10:41 AM UTC
We identified a licensing validation issue where the system incorrectly marks valid sandbox licenses as unlicensed, blocking access to these features. The affected check continues to return incorrect results in impacted environments while functioning correctly in healthy ones. Additional investigations have determined that the issue is also impacting Vlocity Communications, Media, and Energy (CME) and Insurance managed package features in sandbox environments. We’re analyzing the underlying service behavior and JAVA code path to determine the cause and to identify and revert any backend changes contributing to this situation. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Apr 30, 2026, 10:41 AM UTC
We identified a licensing validation issue where the system incorrectly marks valid sandbox licenses as unlicensed, blocking access to these features. The affected check continues to return incorrect results in impacted environments while functioning correctly in healthy ones. Additional investigations have determined that the issue is also impacting Vlocity Communications, Media, and Energy (CME) and Insurance managed package features in sandbox environments. We’re analyzing the underlying service behavior and JAVA code path to determine the cause and to identify and revert any backend changes contributing to this situation. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Apr 30, 2026, 11:09 AM UTC
The licensing validation issue, that was determined as the trigger of the issue, has been confirmed to be a result of a recent change. The team which implemented the change is being engaged and will revert the change on a test instance to establish whether this resolves the issue. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Apr 30, 2026, 12:12 PM UTC
We began reverting the recent change, which resulted in the licensing validation issue, at 11:31 UTC. Upon further investigation, we've identified additionally impacted instances and have added them to this messaging. We’ve also determined that the instance, CAN44, was incorrectly identified as affected by this issue. We'll now remove this instance as Industry Cloud customers on this instance, using this specific feature didn’t experience impact. Impacted instances will continue to be updated. We apologize for any inconvenience caused. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Apr 30, 2026, 01:12 PM UTC
The rollback of the recent change is complete, however, an additional action to clear the org cache is required to bring customers out of impact. We're manually taking this step for all orgs on the impacted instances. This is expected to take some time to complete. The next update will be upon significant update.
Major April 27, 2026 Investigations have highlighted that the impact radius is broader than initially understood and we've added DBs 51090, 51237, 51156, 51062, and 51081 to this posting. 2h 41m DB51002, DB51003, DB51006, DB51009 and 31 more
Started Apr 27, 2026, 12:34 PM UTC· resolved Apr 27, 2026, 03:15 PM UTC
- identified Apr 27, 2026, 12:34 PM UTC
Disruption Started: marketingCloudDisruption
- monitoring Apr 27, 2026, 12:41 PM UTC
We continue to investigate an issue impacting customers using Commerce Cloud and Core services in our France-based infrastructure. Network connectivity began restoring at 11:22 UTC following a power event at our data center. While network links have come back online, services remain in recovery. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Apr 27, 2026, 01:18 PM UTC
Investigations have highlighted that the impact radius is broader than initially understood and we've added DB51006 and DB51075 to this posting.
- monitoring Apr 27, 2026, 01:22 PM UTC
Monitoring for recovery of Marketing Cloud services is still ongoing and customers should be seeing signs of recovery. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Apr 27, 2026, 01:42 PM UTC
As of 12:46 UTC, all Marketing Cloud services are recovered. Out of an abundance of caution, we'll continue to monitor services for a further short period. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Apr 27, 2026, 01:47 PM UTC
Investigations have highlighted that the impact radius is broader than initially understood and we've added DB51038 and DB51219 to this posting.
- monitoring Apr 27, 2026, 02:10 PM UTC
Investigations have highlighted that the impact radius is broader than initially understood and we've added DBs 51090, 51237, 51156, 51062, and 51081 to this posting.
Minor April 27, 2026 Following a thorough investigation, we have determined that the scope of impact is narrower than initially thought. This post has been updated to reflect only the regions impacted. 1h 24m ANYPOINTMANAGEMENTCENTER-CA, ANYPOINTMANAGEMENTCENTER-EU, ANYPOINTMANAGEMENTCENTER-JP, ANYPOINTMANAGEMENTCENTER-US
Started Apr 27, 2026, 12:18 PM UTC· resolved Apr 27, 2026, 01:43 PM UTC
- identified Apr 27, 2026, 12:18 PM UTC
Degradation Started: muleSoftFeatureDegradation
- monitoring Apr 27, 2026, 12:56 PM UTC
Customers using Runtime Manager may be unable to load the Applications list in the Runtime Manager UI, or receive errors when calling the Applications Application Programming Interface (API) directly (/armui/api/v2/applications). Users can't view or manage deployed applications. Refreshing the page may reload the Applications list successfully; the UI auto-refresh may also surface data. Other Runtime Manager functions aren't affected. We're actively working on resolving the issue. We'll provide an update when additional information becomes available.
- monitoring Apr 27, 2026, 01:25 PM UTC
Following a thorough investigation, we have determined that the scope of impact is narrower than initially thought. This post has been updated to reflect only the regions impacted. We apologize if this caused any inconvenience.
Major April 27, 2026 We have determined that restarting services in place is the most effective path to resolution, and we are proceeding with this action now. A site-switch was not performed as we are resolving the issue 4h 31m POD313, FRA12S, FRA24S, FRA2S and 45 more
Started Apr 27, 2026, 11:27 AM UTC· resolved Apr 27, 2026, 03:58 PM UTC
- identified Apr 27, 2026, 11:27 AM UTC
Disruption Started: serviceDisruption
- monitoring Apr 27, 2026, 11:41 AM UTC
Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.
- monitoring Apr 27, 2026, 11:53 AM UTC
We're investigating a widespread service disruption impacting Commerce Cloud and Core Services in the France region. Customers are currently experiencing a full disruption and are unable to log in to or access their services. Initial investigations show that the issue is due to a power failure in the data center. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Apr 27, 2026, 12:05 PM UTC
Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.
- monitoring Apr 27, 2026, 12:41 PM UTC
We continue to investigate an issue impacting customers using Commerce Cloud and Core services in our France-based infrastructure. Network connectivity began restoring at 11:22 UTC following a power event at our data center. While network links have come back online, services remain in recovery. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Apr 27, 2026, 01:11 PM UTC
All Core services are recovered and available as of approximately 11:45 UTC. These instances will now be removed from this posting and will receive their own dedicated posting for this incident. Monitoring for recovery of Commerce Cloud services is still ongoing. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Apr 27, 2026, 01:40 PM UTC
We continue to work to fully restore Commerce Cloud services following the power issue at our data center in France. The majority of PODs are fully back online and under monitoring, and we're restarting services on PODs 248, 258 and 356 as they're still experiencing some latent impact. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Apr 27, 2026, 02:46 PM UTC
We've determined that a site-switch for PODs 248, 258, and 356 is the most appropriate action to get customers out of impact and we're proceeding with this action now. All other PODs remain out of impact. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Apr 27, 2026, 03:31 PM UTC
We have determined that restarting services in place is the most effective path to resolution, and we are proceeding with this action now. A site-switch was not performed as we are resolving the issue through these in-place restarts. During this process, customers will see services begin to return in a staggered phase, often before the full restart is complete. The current status of the remaining instances is as follows: PODs 313 and 356: These instances have been confirmed as restored and are under monitoring. POD 248: The restart is currently in progress. Customers may begin to see service recovery on this instance shortly.All other PODs remain stable. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
Minor April 21, 2026 The Salesforce Technology team is investigating a performance degradation that impacts Government Cloud Plus instances. This issue affects users utilizing .mil domain naming system (DNS) domains. The 3d 6h USA9402
Started Apr 21, 2026, 03:10 PM UTC· resolved Apr 24, 2026, 09:56 PM UTC
- investigating Apr 20, 2026, 01:42 PM UTC
featureServiceDisruption
- identified Apr 21, 2026, 03:10 PM UTC
Degradation Started: featureServiceDisruption
- monitoring Apr 21, 2026, 03:10 PM UTC
The Salesforce Technology team is investigating a performance degradation that impacts Government Cloud Plus instances. This issue affects users utilizing .mil domain naming system (DNS) domains. The Technology team is working with a third-party vendor to troubleshoot the issue. As a result of this issue, affected customers may encounter difficulties accessing their sites or may experience reduced performance. Customers who are utilizing .mil domain naming system (DNS) domains are advised to create a customer case with your .mil DNS vendor to help expedite the resolution. Further updates will be provided as more information becomes available.