Tableau Cloud Outage History
Tableau Cloud is up right nowPingoru has recorded 268 incidents for Tableau Cloud: 268 in the last 12 months and 106 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 570 (27%) |
Incidents, newest first
Minor June 19, 2026 We are aware of a feature degradation impacting Platform Events. As a result, some customers may experience Platform Events and Change Data Capture (CDC) events not being published intermittently. 23m USA866
Started Jun 19, 2026, 02:25 AM UTC· resolved Jun 19, 2026, 02:48 AM UTC
- identified Jun 19, 2026, 02:25 AM UTC
Degradation Started: featurePerfDegradation
- monitoring Jun 19, 2026, 02:26 AM UTC
We are aware of a feature degradation impacting Platform Events. As a result, some customers may experience Platform Events and Change Data Capture (CDC) events not being published intermittently. We are actively investigating the issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.
Minor June 19, 2026 We continue to roll out the fix across all impacted instances, and are monitoring progress until deployment is complete and services are fully stabilized. 9h 3m CAN20S, CAN2S, CAN4S, CAN6S and 282 more
Started Jun 19, 2026, 12:00 AM UTC· resolved Jun 19, 2026, 09:04 AM UTC
- identified Jun 19, 2026, 12:00 AM UTC
Degradation Started: featureServiceDisruption
- monitoring Jun 19, 2026, 12:01 AM UTC
We're investigating a feature disruption issue impacting our Data Cloud and Marketing Cloud customers. When deploying a stream, some users are encountering an error and are unable to complete this action. We're trying to reproduce the issue as an initial resolution step to support ongoing troubleshooting. We are also reviewing any recent changes that may be contributing to the issue while also looking into the full scope of the impact. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 19, 2026, 12:39 AM UTC
We believe we've identified the trigger of the issue impacting Data Cloud and Marketing Cloud streams. A recent code change incorrectly affects the handling of date-time and date-only fields, preventing new streams containing these field types from deploying successfully. We're developing a fix and it's currently in testing. Once validated, we will deploy this to all impacted instances. We also continue to assess the full scope of impact. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 19, 2026, 01:50 AM UTC
After further investigation, we narrowed the scope of impacted instances and confirmed that some instances are no longer considered impacted. We will exclude those instances from future communications. We apologize for any confusion this may have caused.
- monitoring Jun 19, 2026, 01:56 AM UTC
We have deployed a fix to prevent new Data Cloud and Marketing Cloud CRM Connector Streams containing date-time and date-only field types from being affected by this issue. We continue to assess streams that were created during the impact window, and our teams are actively working to restore those affected streams. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 19, 2026, 04:18 AM UTC
There are no additional updates at this time. Our teams continue to assess streams created during the impact window and are actively working to restore those that were affected. We will provide an update in 90 minutes or sooner if additional information becomes available.
- monitoring Jun 19, 2026, 07:26 AM UTC
We continue to roll out the fix across all impacted instances, and are monitoring progress until deployment is complete and services are fully stabilized. We will provide an update once the rollout is complete, or sooner if new information becomes available.
Minor June 18, 2026 The physical restoration activity is now complete. All storage systems are confirmed healthy and back online, with minor management tooling still being remediated. Customers may still see some degrada 34d 3h
Started Jun 18, 2026, 08:53 PM UTC· resolved Jul 23, 2026, 12:07 AM UTC
- identified Jun 18, 2026, 08:53 PM UTC
Degradation Started: featurePerfDegradation
- monitoring Jun 18, 2026, 09:10 PM UTC
We’re investigating an issue impacting multiple sandbox instances, where some customers may experience difficulties accessing some files uploaded to long-term file storage. We’ve identified this is linked to an issue with our third-party infrastructure provider, and they’re actively working to restore their services. Our team remains fully engaged and is collaborating closely with the vendor to restore the services as quickly as possible. We're actively monitoring the recovery and will share the next update as soon as new information is available
- monitoring Jun 19, 2026, 05:14 AM UTC
We remain fully engaged and are working in close coordination with the vendor to restore services as quickly as possible. We will continue to monitor the situation and provide an update as soon as new information becomes available.
- monitoring Jun 23, 2026, 04:54 AM UTC
We continue to make progress to restore services. We remain in close coordination with our third-party infrastructure provider and are actively working toward a resolution. Please note that the impact remains limited to customers with sandbox environments on a subset of instances, and there is no impact to production environments. We will provide an update within 24 hours or sooner as new information becomes available.
- monitoring Jun 24, 2026, 06:15 AM UTC
We continue to make progress toward restoring services and remain in close coordination with our third-party infrastructure provider as recovery efforts continue. The impact remains limited to customers with sandbox environments on a subset of instances, and there is no impact to production environments. We'll provide further updates upon significant developments or sooner as new information becomes available.
- monitoring Jun 25, 2026, 03:20 AM UTC
We continue to make steady progress in restoring services and remain closely engaged with our third-party infrastructure provider. The impact is limited to customers with sandbox environments on a subset of instances. Production environments remain unaffected. We will provide additional updates as significant developments occur or sooner if new information becomes available.
- monitoring Jun 25, 2026, 07:18 PM UTC
Restoration efforts with our third-party infrastructure provider continue to move forward. Current information on restoration timelines, milestones, and permanent remediation suggests that completion is expected within several weeks. The impact is limited to sandbox environments, and production services remain unaffected. We'll provide additional updates as significant developments occur or sooner if new information becomes available.
- monitoring Jul 08, 2026, 02:46 AM UTC
Our restoration efforts with our third-party infrastructure provider are progressing. A temporary solution to restore power to the affected data center is being developed, with an estimated target of mid-July 2026 to restore customer access and services. A permanent repair requiring replacement of damaged electrical components is also underway and will involve a longer timeline. The impact remains limited to sandbox environments, and production services continue to be unaffected. We will provide an update as significant developments occur or sooner if new information becomes available.
- monitoring Jul 13, 2026, 07:27 AM UTC
Our restoration efforts with our third-party infrastructure provider continue to make steady progress. Power has been successfully restored to the DCC modules at the impacted data center, and core network infrastructure has been validated and confirmed operational. We're looking into a problem with the certificate that is given to the data center hosts. This problem is affecting how some network devices are authenticated. Recovery activities remain on schedule, with full restoration of the impacted modules expected by the end of July 16, pending successful completion of the remaining recovery activities. The impact remains limited to sandbox environments, and production services continue to be unaffected. We'll provide an update as significant developments occur or sooner if new information becomes available.
- monitoring Jul 16, 2026, 10:52 PM UTC
Restoration activities with our third-party infrastructure provider continue to make progress. Most affected infrastructure modules have now been powered on, and services are being restored in phases as dependent infrastructure components are brought back online and validated. Recovery work is currently focused on resolving the remaining infrastructure dependencies required to complete sandbox service restoration. The impact remains limited to sandbox environments, and production services continue to be unaffected. We will provide another update as significant developments occur or sooner if new information becomes available.
- monitoring Jul 22, 2026, 12:04 AM UTC
The physical restoration activity is now complete. All storage systems are confirmed healthy and back online, with minor management tooling still being remediated. Customers may still see some degradation as a subset of database services are still to be restarted, so services are not yet considered fully recovered. Long-term restoration activity remains underway and will take several months to complete. We will provide a new update once we can confirm that all database services have been restored. We understand the impact this extended degradation has had and sincerely apologize for the impact this has caused on our customers.
Minor June 18, 2026 We're aware of an issue affecting the Salesforce Core service. As a result, customers may experience intermittent timeouts when accessing Salesforce services. We are actively investigating potential t 26m USA710S, USA712S, USA750S, USA752S and 71 more
Started Jun 18, 2026, 06:22 PM UTC· resolved Jun 18, 2026, 06:49 PM UTC
- identified Jun 18, 2026, 06:22 PM UTC
Degradation Started: performanceDegradation
- monitoring Jun 18, 2026, 06:22 PM UTC
We're aware of an issue affecting the Salesforce Core service. As a result, customers may experience intermittent timeouts when accessing Salesforce services. We are actively investigating potential triggers and working to restore full service functionality. We'll provide an update in 30 minutes or sooner if additional information becomes available.
Minor June 18, 2026 Deployment of the fix continues for the remaining impacted production instances. Teams have made additional progress restoring service and are actively addressing the database connection errors affect 14h 55m BRA2S, BRA4S, BRA54S, BRA6S and 611 more
Started Jun 18, 2026, 02:58 PM UTC· resolved Jun 19, 2026, 05:53 AM UTC
- identified Jun 18, 2026, 02:58 PM UTC
Degradation Started: featurePerfDegradation
- monitoring Jun 18, 2026, 03:01 PM UTC
We're aware of an issue impacting agents using record pages within Salesforce following a recent release. Customers are encountering unexpected additional pop-ups when completing activities, preventing them from working normally within the product. We're working on a fix that'll be rolled out to Hyperforce and the remaining instances will receive the fix during the standard release window. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 18, 2026, 03:30 PM UTC
We've begun deploying a fix to a prioritized group of impacted HyperForce instances and some customers have begun to recover. We're actively preparing for an expedited deployment to all remaining impacted production instances. We'll provide an update in 30 minutes or sooner if additional information becomes available
- monitoring Jun 18, 2026, 03:49 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 Jun 18, 2026, 04:16 PM UTC
We're continuing to deploy the fix to all remaining impacted production instances as quickly as possible. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 18, 2026, 05:09 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 Jun 18, 2026, 05:42 PM UTC
We've expanded deployment of the fix to all the remaining impacted instances. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 18, 2026, 06:11 PM UTC
Deployment of the fix to all remaining impacted production instances remains in progress. Some instances have encountered issues and teams are working to address these database (DB) connection errors. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 18, 2026, 07:52 PM UTC
Impact to Service Cloud agent pop-ups from this incident resolved on June 18, 2026 for a subset of impacted instances. For full details on resolved instances, please visit the Trust post here: https://status.salesforce.com/incidents/20004126 Remediation is still actively in progress for the remaining impacted instances. We'll continue to provide updates as additional instances are restored.
- monitoring Jun 18, 2026, 08:33 PM UTC
Impact to Service Cloud agent pop-ups from this incident resolved on June 18, 2026 for a subset of impacted instances. For full details on resolved instances, please visit the Trust post here: https://status.salesforce.com/incidents/20004130 Remediation is still actively in progress for the remaining impacted instances. We'll continue to provide updates as additional instances are restored.
- monitoring Jun 18, 2026, 10:48 PM UTC
Impact to Service Cloud agent pop-ups from this incident resolved on June 18, 2026 for a subset of impacted instances. For full details on resolved instances, please visit the Trust post here: https://status.salesforce.com/incidents/20004133 Remediation is still actively in progress for the remaining impacted instances. We'll continue to provide updates as additional instances are restored.
- monitoring Jun 18, 2026, 10:49 PM UTC
Deployment of the fix continues for the remaining impacted production instances. Teams have made additional progress restoring service and are actively addressing the database connection errors affecting a subset of instances during deployment. Impact to Service Cloud agent pop-ups has now been resolved for additional groups of customers, and restoration efforts remain focused on the remaining impacted instances. We are closely monitoring instance health as remediation progresses and working to restore all affected customers as quickly as possible. We'll continue to provide updates as additional instances are restored.
Major June 18, 2026 We have completed the restoration of services across all affected B2C Commerce Cloud PODs. Our teams are continuing to monitor the environments to confirm full stability. 4h 12m POD313, POD219, POD234, POD253 and 35 more
Started Jun 18, 2026, 01:36 AM UTC· resolved Jun 18, 2026, 05:49 AM UTC
- identified Jun 18, 2026, 01:36 AM UTC
Degradation Started: featurePerfDegradation
- monitoring Jun 18, 2026, 01:53 AM UTC
We are aware of a service disruption that began impacting B2C Commerce Cloud. As a result, customers may be unable to access their Commerce Cloud Storefronts and services. We're actively working to restore full service availability. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 18, 2026, 02:03 AM UTC
We've identified an infrastructure configuration issue impacting a subset of our PODs. We are actively working to restore affected services. We're currently validating our recovery approach on a subset of environments before applying the fix more broadly. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 18, 2026, 02:35 AM UTC
We're continuing to make progress in restoring services. Infrastructure configuration issue prevented a subset of PODs from completing a planned update, which caused those PODs to enter an unhealthy state. We’ve successfully restored a subset of affected PODs and are actively working through the remaining impacted PODs. We're executing the restoration process in parallel to bring all affected services back online as quickly as possible. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 18, 2026, 03:24 AM UTC
We are continuing to make progress in restoring services. We have successfully restored services on a subset of PODs, and we're actively working through the remaining impacted environments. We are executing the restoration process in parallel to bring all affected services back online as quickly as possible. As PODs are restored, we are publishing individual Trust posts for each instance to accurately capture the service restoration time. Customers on restored instances should refer to their instance-specific post for the end time of this disruption and confirmation that services have been restored. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 18, 2026, 04:51 AM UTC
We have completed the restoration of services across all affected B2C Commerce Cloud PODs. Our teams are continuing to monitor the environments to confirm full stability. Additionally, we want to make customers aware that as a result of this incident, some instances may not have been updated to the latest planned software release version. Reschedule information for the release update will be provided as soon as feasible. Customers who notice they remain on the previous version should expect to receive further communication with updated timings. We apologize for how this incident may have affected you and your business. We will 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 Jun 18, 2026, 05:10 AM UTC
We have completed the restoration of services across all affected B2C Commerce Cloud PODs. Our teams are continuing to monitor the environments to confirm full stability. Additionally, we want to make customers aware that because of this incident, some PODs may not have been updated to the latest planned software release version. Reschedule information for the release update will be provided as soon as feasible. Customers who notice they remain on the previous version should expect to receive further communication with updated timings. We apologize for how this incident may have affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
Minor June 17, 2026 We’ve deployed a service configuration fix across all impacted instances. The fix is designed to resolve the memory issue causing intermittent errors for customers. We're currently monitoring health m 1h 31m BRA2S, BRA4S, BRA54S, BRA6S and 419 more
Started Jun 17, 2026, 10:50 PM UTC· resolved Jun 18, 2026, 12:22 AM UTC
- identified Jun 17, 2026, 10:50 PM UTC
Degradation Started: featurePerfDegradation
- monitoring Jun 17, 2026, 10:55 PM UTC
We're aware of an issue impacting Agentforce. A subset of customers may encounter a "Something went wrong, please try again" error when accessing Agentforce across multiple instances. We're actively investigating potential triggers. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 17, 2026, 11:32 PM UTC
We continue to investigate this issue. We have deployed a fix on one of the impacted instances and are currently monitoring performance. If successfully validated, we will deploy the fix to all impacted instances to restore services as quickly as possible for customers. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 17, 2026, 11:59 PM UTC
We’ve deployed a service configuration fix across all impacted instances. The fix is designed to resolve the memory issue causing intermittent errors for customers. We're currently monitoring health metrics across instances that have received the fix so far. We'll provide an update in 30 minutes or sooner if additional information becomes available.
Minor June 17, 2026 CCServiceDegradationManagedRuntime 25m MANAGEDRUNTIMEAMER, MANAGEDRUNTIMEAPAC, MANAGEDRUNTIMEEMEA
Started Jun 17, 2026, 04:03 PM UTC· resolved Jun 17, 2026, 04:28 PM UTC
- identified Jun 17, 2026, 04:03 PM UTC
Degradation Started: CCServiceDegradationManagedRuntime
Minor June 17, 2026 The fix is progressing through our Emergency Release process and has entered the build process. We expect this process to take several hours, and we continue to closely monitor its progress. 19h 6m USA9402, EU54, BRA2S, BRA4S and 857 more
Started Jun 17, 2026, 10:34 AM UTC· resolved Jun 18, 2026, 05:41 AM UTC
- identified Jun 17, 2026, 10:34 AM UTC
Degradation Started: featurePerfDegradation
- monitoring Jun 17, 2026, 10:52 AM UTC
We identified an issue introduced in a recent release that impacts the creation of new second-generation managed and unlocked package versions. Customers who develop and distribute applications on the Salesforce platform may be unable to create new versions of their managed or unlocked packages if those packages depend on another package that includes a connected app. This issue does not affect customers who are not creating new package versions or whose packages do not have this dependency. We’re developing and validating a fix before deployment. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 17, 2026, 11:52 AM UTC
We’ve verified a fix for this issue and are progressing through the Emergency Release process to obtain the necessary approvals for deployment. The fix requires a code change, which we are developing and validating in a test environment before deploying to production. This validation ensures the fix resolves the issue without introducing additional impact and will take some time to complete. Upon further investigation, we've determined that the start time of impact is different than initially understood. We’ve now aligned the start time to the recent release that went out during the weekend to more accurately reflect on Trust. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 17, 2026, 12:35 PM UTC
The fix is progressing through our Emergency Release process and has entered the build process. We expect this process to take several hours, and we continue to closely monitor its progress. Once the build completes, we'll deploy and validate the fix in a sandbox environment before proceeding with the broader deployment across all impacted instances. This validation will help ensure the issue is fully resolved before wider rollout. We'll provide our next update as soon as additional information becomes available.
Minor June 15, 2026 We're seeing signs of recovery as we address the problematic jobs on the FRA instances, while a subset of customers on the remaining impacted instances may continue to experience high wait times with 3h 16m FRA12S, FRA98S, USA244S, USA252S and 11 more
Started Jun 15, 2026, 09:01 AM UTC· resolved Jun 15, 2026, 12:17 PM UTC
- identified Jun 15, 2026, 09:01 AM UTC
Degradation Started: performanceDegradation
- monitoring Jun 15, 2026, 09:50 AM UTC
and a database overload impacting multiple instances in the eu-west-3, and eu-central-1 regions, triggered by a recent change. We're actively working to reduce database load and restore normal processing. We'll provide an update in 30 minutes or sooner, if additional information becomes available.
- monitoring Jun 15, 2026, 10:07 AM UTC
Customers are experiencing high wait times, with message queue (MQ) processing halted on affected cells.. Investigations have highlighted that the impact radius is broader than initially understood. We've updated the posting to reflect additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.
- monitoring Jun 15, 2026, 10:10 AM UTC
Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.
- monitoring Jun 15, 2026, 10:14 AM UTC
Investigations have highlighted that the impact radius is narrower than initially understood. We will now remove DEU112, USA80S, USA244S, USA252S, and USA876 that haven't 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. We'll provide an update in 30 minutes or sooner, if additional information becomes available.
- monitoring Jun 15, 2026, 10:35 AM UTC
We're continuing to work to reduce database load and restore normal processing by addressing problematic jobs on the impacted instances. We apologize for how you and your business may be affected by this incident. We'll provide an update in 30 minutes or sooner, if additional information becomes available.
- monitoring Jun 15, 2026, 10:42 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 Jun 15, 2026, 11:04 AM UTC
We're actively addressing the problematic jobs on the impacted instances and are seeing signs of service recovery. As a preventive measure, we will terminate non-essential background jobs to avoid further degradation and support continued stabilization. We'll provide an update in 30 minutes or sooner, if additional information becomes available.
- monitoring Jun 15, 2026, 11:40 AM UTC
We're seeing signs of recovery as we address the problematic jobs on the FRA instances, while a subset of customers on the remaining impacted instances may continue to experience high wait times with message queue (MQ) processing halted. Investigations have highlighted that the impact radius is broader than initially understood. We've updated this posting to reflect additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward. We'll provide an update in 30 minutes or sooner, if additional information becomes available.
Minor June 14, 2026 We have identified that specific app servers on the AP60 instance are generating errors. Restarting the first affected app server successfully stopped the errors on that server, confirming our approac 2h 1m AP60
Started Jun 14, 2026, 06:34 AM UTC· resolved Jun 14, 2026, 08:36 AM UTC
- identified Jun 14, 2026, 06:34 AM UTC
Degradation Started: performanceDegradation
- monitoring Jun 14, 2026, 06:45 AM UTC
We are aware that customers on AP60 are experiencing a high volume of errors when performing actions such as saving records, creating new records, and updating records. Users may be able to retry operations to temporarily work around errors. We are actively investigating the technical trigger and our teams are working on remediation steps, including an app server restart. We will provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 14, 2026, 07:29 AM UTC
We have identified that specific app servers on the AP60 instance are generating errors. Restarting the first affected app server successfully stopped the errors on that server, confirming our approach. Based on this success, we have initiated a rolling restart of all app servers on the AP60 instance. We will provide an update once the process is completed for all app servers or if additional information becomes available.
Minor June 13, 2026 At 06:14 UTC on June 12, 2026, a feature degradation began impacting Object Store v2. As a result, customers are unable to store or retrieve keys that contain special characters. 45m OBJECTSTOREV2-CA, OBJECTSTOREV2-US
Started Jun 13, 2026, 11:52 AM UTC· resolved Jun 13, 2026, 12:37 PM UTC
- identified Jun 13, 2026, 11:52 AM UTC
Degradation Started: muleSoftFeatureDegradation
- monitoring Jun 13, 2026, 12:01 PM UTC
At 06:14 UTC on June 12, 2026, a feature degradation began impacting Object Store v2. As a result, customers are unable to store or retrieve keys that contain special characters. We have identified the technical trigger and a fix has been prepared. We are in the process of deploying it to all affected regions. There is no workaround available at this time. We will provide an update in 30 minutes or sooner if additional information becomes available.
Minor June 12, 2026 The investigation into why API Manager alerts are not triggering as expected is ongoing, alongside active troubleshooting efforts. 4h 56m ANYPOINTMANAGEMENTCENTER-US
Started Jun 12, 2026, 04:47 PM UTC· resolved Jun 12, 2026, 09:44 PM UTC
- identified Jun 12, 2026, 04:47 PM UTC
Degradation Started: muleSoftFeatureDegradation
- monitoring Jun 12, 2026, 04:47 PM UTC
Issue: We are aware of an issue affecting the Anypoint Management Center US that began on June 12 at 15:20 UTC. Impact: Customers in US production environments are experiencing an inability to list their applications in Runtime Manager within Anypoint Management Center US. Deployments to new API Omni Gateway (Flex) are also unavailable. Existing running applications are not impacted by this issue. We'll provide another update in 60 minutes or sooner if more information becomes available.
- monitoring Jun 12, 2026, 05:26 PM UTC
We are continuing to investigate the trigger for this incident and have determined that new Runtime deployments and customer alerts on Runtime Manager may be impacted as well. We'll provide another update in 60 minutes or sooner if more information becomes available.
- monitoring Jun 12, 2026, 06:23 PM UTC
We have identified the potential trigger for this incident and have taken action to mitigate impact. We are seeing improvements, but are continuing to monitor the environment to ensure the issue is resolved. We'll provide another update in 60 minutes or sooner if more information becomes available.
- monitoring Jun 12, 2026, 07:50 PM UTC
We have confirmed that all issues affecting the Anypoint Management Center US aside from API Manager alerts failing to trigger correctly have been resolved. We are continuing to investigate the API Manager Alerts and will provide another update in 60 minutes or sooner if more information becomes available.
- monitoring Jun 12, 2026, 09:13 PM UTC
The investigation into why API Manager alerts are not triggering as expected is ongoing, alongside active troubleshooting efforts. We will provide another update in 60 minutes or sooner if more information becomes available.
Minor June 11, 2026 We've identified a source of excessive service usage and have taken steps to address this. We're monitoring and we'll provide an update in 30 minutes or sooner if additional information becomes availa 17m DEU104S, DEU10S, DEU114S, DEU116S and 49 more
Started Jun 11, 2026, 02:30 PM UTC· resolved Jun 11, 2026, 02:48 PM UTC
- identified Jun 11, 2026, 02:30 PM UTC
Degradation Started: featureServiceDisruption
- monitoring Jun 11, 2026, 02:31 PM UTC
We're aware of an issue affecting agents using Messaging in our Core service. As a result, agents are unable to close active Messaging sessions from the UI. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 11, 2026, 02:35 PM UTC
We've identified a source of excessive service usage and have taken steps to address this. We're monitoring and we'll provide an update in 30 minutes or sooner if additional information becomes available.
Major June 10, 2026 We noted an issue impacting Salesforce Field Services (SFS) Mobile on multiple instances. SFS Mobile customers who have the performance priming feature enabled may observe failures when using the sync 25m GBR76, USA324
Started Jun 10, 2026, 10:39 PM UTC· resolved Jun 10, 2026, 11:04 PM UTC
- identified Jun 10, 2026, 10:39 PM UTC
Disruption Started: FieldServiceMobileFeatureDisruption
- monitoring Jun 10, 2026, 10:39 PM UTC
We noted an issue impacting Salesforce Field Services (SFS) Mobile on multiple instances. SFS Mobile customers who have the performance priming feature enabled may observe failures when using the syncing feature within the SFS Mobile application. We’ve identified the technical trigger as a recent deployment, and are performing rollbacks as our primary solution. We’ll provide an update in 30 minutes or sooner as additional information becomes available.
Minor June 10, 2026 We continue to prepare for the daily deployment. We will provide a new update once we have visibility of whether the fix has been deployed and validated, or sooner if new information becomes available 20h 16m CS236, CS237, CS239, CS240 and 42 more
Started Jun 10, 2026, 07:14 AM UTC· resolved Jun 11, 2026, 03:31 AM UTC
- identified Jun 10, 2026, 07:14 AM UTC
Degradation Started: featureServiceDisruption
- monitoring Jun 10, 2026, 08:35 AM UTC
We're currently investigating an issue impacting the Shopper Agent feature, which allows users to interact with a chat-based assistant to search for and discover products on their Storefront, is currently not responding. Customers may be unable to receive responses from the Shopper Agent Guided Chat experience, impacting AI-powered shopping assistance, product recommendations, and related conversational commerce workflows. This is a feature that commerce customers deploy to their storefronts. We have identified a change introduced as part of a recent release as the cause of the issue and are actively working on a fix to restore normal functionality.
- monitoring Jun 10, 2026, 09:17 AM UTC
We’ve confirmed the issue is across multiple instances including production and linked to a permission configuration change introduced as part of a recent release. Due to related database considerations, a rollback is not a viable option. We’re currently working on an emergency release to restore the permission configuration, which is estimated to take several hours to build, validate, and deploy. We will provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 10, 2026, 10:29 AM UTC
We continue our efforts to prepare the fix and deploy it via an Emergency Release. Testing and approval activities are in progress. Following that, the plan is to deploy the ERR to all the impacted instances where this release was deployed, which is expected to take several hours. We’ll provide an update as soon as significant new information becomes available.
- monitoring Jun 10, 2026, 12:13 PM UTC
The fix has been successfully validated in a test environment. We're working to secure the necessary approvals to include this fix in the next scheduled deployment at 15:00 UTC. We'll provide an update following the deployment of the fix to the impacted instances.
- monitoring Jun 10, 2026, 03:48 PM UTC
The fix will be implemented with the next daily deployment, which is scheduled to begin at 00:30 UTC on June 11, 2026. We'll provide an update following the deployment of the fix, or sooner if additional information becomes available.
- monitoring Jun 11, 2026, 01:56 AM UTC
We continue to prepare for the daily deployment. We will provide a new update once we have visibility of whether the fix has been deployed and validated, or sooner if new information becomes available. We apologize for any inconvenience this issue is causing to customers.
Minor June 9, 2026 User messages sent via WhatsApp may continue to see some delay or unexpected results. 2h 38m BRA2S, BRA4S, BRA54S, BRA6S and 14 more
Started Jun 09, 2026, 04:58 PM UTC· resolved Jun 09, 2026, 07:37 PM UTC
- identified Jun 09, 2026, 04:58 PM UTC
Degradation Started: einsteinBots
- monitoring Jun 09, 2026, 05:24 PM UTC
The Einstein Bots performance degradation is related to connection to WhatsApp. User messages sent via WhatsApp may be either delayed, dropped, or not processed by the Agentforce bot, which is causing customers to be stalled mid-conversation with no error. Engineering has identified the trigger and is taking corrective action to increase capacity to mitigate this issue. Initial monitoring is showing positive results. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 09, 2026, 06:49 PM UTC
User messages sent via WhatsApp may continue to see some delay or unexpected results. While the increases in capacity that were implemented had initially shown positive results, our monitoring still shows some increased errors. We are moving forward with further additions to capacity for chatbot services. We’ll provide an update in 60 minutes or sooner if additional information becomes available.
Minor June 9, 2026 Storefronts are no longer in impact. Non-disruptive rolling restarts continue to complete the revert of the runtime environment to the previous version. Granular Data Replication remains temporarily u 8h 23m POD217, POD297
Started Jun 09, 2026, 12:18 PM UTC· resolved Jun 09, 2026, 08:42 PM UTC
- identified Jun 09, 2026, 12:18 PM UTC
Degradation Started: performanceDegradation
- monitoring Jun 09, 2026, 12:29 PM UTC
We're aware of an issue impacting Commerce Cloud customers on some pods. As a result, customers are experiencing intermittent Storefront unavailability, with sites going down for periods ranging from 30 minutes to an hour. We've deactivated a replication feature on impacted pods as an interim measure to reduce further Storefront impact. We're also working to revert the runtime environment on impacted pods back to a previous version, and have begun updating pod configuration files and restarting application servers to validate this change. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 09, 2026, 01:05 PM UTC
The cause has been identified as a behavior change introduced by a recent runtime upgrade. To reduce further impact, we've disabled a replication feature for affected customers., We're now preparing a fix to revert the runtime environment to its previous version, which will take approximately 90 minutes to deploy and will be followed by a non-disruptive rolling restart across the impacted PODs. We'll provide an update in 30 minutes, or sooner if new information becomes available.
- monitoring Jun 09, 2026, 01:57 PM UTC
We’re reverting the runtime environment to its previous version across all impacted PODs via a fix that is estimated to take 45 minutes followed by a non-disruptive rolling restart. As a temporary measure, we have proactively disabled the Granular Data Replication feature to reduce further Storefront impact for affected customers We'll provide our next update in 30 minutes, or sooner if new information becomes available.
- monitoring Jun 09, 2026, 02:47 PM UTC
Storefronts were confirmed out of impact at 13:41 UTC. Granular Data Replication remains temporarily unavailable. Non-disruptive rolling restarts are now in progress on affected PODs to complete the revert of the runtime environment to the previous version. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 09, 2026, 03:51 PM UTC
Storefronts are no longer in impact. Non-disruptive rolling restarts continue to complete the revert of the runtime environment to the previous version. Granular Data Replication remains temporarily unavailable, this will be re-enabled after validation of restart completion. We will provide an update once the restarts are complete, or sooner if additional information becomes available.
Minor June 9, 2026 We're continuing to investigate the recurrence of slow page load times customers are experiencing. We have identified increased traffic levels as a contributing factor and have implemented mitigation 1h 27m CAN4S
Started Jun 09, 2026, 04:11 AM UTC· resolved Jun 09, 2026, 05:38 AM UTC
- identified Jun 09, 2026, 04:11 AM UTC
Degradation Started: performanceDegradation
- monitoring Jun 09, 2026, 04:41 AM UTC
We are investigating a recurrence of performance degradation across multiple instances. Impacted users are experiencing elevated Average Page Times (APTs) when using managed packages on Salesforce services. Our teams are actively reviewing the cause of the recurrence and working to mitigate the impact. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 09, 2026, 05:11 AM UTC
We're continuing to investigate the recurrence of slow page load times customers are experiencing. We have identified increased traffic levels as a contributing factor and have implemented mitigation measures across the impacted instances to help stabilize performance. We're actively monitoring the environment and evaluating the effectiveness of these actions as our investigation continues. We'll provide an update in 60 minutes or sooner if additional information becomes available.
Minor June 8, 2026 We believe that we've identified the root cause of the slow page load times customers are experiencing when using managed packages on Core services. Multiple orgs running package installations simulta 4h 8m CAN20S, CAN4S, CAN8S
Started Jun 08, 2026, 11:19 PM UTC· resolved Jun 09, 2026, 03:27 AM UTC
- identified Jun 08, 2026, 11:19 PM UTC
Degradation Started: performanceDegradation
- monitoring Jun 08, 2026, 11:19 PM UTC
We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.
- monitoring Jun 09, 2026, 01:12 AM UTC
We are investigating a performance degradation on multiple instances, where users are experiencing high Average Page Times (APTs) when using managed packages on Salesforce services. We believe this may be due to a recent change and are investigating to identify the root cause and take remediation actions. We will provide an update in 30 minutes, or as soon as new information becomes available.
- monitoring Jun 09, 2026, 02:02 AM UTC
We believe that we've identified the root cause of the slow page load times customers are experiencing when using managed packages on Core services. Multiple orgs running package installations simultaneously are causing the database to become overloaded, resulting in response times above normal thresholds. We've applied a throttle to the affected instances to limit the number of concurrent package installations and reduce the load on the database. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 09, 2026, 02:29 AM UTC
We're continuing to investigate the slow page load times customers are experiencing. We’ve identified that the issue is being driven by a high volume of automated requests targeting a specific page used for package installations. We've applied rate limits across the affected instances, and additional traffic mitigation actions are underway. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 09, 2026, 02:29 AM UTC
We believe that we've identified the root cause of the slow page load times customers are experiencing when using managed packages on Core services. Multiple orgs running package installations simultaneously are causing the database to become overloaded, resulting in response times well above normal thresholds. We've applied a throttle to the affected instances to limit the number of concurrent package installations and reduce the load on the database. We'll provide an update in 30 minutes or sooner if additional information becomes available.
Minor June 7, 2026 We continue to address a feature degradation affecting Marketing Cloud customers on two Hyperforce stacks. Links embedded in emails are redirecting to an error page, and open and click tracking data i 5h 13m DB401000, DB401001, DB401002, DB401003 and 34 more
Started Jun 07, 2026, 09:34 AM UTC· resolved Jun 07, 2026, 02:47 PM UTC
- identified Jun 07, 2026, 09:34 AM UTC
Degradation Started: marketingCloudFeatureDegradation
- monitoring Jun 07, 2026, 01:20 PM UTC
At 22:31 UTC, June 06, 2026, a feature degradation began impacting Marketing Cloud customers on two Hyperforce stacks. As a result, links embedded in marketing emails are not redirecting recipients to the intended destination - recipients are landing on an error page instead. We are actively working to address this issue. We will provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Jun 07, 2026, 01:53 PM UTC
We continue to address a feature degradation affecting Marketing Cloud customers on two Hyperforce stacks. Links embedded in emails are redirecting to an error page, and open and click tracking data is not being recorded. Our teams have applied a configuration change intended to allow new email sends to function correctly going forward. We are currently validating that this change is working as expected. We are also continuing to investigate the technical trigger to determine the best path to resolution. We will provide an update in 30 minutes or sooner if additional information becomes available.
Major June 7, 2026 maintenanceOverrunServiceDisruptionBegan 1h 35m PDUKAA
Started Jun 07, 2026, 12:56 AM UTC· resolved Jun 07, 2026, 02:31 AM UTC
- identified Jun 07, 2026, 12:56 AM UTC
Disruption Started: maintenanceOverrunServiceDisruptionBegan
Minor June 5, 2026 We continue to deploy the fix across all remaining instances while closely monitoring system performance to ensure stability. 7h ARE6, AUS102, AUS58, AUS60 and 260 more
Started Jun 05, 2026, 09:15 PM UTC· resolved Jun 06, 2026, 04:15 AM UTC
- identified Jun 05, 2026, 09:15 PM UTC
Degradation Started: performanceDegradation
- monitoring Jun 05, 2026, 09:46 PM UTC
We’re investigating a performance degradation impacting multiple instances. During this time, a subset of customers using Search Analytics may experience a delay in their search interaction results between May 18, 2026, and May 28, 2026. While new data on the Data Lake Object (DLO) is flowing correctly following the resolution of a previous incident, the historical data from that window is currently being restored. We’ve successfully validated a fix in one of our production environments and are deploying it across the remaining impacted instances. We’ll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 05, 2026, 10:46 PM UTC
We’re actively deploying the fix across all remaining instances while closely monitoring system performance to ensure stability. We’ll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 06, 2026, 01:32 AM UTC
We continue to deploy the fix across all remaining instances while closely monitoring system performance to ensure stability. We’ll provide an update once additional information becomes available.
Minor June 5, 2026 A feature degradation is causing complete failures for customers attempting to use activations to Meta Custom Audiences (also referred to as Facebook activations). 3h 41m AUS102, AUS58, AUS60, AUS76 and 46 more
Started Jun 05, 2026, 05:14 PM UTC· resolved Jun 05, 2026, 08:55 PM UTC
- identified Jun 05, 2026, 05:14 PM UTC
Degradation Started: salesforceDataCloudFeatureDegradation
- monitoring Jun 05, 2026, 05:14 PM UTC
A feature degradation is causing complete failures for customers attempting to use activations to Meta Custom Audiences (also referred to as Facebook activations).
Minor June 5, 2026 We have identified some new errors in the past 15 minutes, and we’re investigating the cause of the issue. 13h 19m ANYPOINTMANAGEMENTCENTER-EU, ANYPOINTMANAGEMENTCENTER-US
Started Jun 05, 2026, 12:34 PM UTC· resolved Jun 06, 2026, 01:53 AM UTC
- identified Jun 05, 2026, 12:34 PM UTC
Degradation Started: muleSoftFeatureDegradation
- monitoring Jun 05, 2026, 12:38 PM UTC
We're aware of an issue impacting Anypoint Monitoring and Runtime Manager. Customers can't view metric panels in the Anypoint Monitoring dashboard in the US and EU, and US customers can't see their applications in Runtime Manager. As a partial workaround for monitoring metrics, customers can use Anypoint Monitoring Insights. We're investigating a connectivity issue as the likely cause and our teams are actively working toward resolution. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 05, 2026, 12:51 PM UTC
In addition to previous guidance for monitoring, as a partial workaround for Runtime Manager, customers can use Anypoint Insights to search for their application and access it via the Manage Application link. We're continuing to work towards resolution and will provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 05, 2026, 01:50 PM UTC
Investigations have highlighted that a recently expired certificate may be the trigger and we're exploring this further. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 05, 2026, 02:21 PM UTC
We've confirmed the expired certificate as the trigger. At 14:09 UTC, we began redeploying the affected services with a renewed certificate. Impacted EU services are now beginning to recover. We're deploying the fix to the US shortly. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 05, 2026, 02:53 PM UTC
We've completed redeploying the affected services with a renewed certificate to the US, and impacted services there are now beginning to recover. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 05, 2026, 03:55 PM UTC
Anypoint Monitoring dashboards have recovered in the EU and are showing signs of recovery in the US. We continue to monitor for full recovery and provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 05, 2026, 04:50 PM UTC
We continue to monitor the US region for full recovery. In the interim, the workaround remains available where customers can use Anypoint Insights to search for their application and access it via the Manage Application link. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 05, 2026, 05:44 PM UTC
We continue to monitor for full recovery in the US region. During this investigation, a separate issue affecting the application list display in Runtime Manager was identified and is being actively investigated. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 05, 2026, 06:44 PM UTC
We continue to investigate the remaining issue affecting the application list display in Runtime Manager in the US region. Affected customers are unable to view their applications in the Runtime Manager UI; however, applications continue to run and are not impacted. We are actively working to restore full functionality. We'll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 05, 2026, 07:46 PM UTC
We're continuing to investigate the trigger of this issue and evaluating multiple remediation paths to restore services. We'll provide an update in 120 minutes or sooner if additional information becomes available.
- monitoring Jun 05, 2026, 10:04 PM UTC
We've deployed an initial fix, and are monitoring health metrics. Our teams are noting positive signals, and some customers may observe signs of recovery when loading the application list display in Runtime Manager. We are adding capacity to our services in an attempt to alleviate impact. Thank you for your patience as we work through this incident. We’ll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 05, 2026, 11:15 PM UTC
We’re seeing steady improvements across the environment and are actively monitoring performance metrics following the fix. We’ll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 06, 2026, 12:31 AM UTC
As informed earlier, we’re seeing steady improvements across the environment and are still monitoring performance metrics following the fix. We’ll provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring Jun 06, 2026, 01:38 AM UTC
We have identified some new errors in the past 15 minutes, and we’re investigating the cause of the issue. We’ll provide an update in 60 minutes or sooner if additional information becomes available.