Cronologia delle interruzioni di Sps Commerce

1. 18 agosto 2026 alle ore 16:08 UTCmonitoring

   Tra le 09:48 e le 10:26 CST, AS2 Communications ha sperimentato un outage sulla ricezione lato, impedendo ai clienti di inviare o documenti via AS2 a SPS Commerce. Il problema è stato risolto e la connettività AS2 è completamente restaurata e attualmente monitorata dal team. Se i clienti hanno sperimentato errori durante l'invio di documenti per un momento dell'incidente, hanno bisogno di garantire che i documenti interessati sono stati risentiti con successo. Ci scusiamo per qualsiasi disturbo causato.

2. 18 agosto 2026 alle ore 16:15 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 25 luglio 2026 alle ore 12:00 UTCinvestigating

   Stiamo indagando su un incidente aperto con la nostra infrastruttura di elaborazione dei documenti che potenzialmente causa ritardi o guasti per il trattamento delle transazioni attraverso il sistema. Nessun dato è stato perso e il sistema dovrebbe essere catturato a breve. Concilieremo tutti i dati dopo aver recuperato dall'incidente per garantire che tutte le transazioni siano trattate come previsto.

2. 25 luglio 2026 alle ore 12:08 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 6 luglio 2026 alle ore 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 luglio 2026 alle ore 20:34 UTCinvestigating

   We are continuing to investigate this issue.

3. 6 luglio 2026 alle ore 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 luglio 2026 alle ore 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 luglio 2026 alle ore 22:14 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 6 luglio 2026 alle ore 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 luglio 2026 alle ore 23:13 UTCmonitoring

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

8. 7 luglio 2026 alle ore 00:33 UTCresolved

   This incident has been resolved.

1. 6 luglio 2026 alle ore 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 luglio 2026 alle ore 19:11 UTCidentified

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

3. 6 luglio 2026 alle ore 19:35 UTCresolved

   This incident has been resolved.

1. 18 giugno 2026 alle ore 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 giugno 2026 alle ore 09:00 UTCidentified

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

3. 18 giugno 2026 alle ore 09:20 UTCmonitoring

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

4. 18 giugno 2026 alle ore 09:25 UTCresolved

   This incident has been resolved.

1. 10 aprile 2026 alle ore 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 aprile 2026 alle ore 20:52 UTCmonitoring

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

3. 10 aprile 2026 alle ore 22:06 UTCresolved

   This incident has been resolved.

1. 20 febbraio 2026 alle ore 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 febbraio 2026 alle ore 14:12 UTCidentified

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

3. 20 febbraio 2026 alle ore 14:40 UTCmonitoring

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

4. 20 febbraio 2026 alle ore 15:16 UTCresolved

   This incident has been resolved.

1. 24 gennaio 2026 alle ore 19:15 UTCidentified

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

2. 24 gennaio 2026 alle ore 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 gennaio 2026 alle ore 19:30 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 24 gennaio 2026 alle ore 20:17 UTCresolved

   This incident has been resolved.

1. 23 gennaio 2026 alle ore 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 gennaio 2026 alle ore 14:10 UTCmonitoring

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

3. 23 gennaio 2026 alle ore 14:42 UTCmonitoring

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

4. 23 gennaio 2026 alle ore 15:16 UTCmonitoring

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

5. 23 gennaio 2026 alle ore 15:21 UTCresolved

   This incident has been resolved.

1. 23 gennaio 2026 alle ore 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 gennaio 2026 alle ore 04:52 UTCmonitoring

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

3. 23 gennaio 2026 alle ore 04:53 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 23 gennaio 2026 alle ore 05:18 UTCresolved

   This incident has been resolved.