Sps Commerce 中断历史

1. 2026年10月12日 UTC 13:02investigating

   我们正在调查一个影响实现的问题。 用户可能无法查看,打开或发送Fullation应用程序内的文档. 文件处理和数据流动继续正常进行。 一旦掌握更多信息,我们将提供最新情况。 谢谢你的耐心.

2. 2026年10月12日 UTC 13:18investigating

   我们正在继续调查影响文件查看和发送的问题。 我们的团队具有领导地位,并正在积极努力确认这一事业。 文件处理和数据流动没有受到影响,而且继续正常。 我们将在10分钟内提供另一个最新情况。 谢谢你的耐心.

3. 2026年10月12日 UTC 13:26identified

   我们正在继续努力解决这个问题。

4. 2026年10月12日 UTC 13:26identified

   我们查明了影响文件查看和在 " 执行 " 范围内发送的问题的原因,我们的小组正在积极拟订一项决议.

5. 2026年10月12日 UTC 13:51identified

   我们的小组正在继续就影响文件查看和在 " 完成 " 范围内发送的问题制定一项解决办法。 文件处理和数据流动没有受到影响,而且继续正常.

6. 2026年10月12日 UTC 14:04monitoring

   一项措施已经执行,我们正在监测结果.

7. 2026年10月12日 UTC 14:36monitoring

   已经针对影响文件查看和在 " 完成 " 范围内发送的问题采取了一项措施,我们看到恢复的积极迹象。 我们继续进行监测,以确认完全稳定,并将在20分钟内再次提供最新情况.

8. 2026年10月12日 UTC 15:07resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年8月18日 UTC 16:08monitoring

   09:48至10:26 CST,AS2通信在接收方出现停用,使客户无法通过AS2向SPS Commerce发送或提供文件. 这个问题已经解决,AS2连接完全恢复,目前由团队监测. 如果客户在发送文件一段时间内出现错误,他们需要确保受影响的文件被成功怨恨. 我们对此造成的任何干扰表示歉意.

2. 2026年8月18日 UTC 16:15resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月25日 UTC 12:00investigating

   我们正在调查一个与我们的文件处理基础设施有关的公开事件,这可能造成通过该系统处理交易的延误或失败。 没有丢失任何数据,该系统应很快赶上。 我们将在从事件中收回所有数据后进行核对,以确保所有交易按预期进行.

2. 2026年7月25日 UTC 12:08resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月6日 UTC 20:25investigating

   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日 UTC 20:34investigating

   We are continuing to investigate this issue.

3. 2026年7月6日 UTC 20:48identified

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

4. 2026年7月6日 UTC 21:26monitoring

   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日 UTC 22:14monitoring

   We are continuing to monitor for any further issues.

6. 2026年7月6日 UTC 22:36monitoring

   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日 UTC 23:13monitoring

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

8. 2026年7月7日 UTC 00:33resolved

   This incident has been resolved.

1. 2026年7月6日 UTC 18:44investigating

   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日 UTC 19:11identified

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

3. 2026年7月6日 UTC 19:35resolved

   This incident has been resolved.

1. 2026年6月18日 UTC 08:02investigating

   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日 UTC 09:00identified

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

3. 2026年6月18日 UTC 09:20monitoring

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

4. 2026年6月18日 UTC 09:25resolved

   This incident has been resolved.

1. 2026年4月10日 UTC 20:37investigating

   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日 UTC 20:52monitoring

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

3. 2026年4月10日 UTC 22:06resolved

   This incident has been resolved.

1. 2026年2月20日 UTC 13:34identified

   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日 UTC 14:12identified

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

3. 2026年2月20日 UTC 14:40monitoring

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

4. 2026年2月20日 UTC 15:16resolved

   This incident has been resolved.

1. 2026年1月24日 UTC 19:15identified

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

2. 2026年1月24日 UTC 19:28monitoring

   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日 UTC 19:30monitoring

   We are continuing to monitor for any further issues.

4. 2026年1月24日 UTC 20:17resolved

   This incident has been resolved.

1. 2026年1月23日 UTC 13:53investigating

   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日 UTC 14:10monitoring

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

3. 2026年1月23日 UTC 14:42monitoring

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

4. 2026年1月23日 UTC 15:16monitoring

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

5. 2026年1月23日 UTC 15:21resolved

   This incident has been resolved.

1. 2026年1月23日 UTC 04:41investigating

   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日 UTC 04:52monitoring

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

3. 2026年1月23日 UTC 04:53monitoring

   We are continuing to monitor for any further issues.

4. 2026年1月23日 UTC 05:18resolved

   This incident has been resolved.