Histórico de interrupções do Sps Commerce

1. 18 Eost 2026 da 16:08 UTCmonitoring

   Entre as 09:48 e 10:26 CST, a AS2 Communications teve uma falha na recepção, impedindo os clientes de enviar ou documentos via AS2 para o SPS Commerce. O problema foi resolvido e a conectividade AS2 é totalmente restaurada e atualmente monitorada pela equipe. Se os clientes sofreram erros durante o envio de documentos para um momento do incidente, eles precisam garantir que os documentos afetados foram ressentidos com sucesso. Pedimos desculpa por qualquer perturbação que isto causou.

2. 18 Eost 2026 da 16:15 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 25 Gouere 2026 da 12:00 UTCinvestigating

   Estamos investigando um incidente aberto com nossa infraestrutura de processamento de documentos que está potencialmente causando atrasos ou falhas no processamento de transações através do sistema. Nenhum dado foi perdido e o sistema deve ser retomado em breve. Vamos conciliar todos os dados após termos recuperado do incidente para garantir que todas as transações são processadas como esperado.

2. 25 Gouere 2026 da 12:08 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 6 Gouere 2026 da 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 Gouere 2026 da 20:34 UTCinvestigating

   We are continuing to investigate this issue.

3. 6 Gouere 2026 da 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 Gouere 2026 da 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 Gouere 2026 da 22:14 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 6 Gouere 2026 da 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 Gouere 2026 da 23:13 UTCmonitoring

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

8. 7 Gouere 2026 da 00:33 UTCresolved

   This incident has been resolved.

1. 6 Gouere 2026 da 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 Gouere 2026 da 19:11 UTCidentified

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

3. 6 Gouere 2026 da 19:35 UTCresolved

   This incident has been resolved.

1. 18 Mezheven 2026 da 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 Mezheven 2026 da 09:00 UTCidentified

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

3. 18 Mezheven 2026 da 09:20 UTCmonitoring

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

4. 18 Mezheven 2026 da 09:25 UTCresolved

   This incident has been resolved.

1. 10 Ebrel 2026 da 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 Ebrel 2026 da 20:52 UTCmonitoring

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

3. 10 Ebrel 2026 da 22:06 UTCresolved

   This incident has been resolved.

1. 20 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 14:12 UTCidentified

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

3. 20 Cʼhwevrer 2026 da 14:40 UTCmonitoring

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

4. 20 Cʼhwevrer 2026 da 15:16 UTCresolved

   This incident has been resolved.

1. 24 Genver 2026 da 19:15 UTCidentified

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

2. 24 Genver 2026 da 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 Genver 2026 da 19:30 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 24 Genver 2026 da 20:17 UTCresolved

   This incident has been resolved.

1. 23 Genver 2026 da 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 Genver 2026 da 14:10 UTCmonitoring

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

3. 23 Genver 2026 da 14:42 UTCmonitoring

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

4. 23 Genver 2026 da 15:16 UTCmonitoring

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

5. 23 Genver 2026 da 15:21 UTCresolved

   This incident has been resolved.

1. 23 Genver 2026 da 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 Genver 2026 da 04:52 UTCmonitoring

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

3. 23 Genver 2026 da 04:53 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 23 Genver 2026 da 05:18 UTCresolved

   This incident has been resolved.