SPS Commerce experienced a major incident on October 12, 2026 affecting Fulfillment, lasting 2h 4m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 12, 2026, 01:02 PM UTC
We are investigating an issue affecting Fulfillment. Users may be unable to view, open, or send documents within the Fulfillment application. Document processing and data flow are continuing as normal. We will provide an update as soon as we have more information. Thank you for your patience.
- investigating Oct 12, 2026, 01:18 PM UTC
We are continuing to investigate the issue affecting document viewing and sending within Fulfillment. Our teams have a lead and are actively working to confirm the cause. Document processing and data flow are not impacted and continue as normal. We will provide another update within 10 minutes. Thank you for your patience.
- identified Oct 12, 2026, 01:25 PM UTC
We have identified the cause of the issue affecting document viewing and sending within Fulfillment and our teams are actively working on a resolution.
- identified Oct 12, 2026, 01:26 PM UTC
We are continuing to work on a fix for this issue.
- identified Oct 12, 2026, 01:26 PM UTC
We have identified the cause of the issue affecting document viewing and sending within Fulfillment and our teams are actively working on a resolution.
- identified Oct 12, 2026, 01:51 PM UTC
Our teams are continuing to work on a resolution for the issue affecting document viewing and sending within Fulfillment. Document processing and data flow are not impacted and continue as normal.
- monitoring Oct 12, 2026, 02:04 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Oct 12, 2026, 02:36 PM UTC
A fix has been implemented for the issue affecting document viewing and sending within Fulfillment, and we are seeing positive signs of recovery. We are continuing to monitor to confirm full stability and will provide another update within 20 minutes.
- resolved Oct 12, 2026, 03:07 PM UTC
This incident has been resolved.