Störungsverlauf von Sps Commerce

1. 18. August 2026 um 16:08 UTCmonitoring

   Zwischen 09:48 und 10:26 CST erlebte AS2 Communications einen Ausfall auf der Empfangsseite, der verhinderte, dass Kunden über AS2 an SPS Commerce senden oder Dokumente senden konnten. Das Problem wurde behoben und die AS2-Konnektivität wurde vollständig wiederhergestellt und derzeit vom Team überwacht. Wenn Kunden Fehler beim Versenden von Dokumenten für eine Zeit des Vorfalls hatten, müssen sie sicherstellen, dass die betroffenen Dokumente erfolgreich erneut gesendet wurden. Wir entschuldigen uns für jede Störung, die dadurch verursacht wurde.

2. 18. August 2026 um 16:15 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 25. Juli 2026 um 12:00 UTCinvestigating

   Wir untersuchen einen offenen Vorfall mit unserer Dokumentenverarbeitungsinfrastruktur, der möglicherweise zu Verzögerungen oder Ausfällen bei der Transaktionsverarbeitung durch das System führt. Es sind keine Daten verloren gegangen und das System sollte in Kürze aufgeholt werden. Wir werden alle Daten abgleichen, nachdem wir uns von dem Vorfall erholt haben, um sicherzustellen, dass alle Transaktionen wie erwartet verarbeitet werden.

2. 25. Juli 2026 um 12:08 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 6. Juli 2026 um 20:25 UTCinvestigating

   We are investigating an open incident with our document processing infrastructure which is potentially causing delays or failures for transactions processing through the system. No data has been lost and the system should be caught up shortly. We will reconcile all data after we have recovered from the incident to ensure all transactions are processed as expected.

2. 6. Juli 2026 um 20:34 UTCinvestigating

   We are continuing to investigate this issue.

3. 6. Juli 2026 um 20:48 UTCidentified

   We are continuing to investigate the issue. The team is isolated the cause and we are working on a fix.

4. 6. Juli 2026 um 21:26 UTCmonitoring

   The issue was identified and a fix was implemented. Recovery of the backlog of data is in process. Any failed documents are being isolated and determined for recovery.

5. 6. Juli 2026 um 22:14 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 6. Juli 2026 um 22:36 UTCmonitoring

   We are continuing to process a small backlog of data, but new documents entering the system are processing normally. Any documents that failed during the outage are being assessed for recovery.

7. 6. Juli 2026 um 23:13 UTCmonitoring

   The backlog of data is fully processed. We continue to isolate and recover failed documents.

8. 7. Juli 2026 um 00:33 UTCresolved

   This incident has been resolved.

1. 6. Juli 2026 um 18:44 UTCinvestigating

   We are investigating an open incident with our document processing infrastructure which is potentially causing delays or failures for transactions for customers using our Web portal. No data has been lost and the system should be caught up shortly. We will reconcile all data after we have recovered from the incident to ensure all transactions are processed as expected.

2. 6. Juli 2026 um 19:11 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 6. Juli 2026 um 19:35 UTCresolved

   This incident has been resolved.

1. 18. Juni 2026 um 08:02 UTCinvestigating

   We are investigating an open incident with our document processing infrastructure which is potentially causing delays or failures for transactions processing through the system. No data has been lost and the system should be caught up shortly. We will reconcile all data after we have recovered from the incident to ensure all transactions are processed as expected.

2. 18. Juni 2026 um 09:00 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 18. Juni 2026 um 09:20 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 18. Juni 2026 um 09:25 UTCresolved

   This incident has been resolved.

1. 10. April 2026 um 20:37 UTCinvestigating

   We are investigating an open incident with our NetSuite Integration which is potentially causing delays for document processing through the system. No data has been lost and all transactions will process as expected after we have recovered from the incident. We will reconcile all data after we have recovered from the incident to ensure all transactions are processed as expected.

2. 10. April 2026 um 20:52 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 10. April 2026 um 22:06 UTCresolved

   This incident has been resolved.

1. 20. Februar 2026 um 13:34 UTCidentified

   We have identified the cause of this incident and our Technology team is working diligently to correct it. Thanks for your continued patience.

2. 20. Februar 2026 um 14:12 UTCidentified

   We are continuing to work on a fix for this issue.

3. 20. Februar 2026 um 14:40 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 20. Februar 2026 um 15:16 UTCresolved

   This incident has been resolved.

1. 24. Januar 2026 um 19:15 UTCidentified

   We have identified an issue with Commerce Platform. Applications in Commerce platform (including Assortment and Fulfillment).

2. 24. Januar 2026 um 19:28 UTCmonitoring

   We have corrected the issue that has caused this incident and we're actively monitoring the situation to ensure performance returns to acceptable levels. Thank you.

3. 24. Januar 2026 um 19:30 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 24. Januar 2026 um 20:17 UTCresolved

   This incident has been resolved.

1. 23. Januar 2026 um 13:53 UTCinvestigating

   We are investigating an open incident with our document processing infrastructure which is potentially causing delays or failures for transactions processing through the system. No data has been lost and the system should be caught up shortly. We will reconcile all data after we have recovered from the incident to ensure all transactions are processed as expected.

2. 23. Januar 2026 um 14:10 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 23. Januar 2026 um 14:42 UTCmonitoring

   A fix has been implemented and we are continue to monitor the results.

4. 23. Januar 2026 um 15:16 UTCmonitoring

   We seeing performance returning to normal and continue to monitor system performance for full recovery.

5. 23. Januar 2026 um 15:21 UTCresolved

   This incident has been resolved.

1. 23. Januar 2026 um 04:41 UTCinvestigating

   We have corrected the issue that caused this incident and we're actively monitoring the situation to ensure performance returns to acceptable levels. Thank you for your patience.

2. 23. Januar 2026 um 04:52 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 23. Januar 2026 um 04:53 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 23. Januar 2026 um 05:18 UTCresolved

   This incident has been resolved.