Salsify Outage History

Salsify partial outage View live status →

There were 12 Salsify outages since February 19, 2026 totaling 1164h 27m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.salsify.com

Notice April 29, 2026

Facebook Catalog Direct & Instagram Connection failing to syndicate

Detected by Pingoru
Apr 29, 2026, 02:23 AM UTC
Resolved
Apr 29, 2026, 02:23 AM UTC
Duration
Affected: Syndication
Timeline · 1 update
  1. resolved Apr 29, 2026, 02:23 AM UTC

    Our engineering team has resolved an issue that affected the Facebook Catalog Direct and Instagram connections for approximately 12 hours, starting April 28, 2026, at 14:09 GMT+1. During this window, publications to these specific channels may have failed. We have implemented a fix and confirmed that the systems are now stable and operating as expected. If you had a publication fail during this time, please republish your content to ensure it is successfully delivered. No other syndication channels were impacted by this issue. If you have any questions, please use the "My Cases" option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.

Read the full incident report →

Major April 21, 2026

Home Depot - Customers receiving 403 error response after channel publish

Detected by Pingoru
Apr 21, 2026, 05:55 PM UTC
Resolved
Apr 22, 2026, 02:33 PM UTC
Duration
20h 37m
Affected: The Home Depot
Timeline · 3 updates
  1. investigating Apr 21, 2026, 05:55 PM UTC

    We are investigating reports of the following feedback being returned in the Home Depot direct connection: 'Unable to prepare target system for upload. Unexpected answer received: 403' We have escalated this issue to Home Depot. The feedback has been reported starting yesterday April 20th. If you have any questions, please use the "My Cases" option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.

  2. monitoring Apr 22, 2026, 10:17 AM UTC

    Our Home Depot partners have implemented a fix for the issue that was causing 403 error responses following channel publishes. We have confirmed that publishing functionality has returned to expected levels. We request that any customers who experienced failed publishes during this time manually republish their channels to confirm resolution. Our engineering team will continue to monitor the connection and system stability closely to ensure performance remains consistent. We will provide a final update once we have full confidence in the resolution. If you have any questions, please use the "My Cases" option within the Customer Portal ([https://help.salsify.com/ProductXM/s/](https://help.salsify.com/ProductXM/s/)) to connect with our team.

  3. resolved Apr 22, 2026, 02:33 PM UTC

    Our Home Depot partners have deployed a fix and the issue is now confirmed resolved. If you have not yet republished, please do so to confirm. If you have any questions, please use the "My Cases" option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.

Read the full incident report →

Minor April 16, 2026

Renaming Smart Lists causing filter removal

Detected by Pingoru
Apr 16, 2026, 10:34 PM UTC
Resolved
Apr 17, 2026, 03:53 PM UTC
Duration
17h 19m
Affected: Salsify Application
Timeline · 3 updates
  1. investigating Apr 16, 2026, 10:34 PM UTC

    We are investigating reports of Product and Asset Lists losing their filters when renaming the List. If you have any questions, please use the "My Cases" option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.

  2. monitoring Apr 17, 2026, 12:18 AM UTC

    We have identified the cause of the issue, and have temporarily disabled the new List Experience so as to ensure no further filter removals across organizations. We are monitoring for continued success. If you have any questions, or believe a list was impacted by this incident, please use the "My Cases" option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.

  3. resolved Apr 17, 2026, 03:53 PM UTC

    The incident affecting Smart List Filter Removal has been resolved, and the new List UI has been re-enabled. If you have any questions, or believe your list may have been impacted, please use the "My Cases" option within the Customer Portal (https://help.salsify.com/ProductXM/s/) to connect with our team.

Read the full incident report →

Major April 16, 2026

Digital Asset Feed generating blank export

Detected by Pingoru
Apr 16, 2026, 06:06 PM UTC
Resolved
Apr 16, 2026, 07:50 PM UTC
Duration
1h 43m
Affected: Salsify ApplicationCatalog Sites
Timeline · 3 updates
  1. investigating Apr 16, 2026, 06:06 PM UTC

    We have identified an issue that causes blank zip files when exporting Digital Asset Feeds and Digital Assets from Sites & Classic Catalogs. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  2. monitoring Apr 16, 2026, 06:42 PM UTC

    We have identified and corrected an issue that was generating blank zip files when exporting Digital Asset Feeds and Digital Assets from Sites & Classic Catalogs. If you continue to see issues with generating a Digital Asset export, please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  3. resolved Apr 16, 2026, 07:50 PM UTC

    This issue has been resolved. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

Read the full incident report →

Major April 16, 2026

Walmart 1P Connector Publication Failures

Detected by Pingoru
Apr 16, 2026, 09:22 AM UTC
Resolved
Apr 17, 2026, 09:22 AM UTC
Duration
1d
Affected: Enhanced ContentWalmart
Timeline · 4 updates
  1. investigating Apr 16, 2026, 09:22 AM UTC

    We have identified an issue causing all publications via the Walmart 1P (Vendor) connector to fail due to an error retrieving credentials from Walmart's API. This appears to be related to an outage on Walmart's side. Walmart 3P (Marketplace) services appear to be unaffected at this time. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  2. investigating Apr 16, 2026, 01:55 PM UTC

    We are currently investigating an issue causing publications via the Walmart 1P (Vendor) connector to fail due to an error retrieving credentials from Walmart's API. This issue also impacts Enhanced Content publishes for customers utilizing OAuth authentication with Walmart’s API Gateway.Walmart 3P (Marketplace) services using legacy authentication appear to be unaffected at this time. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  3. monitoring Apr 16, 2026, 11:23 PM UTC

    Walmart has reported progress in resolving the internal errors that have been broadly impacting supplier API submissions. As of 6:40 PM WET (1:40 PM EDT), our engineering team has observed the first successful publications through the Walmart 1P (Vendor) and Enhanced Content (OAuth) connectors. While this indicates that the service is recovering, we are continuing to monitor the success rate to ensure stability across all accounts. Action Required for Failed Submissions: Please note that any publications that failed prior to this recovery window will not automatically reprocess. Please republish the affected products to transmit them to Walmart. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for assistance or questions.

  4. resolved Apr 17, 2026, 09:22 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 14, 2026

Delayed Kroger Publications + Increase in Failed Intelligence Suite Workflow Tasks

Detected by Pingoru
Apr 14, 2026, 08:27 PM UTC
Resolved
Apr 14, 2026, 09:35 PM UTC
Duration
1h 8m
Affected: Salsify Application
Timeline · 3 updates
  1. investigating Apr 14, 2026, 08:27 PM UTC

    We are investigating issues with one of our model providers, manifesting as delayed Kroger Publications. Additionally, users leveraging Intelligence Suite Workflows may be experiencing an increase of Task Failures. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  2. monitoring Apr 14, 2026, 08:58 PM UTC

    The model issue affecting delayed Kroger Publications and Intelligence Suite Workflow Failures has been corrected. We are monitoring for continued success, and final confirmation from our provider. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  3. resolved Apr 14, 2026, 09:35 PM UTC

    This issue has been resolved. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

Read the full incident report →

Critical March 17, 2026

Product Detail Pages failing to load

Detected by Pingoru
Mar 17, 2026, 02:59 PM UTC
Resolved
Mar 17, 2026, 04:00 PM UTC
Duration
1h
Affected: Salsify Application
Timeline · 3 updates
  1. investigating Mar 17, 2026, 02:59 PM UTC

    Product detail pages may be failing to load. Error "unable to load properties" appears. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  2. monitoring Mar 17, 2026, 03:12 PM UTC

    We have addressed an issue which was causing product detail pages to fail with error "unable to load properties." We are continuing to monitor at this time. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  3. resolved Mar 17, 2026, 04:00 PM UTC

    We addressed an issue which was causing product detail pages to fail with error "unable to load properties." Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

Read the full incident report →

Major March 12, 2026

GDSN load publishing impacted

Detected by Pingoru
Mar 12, 2026, 08:51 PM UTC
Resolved
Mar 12, 2026, 10:16 PM UTC
Duration
1h 24m
Affected: GDSN
Timeline · 2 updates
  1. identified Mar 12, 2026, 08:51 PM UTC

    We have identified an issue when load publishing GDSN data to the Salsify data pool. Previously existing data pool validation errors are not clearing, after the previously identified/reported data discrepancies have been addressed. Our engineering team has identified the problem and is currently in the process of applying a fix.

  2. resolved Mar 12, 2026, 10:16 PM UTC

    The issue impacting GDSN load publishes (which prevented data pool validations from clearing) has been resolved. If you have GTINs that were impacted by this issue, please load publish those GTINs to our data pool again. If you encounter any further issues of this nature, please reach out to Salsify Support.

Read the full incident report →

Critical March 5, 2026

Facebook/Instagram failed publications

Detected by Pingoru
Mar 05, 2026, 04:15 PM UTC
Resolved
Apr 10, 2026, 03:29 PM UTC
Duration
35d 23h
Affected: Syndication
Timeline · 3 updates
  1. investigating Mar 05, 2026, 04:15 PM UTC

    Our engineers identified an issue that is causing any publications through the Facebook/Instagram direct connections to fail. The team is currently working to resolve this issue. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  2. identified Mar 30, 2026, 02:25 PM UTC

    Our engineers are continuing to work through an issue which is causing publications to fail for the Facebook/Instagram channel.We continue working with Meta to restore service functionality. As new workaround has been implemented to allow affected customers to create a CSV file through the channel and do a manual upload of all published data to the Facebook catalogs through https://business.facebook.com/commerce. The below steps will need to be followed to enable the manual CSV creation in the Facebook/Instagram channel: 1. Go to the desired Salsify Facebook channel 2. Select Settings > Destination 3. Switch the 'Export File Only' field from 'False' to 'True' 4. Select 'Save' 5. Publish products per usual 6. Select the down button for the recent publish and select 'Download Product Data' Once you have the CSV file, please go to https://business.facebook.com/commerce to find your related Facebook catalog.From there, you can follow the below steps to upload the CSV file: 1. Select the desired catalog 2. On the left hand side under 'Commerce Manager', select 'Catalog' > 'Products' 3. Select the green '+Add' button on the upper right hand corner of the window > 'Data File' 4. Select 'Upload from your computer' and upload the related CSV file 5. Select 'Next' 6. Select the currency under 'Default Currency' field and then select 'Upload' Please reach out to Customer Support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  3. resolved Apr 10, 2026, 03:29 PM UTC

    Our engineers have confirmed the Facebook channel is now resolved. Before republishing in the Facebook channel, please follow the below steps to disconnect Salsify and re-authorize Salsify within your Facebook app along with changing the channel settings if the previous workaround was used: 1. remove Salsify from the meta business dashboard - log in to https://business.facebook.com > settings > on the left panel, select integrations -> associated apps 2. go to https://con-instagram-commerce.salsify.com/auth/setup_app and go through the authorization process - please select the Set Up button for the specific channel after the authorization steps 3. go to the Salsify Facebook channel > Settings > ensure Export File Only is set to False Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

Read the full incident report →

Minor March 4, 2026

Delays affecting imports, bulk edits, subscriptions

Detected by Pingoru
Mar 04, 2026, 04:30 PM UTC
Resolved
Mar 04, 2026, 07:31 PM UTC
Duration
3h
Affected: Salsify Application
Timeline · 3 updates
  1. investigating Mar 04, 2026, 04:30 PM UTC

    Our engineers are investigating long-queuing imports, and delayed bulk edit actions and subscription triggers. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  2. monitoring Mar 04, 2026, 06:19 PM UTC

    Our engineers have identified and addressed an issue which was causing long-queuing imports, as well as delayed bulk edit actions and subscription triggers. Operation times should be returning to normal. We are continuing to monitor closely. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  3. resolved Mar 04, 2026, 07:31 PM UTC

    Our engineers identified and addressed an issue which caused long-queuing imports, as well as delayed bulk edit actions and subscription triggers. Operation times have returned to normal. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

Read the full incident report →

Notice March 2, 2026

Salsify FTP connection failures

Detected by Pingoru
Mar 02, 2026, 10:28 PM UTC
Resolved
Mar 06, 2026, 04:58 PM UTC
Duration
3d 18h
Affected: Salsify FTP
Timeline · 2 updates
  1. monitoring Mar 02, 2026, 10:28 PM UTC

    On March 2, 2026 at approximately 9:00PM UTC, multiple connection failures occurred when processing imports from and exports to the Salsify FTP. The connection errors appear to be resolved as of 9:30PM UTC. We are continuing to monitor the imports and exports connecting to the Salsify FTP to ensure this does not occur again. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  2. resolved Mar 06, 2026, 04:58 PM UTC

    Through our monitoring, we have seen stable connections to the Salsify FTP since March 2, 2026 at 9:30PM UTC. Publication to the Salsify FTP and imports of files from the Salsify FTP are completing successfully without any issues. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

Read the full incident report →

Major February 19, 2026

Walmart US Enhanced Content issues with syndication

Detected by Pingoru
Feb 19, 2026, 09:37 PM UTC
Resolved
Feb 25, 2026, 06:05 PM UTC
Duration
5d 20h
Affected: Enhanced ContentWalmart
Timeline · 2 updates
  1. identified Feb 19, 2026, 09:37 PM UTC

    We identified an issue with syndicating Enhanced Content to Walmart US. We have reached out to our partners at Walmart to further identify the root cause and an estimated time for resolution. Please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions regarding this subject.

  2. resolved Feb 25, 2026, 06:05 PM UTC

    We are now seeing successful syndications of Enhanced Content to Walmart US. If you experienced Enhanced Content not going live on Walmart US during this Incident, we encourage you to republish the layout. If you continue to see Enhanced Content not go live on Walmart US, please reach out to customer support at https://help.salsify.com/help/contact-feedback for any questions or further investigation.

Read the full incident report →

Looking to track Salsify downtime and outages?

Pingoru polls Salsify's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Salsify reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Salsify alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Salsify for free

5 free monitors · No credit card required