Historial de interrupciones de Sps Commerce

1. 18 de agosto de 2026 a las 16:08 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. 18 de agosto de 2026 a las 16:15 UTCresolved

   Este incidente ha sido resuelto.

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

1. 25 de julio de 2026 a las 12:00 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. 25 de julio de 2026 a las 12:08 UTCresolved

   Este incidente ha sido resuelto.

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

1. 6 de julio de 2026 a las 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 de julio de 2026 a las 20:34 UTCinvestigating

   We are continuing to investigate this issue.

3. 6 de julio de 2026 a las 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 de julio de 2026 a las 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 de julio de 2026 a las 22:14 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 6 de julio de 2026 a las 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 de julio de 2026 a las 23:13 UTCmonitoring

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

8. 7 de julio de 2026 a las 0:33 UTCresolved

   This incident has been resolved.

1. 6 de julio de 2026 a las 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 de julio de 2026 a las 19:11 UTCidentified

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

3. 6 de julio de 2026 a las 19:35 UTCresolved

   This incident has been resolved.

1. 18 de junio de 2026 a las 8: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 de junio de 2026 a las 9:00 UTCidentified

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

3. 18 de junio de 2026 a las 9:20 UTCmonitoring

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

4. 18 de junio de 2026 a las 9:25 UTCresolved

   This incident has been resolved.

1. 10 de abril de 2026 a las 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 de abril de 2026 a las 20:52 UTCmonitoring

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

3. 10 de abril de 2026 a las 22:06 UTCresolved

   This incident has been resolved.

1. 20 de febrero de 2026 a las 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 de febrero de 2026 a las 14:12 UTCidentified

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

3. 20 de febrero de 2026 a las 14:40 UTCmonitoring

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

4. 20 de febrero de 2026 a las 15:16 UTCresolved

   This incident has been resolved.

1. 24 de enero de 2026 a las 19:15 UTCidentified

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

2. 24 de enero de 2026 a las 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 de enero de 2026 a las 19:30 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 24 de enero de 2026 a las 20:17 UTCresolved

   This incident has been resolved.

1. 23 de enero de 2026 a las 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 de enero de 2026 a las 14:10 UTCmonitoring

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

3. 23 de enero de 2026 a las 14:42 UTCmonitoring

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

4. 23 de enero de 2026 a las 15:16 UTCmonitoring

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

5. 23 de enero de 2026 a las 15:21 UTCresolved

   This incident has been resolved.

1. 23 de enero de 2026 a las 4: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 de enero de 2026 a las 4:52 UTCmonitoring

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

3. 23 de enero de 2026 a las 4:53 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 23 de enero de 2026 a las 5:18 UTCresolved

   This incident has been resolved.