Live  /  Salsify  /  Incident

Salsify: JSON Custom Channel Export failures

Salsify · salsify.comMajor incidentResolved2026-09-24 23:02 UTC
Public — what happened

Summary

Salsify reported a major incident in which exports through its JSON Custom Channel were failing, beginning at 21:14 UTC on 2026-09-24. The company said it found and fixed the underlying problem, though it did not describe what that problem was, and the incident was marked resolved at 23:02. Salsify said exports that failed during this period will need to be run again, and it directed customers with questions to its support team.

Timeline

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

Independent path health

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

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

Included with any paid plan.

Open the Salsify report →

More from Salsify

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

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

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