Sezzle の障害履歴

1. 2026年10月19日 0:13 UTCinvestigating

   ゲートウェイとコア API のエラー率が向上しました.

2. 2026年10月19日 0:19 UTCinvestigating

   今後もこの問題について調査を続けてまいります.

3. 2026年10月19日 0:19 UTCidentified

   問題が特定され、修正が実装されています.

4. 2026年10月19日 0:19 UTCmonitoring

   修正を実装し、結果を監視しています.

5. 2026年10月19日 0:45 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月5日 17:52 UTCinvestigating

   We are currently investigating this issue.

2. 2026年7月5日 18:03 UTCidentified

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

3. 2026年7月5日 18:31 UTCmonitoring

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

4. 2026年7月5日 18:53 UTCmonitoring

   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日 19:32 UTCresolved

   This incident has been resolved.

1. 2026年5月3日 19:50 UTCresolved

   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日 3:34 UTCmonitoring

   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日 5:44 UTCresolved

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

1. 2026年2月9日 19:12 UTCinvestigating

   We are currently investigating this issue.

2. 2026年2月9日 19:30 UTCidentified

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

3. 2026年2月9日 19:36 UTCmonitoring

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

4. 2026年2月9日 19:36 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2026年2月9日 19:52 UTCresolved

   This incident has been resolved.

1. 2026年1月29日 23:14 UTCinvestigating

   We are currently investigating this issue.

2. 2026年1月29日 23:15 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026年1月29日 23:15 UTCidentified

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

4. 2026年1月29日 23:15 UTCidentified

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

5. 2026年1月29日 23:17 UTCmonitoring

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

6. 2026年1月29日 23:21 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 2026年1月29日 23:32 UTCresolved

   This incident has been resolved.

1. 2026年1月2日 17:27 UTCinvestigating

   We have identified the issue and a rollback is underway

2. 2026年1月2日 17:28 UTCidentified

   The issue has been identified and a solution is being merged

3. 2026年1月2日 17:28 UTCinvestigating

   We are currently investigating this issue.

4. 2026年1月2日 17:31 UTCmonitoring

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

5. 2026年1月2日 17:32 UTCresolved

   This incident has been resolved.

1. 2025年7月23日 16:55 UTCinvestigating

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

2. 2025年7月23日 16:59 UTCidentified

   A faulty query was recently merged and has been reverted.

3. 2025年7月23日 17:05 UTCmonitoring

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

4. 2025年7月23日 17:11 UTCresolved

   All services are fully operational again

1. 2025年2月18日 8:22 UTCinvestigating

   We are currently investigating this issue.

2. 2025年2月18日 8:34 UTCinvestigating

   Mitigation efforts put in place and partial recovery

3. 2025年2月18日 9:55 UTCidentified

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

4. 2025年2月18日 10:35 UTCmonitoring

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

5. 2025年2月18日 12:11 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 2025年2月18日 12:16 UTCresolved

   This incident has been resolved.

1. 2024年10月28日 17:35 UTCinvestigating

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

2. 2024年10月28日 17:45 UTCmonitoring

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

3. 2024年10月28日 18:40 UTCresolved

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

1. 2024年10月17日 14:52 UTCinvestigating

   We are currently investigating this issue.

2. 2024年10月17日 14:58 UTCidentified

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

3. 2024年10月17日 14:59 UTCmonitoring

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

4. 2024年10月17日 15:47 UTCresolved

   This incident has been resolved.

1. 2024年9月12日 21:53 UTCinvestigating

   We are currently investigating this issue.

2. 2024年9月12日 22:04 UTCmonitoring

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

3. 2024年9月12日 22:15 UTCresolved

   This incident has been resolved.

1. 2024年8月29日 9:37 UTCinvestigating

   We are currently investigating an issue.

2. 2024年8月29日 9:56 UTCinvestigating

   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日 10:30 UTCinvestigating

   The issue has been resolved.

4. 2024年8月29日 10:31 UTCresolved

   This incident has been resolved.

1. 2024年8月28日 22:00 UTCinvestigating

   We are currently investigating this issue.

2. 2024年8月28日 22:06 UTCidentified

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

3. 2024年8月28日 22:06 UTCmonitoring

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

4. 2024年8月28日 22:39 UTCresolved

   This incident has been resolved.

1. 2024年7月31日 21:46 UTCinvestigating

   We are currently investigating this issue.

2. 2024年7月31日 21:46 UTCidentified

   We have identified the issue and applying the fix now.

3. 2024年7月31日 21:50 UTCmonitoring

   A fix has been applied and we are monitoring the results

4. 2024年7月31日 22:34 UTCresolved

   This incident has been resolved.

1. 2024年7月30日 16:19 UTCinvestigating

   We are currently investigating this issue.

2. 2024年7月30日 16:22 UTCidentified

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

3. 2024年7月30日 16:23 UTCmonitoring

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

4. 2024年7月30日 16:54 UTCresolved

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

1. 2024年7月19日 13:38 UTCidentified

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

2. 2024年7月19日 18:49 UTCidentified

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

3. 2024年7月19日 18:50 UTCresolved

   This incident has been resolved.

1. 2024年4月25日 20:23 UTCinvestigating

   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日 21:42 UTCmonitoring

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

3. 2024年4月25日 22:13 UTCresolved

   This incident has been resolved.

1. 2024年2月15日 15:38 UTCinvestigating

   We are currently investigating this issue.

2. 2024年2月15日 15:55 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024年2月15日 16:03 UTCidentified

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

4. 2024年2月15日 16:11 UTCmonitoring

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

5. 2024年2月15日 17:01 UTCresolved

   This incident has been resolved.

1. 2024年1月31日 17:05 UTCinvestigating

   We are currently investigating this issue.

2. 2024年1月31日 17:05 UTCidentified

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

3. 2024年1月31日 17:07 UTCmonitoring

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

4. 2024年1月31日 17:41 UTCresolved

   This incident has been resolved.