Historial de interrupciones de Sps Commerce

1. August 18, 2026 at 4:08 PM UTCmonitoring

   Entre las 09:48 y las 10:26 CST, AS2 Communications experimentó un outage en el lado receptor, evitando que los clientes envíen o documenten vía AS2 a SPS Commerce. La cuestión se ha resuelto y la conectividad AS2 es totalmente restaurada y actualmente supervisada por el equipo. Si los clientes experimentaron errores durante el envío de documentos durante un tiempo del incidente, necesitan asegurarse de que los documentos afectados se hayan resentido con éxito. Nos disculpamos por cualquier perturbación que esto causó.

2. August 18, 2026 at 4:15 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 25, 2026 at 12:00 PM UTCinvestigating

   Estamos investigando un incidente abierto con nuestra infraestructura de procesamiento de documentos que potencialmente está causando demoras o fracasos para el procesamiento de transacciones a través del sistema. No se han perdido datos y el sistema debe quedar atrapado en breve. Conciliaremos todos los datos después de que nos hayamos recuperado del incidente para asegurar que todas las transacciones sean procesadas como se espera.

2. July 25, 2026 at 12:08 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 6, 2026 at 8:25 PM 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. July 6, 2026 at 8:34 PM UTCinvestigating

   We are continuing to investigate this issue.

3. July 6, 2026 at 8:48 PM UTCidentified

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

4. July 6, 2026 at 9:26 PM 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. July 6, 2026 at 10:14 PM UTCmonitoring

   We are continuing to monitor for any further issues.

6. July 6, 2026 at 10:36 PM 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. July 6, 2026 at 11:13 PM UTCmonitoring

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

8. July 7, 2026 at 12:33 AM UTCresolved

   This incident has been resolved.

1. July 6, 2026 at 6:44 PM 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. July 6, 2026 at 7:11 PM UTCidentified

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

3. July 6, 2026 at 7:35 PM UTCresolved

   This incident has been resolved.

1. June 18, 2026 at 8:02 AM 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. June 18, 2026 at 9:00 AM UTCidentified

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

3. June 18, 2026 at 9:20 AM UTCmonitoring

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

4. June 18, 2026 at 9:25 AM UTCresolved

   This incident has been resolved.

1. April 10, 2026 at 8:37 PM 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. April 10, 2026 at 8:52 PM UTCmonitoring

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

3. April 10, 2026 at 10:06 PM UTCresolved

   This incident has been resolved.

1. February 20, 2026 at 1:34 PM 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. February 20, 2026 at 2:12 PM UTCidentified

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

3. February 20, 2026 at 2:40 PM UTCmonitoring

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

4. February 20, 2026 at 3:16 PM UTCresolved

   This incident has been resolved.

1. January 24, 2026 at 7:15 PM UTCidentified

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

2. January 24, 2026 at 7:28 PM 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. January 24, 2026 at 7:30 PM UTCmonitoring

   We are continuing to monitor for any further issues.

4. January 24, 2026 at 8:17 PM UTCresolved

   This incident has been resolved.

1. January 23, 2026 at 1:53 PM 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. January 23, 2026 at 2:10 PM UTCmonitoring

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

3. January 23, 2026 at 2:42 PM UTCmonitoring

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

4. January 23, 2026 at 3:16 PM UTCmonitoring

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

5. January 23, 2026 at 3:21 PM UTCresolved

   This incident has been resolved.

1. January 23, 2026 at 4:41 AM 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. January 23, 2026 at 4:52 AM UTCmonitoring

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

3. January 23, 2026 at 4:53 AM UTCmonitoring

   We are continuing to monitor for any further issues.

4. January 23, 2026 at 5:18 AM UTCresolved

   This incident has been resolved.