Sps Commerce 장애 기록

1. 2026년 8월 18일 PM 4:08 UTCmonitoring

   09:48과 10:26 CST 사이에서, AS2 통신은 AS2에서 SPS 상공에 AS2를 통해 고객에게 전송 또는 문서를 방지하는 측면을 수신하는 정전을 경험했습니다. 문제는 해결되고 AS2 연결성은 완전히 복원되고 현재 팀에 의해 모니터링됩니다. 고객이 사건의 시간을 보내는 동안 오류를 경험했다면 영향을받는 문서가 성공적으로 재발견되었는지 확인해야합니다. 우리는 이 기인한 어떤 혼란든지를 위해 apologize.

2. 2026년 8월 18일 PM 4:15 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 25일 PM 12:00 UTCinvestigating

   우리는 시스템을 통해 처리하는 거래에 대한 지연이나 실패를 유발하는 우리의 문서 처리 인프라로 열린 사건을 조사하고 있습니다. 데이터가 잃어 졌고 시스템은 곧 잡혀야합니다. 우리는 모든 거래가 예상대로 처리되도록 사고에서 회복 한 후 모든 데이터를 재구성합니다.

2. 2026년 7월 25일 PM 12:08 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 6일 PM 8: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. 2026년 7월 6일 PM 8:34 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 7월 6일 PM 8:48 UTCidentified

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

4. 2026년 7월 6일 PM 9: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. 2026년 7월 6일 PM 10:14 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 2026년 7월 6일 PM 10: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. 2026년 7월 6일 PM 11:13 UTCmonitoring

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

8. 2026년 7월 7일 AM 12:33 UTCresolved

   This incident has been resolved.

1. 2026년 7월 6일 PM 6: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. 2026년 7월 6일 PM 7:11 UTCidentified

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

3. 2026년 7월 6일 PM 7:35 UTCresolved

   This incident has been resolved.

1. 2026년 6월 18일 AM 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. 2026년 6월 18일 AM 9:00 UTCidentified

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

3. 2026년 6월 18일 AM 9:20 UTCmonitoring

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

4. 2026년 6월 18일 AM 9:25 UTCresolved

   This incident has been resolved.

1. 2026년 4월 10일 PM 8: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. 2026년 4월 10일 PM 8:52 UTCmonitoring

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

3. 2026년 4월 10일 PM 10:06 UTCresolved

   This incident has been resolved.

1. 2026년 2월 20일 PM 1: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. 2026년 2월 20일 PM 2:12 UTCidentified

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

3. 2026년 2월 20일 PM 2:40 UTCmonitoring

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

4. 2026년 2월 20일 PM 3:16 UTCresolved

   This incident has been resolved.

1. 2026년 1월 24일 PM 7:15 UTCidentified

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

2. 2026년 1월 24일 PM 7: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. 2026년 1월 24일 PM 7:30 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2026년 1월 24일 PM 8:17 UTCresolved

   This incident has been resolved.

1. 2026년 1월 23일 PM 1: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. 2026년 1월 23일 PM 2:10 UTCmonitoring

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

3. 2026년 1월 23일 PM 2:42 UTCmonitoring

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

4. 2026년 1월 23일 PM 3:16 UTCmonitoring

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

5. 2026년 1월 23일 PM 3:21 UTCresolved

   This incident has been resolved.

1. 2026년 1월 23일 AM 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. 2026년 1월 23일 AM 4:52 UTCmonitoring

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

3. 2026년 1월 23일 AM 4:53 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2026년 1월 23일 AM 5:18 UTCresolved

   This incident has been resolved.