Sps Commerce driftsforstyrrelser

1. 18. august 2026 kl. 16.08 UTCmonitoring

   Mellem 09: 48 og 10: 26 CST, AS2 Kommunikation oplevede en afbrydelse på modtagelse side, forhindrer kunderne i at sende eller dokumenter via AS2 til SPS Commerce. Problemet er blevet løst, og AS2 forbindelse er fuldt restaureret og i øjeblikket overvåges af team. Hvis kunderne har oplevet fejl under afsendelsen af dokumenter i en tid af hændelsen, skal de sikre, at de berørte dokumenter er blevet negativt modtaget. Vi undskylder for eventuelle forstyrrelser.

2. 18. august 2026 kl. 16.15 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 25. juli 2026 kl. 12.00 UTCinvestigating

   Vi er ved at undersøge en åben hændelse med vores dokument behandling infrastruktur, som potentielt forårsager forsinkelser eller svigt for transaktioner behandling gennem systemet. Der er ikke gået nogen data tabt, og systemet bør snart inddrages. Vi vil forene alle data efter vi er kommet os efter hændelsen for at sikre, at alle transaktioner behandles som forventet.

2. 25. juli 2026 kl. 12.08 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 6. juli 2026 kl. 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. juli 2026 kl. 20.34 UTCinvestigating

   We are continuing to investigate this issue.

3. 6. juli 2026 kl. 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. juli 2026 kl. 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. juli 2026 kl. 22.14 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 6. juli 2026 kl. 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. juli 2026 kl. 23.13 UTCmonitoring

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

8. 7. juli 2026 kl. 00.33 UTCresolved

   This incident has been resolved.

1. 6. juli 2026 kl. 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. juli 2026 kl. 19.11 UTCidentified

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

3. 6. juli 2026 kl. 19.35 UTCresolved

   This incident has been resolved.

1. 18. juni 2026 kl. 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. juni 2026 kl. 09.00 UTCidentified

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

3. 18. juni 2026 kl. 09.20 UTCmonitoring

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

4. 18. juni 2026 kl. 09.25 UTCresolved

   This incident has been resolved.

1. 10. april 2026 kl. 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. april 2026 kl. 20.52 UTCmonitoring

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

3. 10. april 2026 kl. 22.06 UTCresolved

   This incident has been resolved.

1. 20. februar 2026 kl. 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. februar 2026 kl. 14.12 UTCidentified

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

3. 20. februar 2026 kl. 14.40 UTCmonitoring

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

4. 20. februar 2026 kl. 15.16 UTCresolved

   This incident has been resolved.

1. 24. januar 2026 kl. 19.15 UTCidentified

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

2. 24. januar 2026 kl. 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. januar 2026 kl. 19.30 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 24. januar 2026 kl. 20.17 UTCresolved

   This incident has been resolved.

1. 23. januar 2026 kl. 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. januar 2026 kl. 14.10 UTCmonitoring

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

3. 23. januar 2026 kl. 14.42 UTCmonitoring

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

4. 23. januar 2026 kl. 15.16 UTCmonitoring

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

5. 23. januar 2026 kl. 15.21 UTCresolved

   This incident has been resolved.

1. 23. januar 2026 kl. 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. januar 2026 kl. 04.52 UTCmonitoring

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

3. 23. januar 2026 kl. 04.53 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 23. januar 2026 kl. 05.18 UTCresolved

   This incident has been resolved.