История сбоев Sezzle

1. 19 октября 2026 г. в 00:13 UTCinvestigating

   Мы испытываем повышенные показатели ошибок на наших шлюзах и основных API.

2. 19 октября 2026 г. в 00:19 UTCinvestigating

   Мы продолжаем расследование этого вопроса.

3. 19 октября 2026 г. в 00:19 UTCidentified

   Этот вопрос был определен, и в настоящее время осуществляется исправление.

4. 19 октября 2026 г. в 00:19 UTCmonitoring

   Реализовано исправление, и мы отслеживаем результаты.

5. 19 октября 2026 г. в 00:45 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 5 июля 2026 г. в 17:52 UTCinvestigating

   We are currently investigating this issue.

2. 5 июля 2026 г. в 18:03 UTCidentified

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

3. 5 июля 2026 г. в 18:31 UTCmonitoring

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

4. 5 июля 2026 г. в 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. 5 июля 2026 г. в 19:32 UTCresolved

   This incident has been resolved.

1. 3 мая 2026 г. в 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. 18 апреля 2026 г. в 03: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. 18 апреля 2026 г. в 05:44 UTCresolved

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

1. 9 февраля 2026 г. в 19:12 UTCinvestigating

   We are currently investigating this issue.

2. 9 февраля 2026 г. в 19:30 UTCidentified

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

3. 9 февраля 2026 г. в 19:36 UTCmonitoring

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

4. 9 февраля 2026 г. в 19:36 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 9 февраля 2026 г. в 19:52 UTCresolved

   This incident has been resolved.

1. 29 января 2026 г. в 23:14 UTCinvestigating

   We are currently investigating this issue.

2. 29 января 2026 г. в 23:15 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 января 2026 г. в 23:15 UTCidentified

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

4. 29 января 2026 г. в 23:15 UTCidentified

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

5. 29 января 2026 г. в 23:17 UTCmonitoring

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

6. 29 января 2026 г. в 23:21 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 29 января 2026 г. в 23:32 UTCresolved

   This incident has been resolved.

1. 2 января 2026 г. в 17:27 UTCinvestigating

   We have identified the issue and a rollback is underway

2. 2 января 2026 г. в 17:28 UTCidentified

   The issue has been identified and a solution is being merged

3. 2 января 2026 г. в 17:28 UTCinvestigating

   We are currently investigating this issue.

4. 2 января 2026 г. в 17:31 UTCmonitoring

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

5. 2 января 2026 г. в 17:32 UTCresolved

   This incident has been resolved.

1. 23 июля 2025 г. в 16:55 UTCinvestigating

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

2. 23 июля 2025 г. в 16:59 UTCidentified

   A faulty query was recently merged and has been reverted.

3. 23 июля 2025 г. в 17:05 UTCmonitoring

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

4. 23 июля 2025 г. в 17:11 UTCresolved

   All services are fully operational again

1. 18 февраля 2025 г. в 08:22 UTCinvestigating

   We are currently investigating this issue.

2. 18 февраля 2025 г. в 08:34 UTCinvestigating

   Mitigation efforts put in place and partial recovery

3. 18 февраля 2025 г. в 09:55 UTCidentified

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

4. 18 февраля 2025 г. в 10:35 UTCmonitoring

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

5. 18 февраля 2025 г. в 12:11 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 18 февраля 2025 г. в 12:16 UTCresolved

   This incident has been resolved.

1. 28 октября 2024 г. в 17:35 UTCinvestigating

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

2. 28 октября 2024 г. в 17:45 UTCmonitoring

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

3. 28 октября 2024 г. в 18:40 UTCresolved

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

1. 17 октября 2024 г. в 14:52 UTCinvestigating

   We are currently investigating this issue.

2. 17 октября 2024 г. в 14:58 UTCidentified

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

3. 17 октября 2024 г. в 14:59 UTCmonitoring

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

4. 17 октября 2024 г. в 15:47 UTCresolved

   This incident has been resolved.

1. 12 сентября 2024 г. в 21:53 UTCinvestigating

   We are currently investigating this issue.

2. 12 сентября 2024 г. в 22:04 UTCmonitoring

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

3. 12 сентября 2024 г. в 22:15 UTCresolved

   This incident has been resolved.

1. 29 августа 2024 г. в 09:37 UTCinvestigating

   We are currently investigating an issue.

2. 29 августа 2024 г. в 09: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. 29 августа 2024 г. в 10:30 UTCinvestigating

   The issue has been resolved.

4. 29 августа 2024 г. в 10:31 UTCresolved

   This incident has been resolved.

1. 28 августа 2024 г. в 22:00 UTCinvestigating

   We are currently investigating this issue.

2. 28 августа 2024 г. в 22:06 UTCidentified

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

3. 28 августа 2024 г. в 22:06 UTCmonitoring

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

4. 28 августа 2024 г. в 22:39 UTCresolved

   This incident has been resolved.

1. 31 июля 2024 г. в 21:46 UTCinvestigating

   We are currently investigating this issue.

2. 31 июля 2024 г. в 21:46 UTCidentified

   We have identified the issue and applying the fix now.

3. 31 июля 2024 г. в 21:50 UTCmonitoring

   A fix has been applied and we are monitoring the results

4. 31 июля 2024 г. в 22:34 UTCresolved

   This incident has been resolved.

1. 30 июля 2024 г. в 16:19 UTCinvestigating

   We are currently investigating this issue.

2. 30 июля 2024 г. в 16:22 UTCidentified

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

3. 30 июля 2024 г. в 16:23 UTCmonitoring

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

4. 30 июля 2024 г. в 16:54 UTCresolved

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

1. 19 июля 2024 г. в 13:38 UTCidentified

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

2. 19 июля 2024 г. в 18:49 UTCidentified

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

3. 19 июля 2024 г. в 18:50 UTCresolved

   This incident has been resolved.

1. 25 апреля 2024 г. в 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. 25 апреля 2024 г. в 21:42 UTCmonitoring

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

3. 25 апреля 2024 г. в 22:13 UTCresolved

   This incident has been resolved.

1. 15 февраля 2024 г. в 15:38 UTCinvestigating

   We are currently investigating this issue.

2. 15 февраля 2024 г. в 15:55 UTCinvestigating

   We are continuing to investigate this issue.

3. 15 февраля 2024 г. в 16:03 UTCidentified

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

4. 15 февраля 2024 г. в 16:11 UTCmonitoring

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

5. 15 февраля 2024 г. в 17:01 UTCresolved

   This incident has been resolved.

1. 31 января 2024 г. в 17:05 UTCinvestigating

   We are currently investigating this issue.

2. 31 января 2024 г. в 17:05 UTCidentified

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

3. 31 января 2024 г. в 17:07 UTCmonitoring

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

4. 31 января 2024 г. в 17:41 UTCresolved

   This incident has been resolved.