История сбоев Sps Commerce

1. 18 августа 2026 г. в 16:08 UTCmonitoring

   В период с 09:48 по 10:26 CST AS2 Communications столкнулась с перебоями в приеме, что не позволило клиентам отправлять или передавать документы через AS2 в SPS Commerce. Проблема была решена, и соединение AS2 полностью восстановлено и в настоящее время контролируется командой. Если клиенты столкнулись с ошибками при отправке документов на время инцидента, они должны убедиться, что затронутые документы были успешно возмущены. Мы приносим извинения за любые нарушения, вызванные этим.

2. 18 августа 2026 г. в 16:15 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 25 июля 2026 г. в 12:00 UTCinvestigating

   Мы расследуем открытый инцидент с нашей инфраструктурой обработки документов, который может привести к задержкам или сбоям в обработке транзакций через систему. Никаких данных не было потеряно, и система должна быть захвачена в ближайшее время. Мы будем согласовывать все данные после того, как мы оправились от инцидента, чтобы гарантировать, что все транзакции обрабатываются, как ожидается.

2. 25 июля 2026 г. в 12:08 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 6 июля 2026 г. в 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 июля 2026 г. в 20:34 UTCinvestigating

   We are continuing to investigate this issue.

3. 6 июля 2026 г. в 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 июля 2026 г. в 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 июля 2026 г. в 22:14 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 6 июля 2026 г. в 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 июля 2026 г. в 23:13 UTCmonitoring

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

8. 7 июля 2026 г. в 00:33 UTCresolved

   This incident has been resolved.

1. 6 июля 2026 г. в 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 июля 2026 г. в 19:11 UTCidentified

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

3. 6 июля 2026 г. в 19:35 UTCresolved

   This incident has been resolved.

1. 18 июня 2026 г. в 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 июня 2026 г. в 09:00 UTCidentified

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

3. 18 июня 2026 г. в 09:20 UTCmonitoring

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

4. 18 июня 2026 г. в 09:25 UTCresolved

   This incident has been resolved.

1. 10 апреля 2026 г. в 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 апреля 2026 г. в 20:52 UTCmonitoring

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

3. 10 апреля 2026 г. в 22:06 UTCresolved

   This incident has been resolved.

1. 20 февраля 2026 г. в 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 февраля 2026 г. в 14:12 UTCidentified

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

3. 20 февраля 2026 г. в 14:40 UTCmonitoring

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

4. 20 февраля 2026 г. в 15:16 UTCresolved

   This incident has been resolved.

1. 24 января 2026 г. в 19:15 UTCidentified

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

2. 24 января 2026 г. в 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 января 2026 г. в 19:30 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 24 января 2026 г. в 20:17 UTCresolved

   This incident has been resolved.

1. 23 января 2026 г. в 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 января 2026 г. в 14:10 UTCmonitoring

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

3. 23 января 2026 г. в 14:42 UTCmonitoring

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

4. 23 января 2026 г. в 15:16 UTCmonitoring

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

5. 23 января 2026 г. в 15:21 UTCresolved

   This incident has been resolved.

1. 23 января 2026 г. в 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 января 2026 г. в 04:52 UTCmonitoring

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

3. 23 января 2026 г. в 04:53 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 23 января 2026 г. в 05:18 UTCresolved

   This incident has been resolved.