Sezzle 中断历史

1. 2026年10月19日 UTC 00:13investigating

   我们的网关和核心API的出错率很高.

2. 2026年10月19日 UTC 00:19investigating

   我们正在继续调查这一问题.

3. 2026年10月19日 UTC 00:19identified

   这一问题已经确定,一个解决办法正在实施之中.

4. 2026年10月19日 UTC 00:19monitoring

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

5. 2026年10月19日 UTC 00:45resolved

   这一事件已经得到解决.

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

1. 2026年7月5日 UTC 17:52investigating

   We are currently investigating this issue.

2. 2026年7月5日 UTC 18:03identified

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

3. 2026年7月5日 UTC 18:31monitoring

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

4. 2026年7月5日 UTC 18:53monitoring

   We have made updates and have seen operational improvements for Sezzle Gateway and Sezzle Dashboards. Minor degraded performance remains on Sezzle Core API

5. 2026年7月5日 UTC 19:32resolved

   This incident has been resolved.

1. 2026年5月3日 UTC 19:50resolved

   A service degradation between 2:05 PM CT and 2:35 PM CT caused elevated error rates with checkouts. The issue has been identified and resolved.

1. 2026年4月18日 UTC 03:34monitoring

   We have learned of an incident between Twilio and AT&T that is impacting SMS deliverability for One Time Passwords: https://status.twilio.com/

2. 2026年4月18日 UTC 05:44resolved

   We are seeing One Time Passwords from AT&T delivery successfully now. This incident has been resolved.

1. 2026年2月9日 UTC 19:12investigating

   We are currently investigating this issue.

2. 2026年2月9日 UTC 19:30identified

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

3. 2026年2月9日 UTC 19:36monitoring

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

4. 2026年2月9日 UTC 19:36monitoring

   We are continuing to monitor for any further issues.

5. 2026年2月9日 UTC 19:52resolved

   This incident has been resolved.

1. 2026年1月29日 UTC 23:14investigating

   We are currently investigating this issue.

2. 2026年1月29日 UTC 23:15investigating

   We are continuing to investigate this issue.

3. 2026年1月29日 UTC 23:15identified

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

4. 2026年1月29日 UTC 23:15identified

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

5. 2026年1月29日 UTC 23:17monitoring

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

6. 2026年1月29日 UTC 23:21monitoring

   We are continuing to monitor for any further issues.

7. 2026年1月29日 UTC 23:32resolved

   This incident has been resolved.

1. 2026年1月2日 UTC 17:27investigating

   We have identified the issue and a rollback is underway

2. 2026年1月2日 UTC 17:28identified

   The issue has been identified and a solution is being merged

3. 2026年1月2日 UTC 17:28investigating

   We are currently investigating this issue.

4. 2026年1月2日 UTC 17:31monitoring

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

5. 2026年1月2日 UTC 17:32resolved

   This incident has been resolved.

1. 2025年7月23日 UTC 16:55investigating

   Our team has identified an issue that is causing some of our services to be unavailable.

2. 2025年7月23日 UTC 16:59identified

   A faulty query was recently merged and has been reverted.

3. 2025年7月23日 UTC 17:05monitoring

   We have merged a fix for the issue, and we're seeing successful requests

4. 2025年7月23日 UTC 17:11resolved

   All services are fully operational again

1. 2025年2月18日 UTC 08:22investigating

   We are currently investigating this issue.

2. 2025年2月18日 UTC 08:34investigating

   Mitigation efforts put in place and partial recovery

3. 2025年2月18日 UTC 09:55identified

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

4. 2025年2月18日 UTC 10:35monitoring

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

5. 2025年2月18日 UTC 12:11monitoring

   We are continuing to monitor for any further issues.

6. 2025年2月18日 UTC 12:16resolved

   This incident has been resolved.

1. 2024年10月28日 UTC 17:35investigating

   We are experiencing a system outage. We are actively identifying the issue and trying to deploy a fix.

2. 2024年10月28日 UTC 17:45monitoring

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

3. 2024年10月28日 UTC 18:40resolved

   We have identified and resolve the issue. Overall impact was between 12:03 and 12:38 CT.

1. 2024年10月17日 UTC 14:52investigating

   We are currently investigating this issue.

2. 2024年10月17日 UTC 14:58identified

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

3. 2024年10月17日 UTC 14:59monitoring

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

4. 2024年10月17日 UTC 15:47resolved

   This incident has been resolved.

1. 2024年9月12日 UTC 21:53investigating

   We are currently investigating this issue.

2. 2024年9月12日 UTC 22:04monitoring

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

3. 2024年9月12日 UTC 22:15resolved

   This incident has been resolved.

1. 2024年8月29日 UTC 09:37investigating

   We are currently investigating an issue.

2. 2024年8月29日 UTC 09:56investigating

   We have identified the issue as due to an incident impacting our hosting provider, AWS. They report signs of recovery, and will provide updates within 30 minutes.

3. 2024年8月29日 UTC 10:30investigating

   The issue has been resolved.

4. 2024年8月29日 UTC 10:31resolved

   This incident has been resolved.

1. 2024年8月28日 UTC 22:00investigating

   We are currently investigating this issue.

2. 2024年8月28日 UTC 22:06identified

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

3. 2024年8月28日 UTC 22:06monitoring

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

4. 2024年8月28日 UTC 22:39resolved

   This incident has been resolved.

1. 2024年7月31日 UTC 21:46investigating

   We are currently investigating this issue.

2. 2024年7月31日 UTC 21:46identified

   We have identified the issue and applying the fix now.

3. 2024年7月31日 UTC 21:50monitoring

   A fix has been applied and we are monitoring the results

4. 2024年7月31日 UTC 22:34resolved

   This incident has been resolved.

1. 2024年7月30日 UTC 16:19investigating

   We are currently investigating this issue.

2. 2024年7月30日 UTC 16:22identified

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

3. 2024年7月30日 UTC 16:23monitoring

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

4. 2024年7月30日 UTC 16:54resolved

   This incident has been resolved. A small subset of Virtual Card authorizations experienced timeouts during the incident period.

1. 2024年7月19日 UTC 13:38identified

   The issue has been identified as related to the global Microsoft cloud outage, we are monitoring the situation.

2. 2024年7月19日 UTC 18:49identified

   The issue has been resolved, and we're continuing to monitor

3. 2024年7月19日 UTC 18:50resolved

   This incident has been resolved.

1. 2024年4月25日 UTC 20:23investigating

   An incident is occurring with a 3rd party provider. We will have minor UI inconsistencies until they have resolved their incident.

2. 2024年4月25日 UTC 21:42monitoring

   Third party provider indicated the issue is resolved. Will be monitoring for the next 30 minutes

3. 2024年4月25日 UTC 22:13resolved

   This incident has been resolved.

1. 2024年2月15日 UTC 15:38investigating

   We are currently investigating this issue.

2. 2024年2月15日 UTC 15:55investigating

   We are continuing to investigate this issue.

3. 2024年2月15日 UTC 16:03identified

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

4. 2024年2月15日 UTC 16:11monitoring

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

5. 2024年2月15日 UTC 17:01resolved

   This incident has been resolved.

1. 2024年1月31日 UTC 17:05investigating

   We are currently investigating this issue.

2. 2024年1月31日 UTC 17:05identified

   Identified the issue and have made updates to fix the underlying issue.

3. 2024年1月31日 UTC 17:07monitoring

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

4. 2024年1月31日 UTC 17:41resolved

   This incident has been resolved.