Historique des pannes de Sezzle

1. 19 octobre 2026 à 00:13 UTCinvestigating

   Nous connaissons des taux d'erreur élevés sur notre passerelle et nos API de base.

2. 19 octobre 2026 à 00:19 UTCinvestigating

   Nous continuons d'enquêter sur cette question.

3. 19 octobre 2026 à 00:19 UTCidentified

   Le problème a été identifié et une solution est en cours de mise en oeuvre.

4. 19 octobre 2026 à 00:19 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

5. 19 octobre 2026 à 00:45 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 5 juillet 2026 à 17:52 UTCinvestigating

   We are currently investigating this issue.

2. 5 juillet 2026 à 18:03 UTCidentified

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

3. 5 juillet 2026 à 18:31 UTCmonitoring

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

4. 5 juillet 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 juillet 2026 à 19:32 UTCresolved

   This incident has been resolved.

1. 3 mai 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 avril 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 avril 2026 à 05:44 UTCresolved

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

1. 9 février 2026 à 19:12 UTCinvestigating

   We are currently investigating this issue.

2. 9 février 2026 à 19:30 UTCidentified

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

3. 9 février 2026 à 19:36 UTCmonitoring

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

4. 9 février 2026 à 19:36 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 9 février 2026 à 19:52 UTCresolved

   This incident has been resolved.

1. 29 janvier 2026 à 23:14 UTCinvestigating

   We are currently investigating this issue.

2. 29 janvier 2026 à 23:15 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 janvier 2026 à 23:15 UTCidentified

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

4. 29 janvier 2026 à 23:15 UTCidentified

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

5. 29 janvier 2026 à 23:17 UTCmonitoring

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

6. 29 janvier 2026 à 23:21 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 29 janvier 2026 à 23:32 UTCresolved

   This incident has been resolved.

1. 2 janvier 2026 à 17:27 UTCinvestigating

   We have identified the issue and a rollback is underway

2. 2 janvier 2026 à 17:28 UTCidentified

   The issue has been identified and a solution is being merged

3. 2 janvier 2026 à 17:28 UTCinvestigating

   We are currently investigating this issue.

4. 2 janvier 2026 à 17:31 UTCmonitoring

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

5. 2 janvier 2026 à 17:32 UTCresolved

   This incident has been resolved.

1. 23 juillet 2025 à 16:55 UTCinvestigating

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

2. 23 juillet 2025 à 16:59 UTCidentified

   A faulty query was recently merged and has been reverted.

3. 23 juillet 2025 à 17:05 UTCmonitoring

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

4. 23 juillet 2025 à 17:11 UTCresolved

   All services are fully operational again

1. 18 février 2025 à 08:22 UTCinvestigating

   We are currently investigating this issue.

2. 18 février 2025 à 08:34 UTCinvestigating

   Mitigation efforts put in place and partial recovery

3. 18 février 2025 à 09:55 UTCidentified

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

4. 18 février 2025 à 10:35 UTCmonitoring

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

5. 18 février 2025 à 12:11 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 18 février 2025 à 12:16 UTCresolved

   This incident has been resolved.

1. 28 octobre 2024 à 17:35 UTCinvestigating

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

2. 28 octobre 2024 à 17:45 UTCmonitoring

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

3. 28 octobre 2024 à 18:40 UTCresolved

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

1. 17 octobre 2024 à 14:52 UTCinvestigating

   We are currently investigating this issue.

2. 17 octobre 2024 à 14:58 UTCidentified

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

3. 17 octobre 2024 à 14:59 UTCmonitoring

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

4. 17 octobre 2024 à 15:47 UTCresolved

   This incident has been resolved.

1. 12 septembre 2024 à 21:53 UTCinvestigating

   We are currently investigating this issue.

2. 12 septembre 2024 à 22:04 UTCmonitoring

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

3. 12 septembre 2024 à 22:15 UTCresolved

   This incident has been resolved.

1. 29 août 2024 à 09:37 UTCinvestigating

   We are currently investigating an issue.

2. 29 août 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 août 2024 à 10:30 UTCinvestigating

   The issue has been resolved.

4. 29 août 2024 à 10:31 UTCresolved

   This incident has been resolved.

1. 28 août 2024 à 22:00 UTCinvestigating

   We are currently investigating this issue.

2. 28 août 2024 à 22:06 UTCidentified

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

3. 28 août 2024 à 22:06 UTCmonitoring

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

4. 28 août 2024 à 22:39 UTCresolved

   This incident has been resolved.

1. 31 juillet 2024 à 21:46 UTCinvestigating

   We are currently investigating this issue.

2. 31 juillet 2024 à 21:46 UTCidentified

   We have identified the issue and applying the fix now.

3. 31 juillet 2024 à 21:50 UTCmonitoring

   A fix has been applied and we are monitoring the results

4. 31 juillet 2024 à 22:34 UTCresolved

   This incident has been resolved.

1. 30 juillet 2024 à 16:19 UTCinvestigating

   We are currently investigating this issue.

2. 30 juillet 2024 à 16:22 UTCidentified

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

3. 30 juillet 2024 à 16:23 UTCmonitoring

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

4. 30 juillet 2024 à 16:54 UTCresolved

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

1. 19 juillet 2024 à 13:38 UTCidentified

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

2. 19 juillet 2024 à 18:49 UTCidentified

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

3. 19 juillet 2024 à 18:50 UTCresolved

   This incident has been resolved.

1. 25 avril 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 avril 2024 à 21:42 UTCmonitoring

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

3. 25 avril 2024 à 22:13 UTCresolved

   This incident has been resolved.

1. 15 février 2024 à 15:38 UTCinvestigating

   We are currently investigating this issue.

2. 15 février 2024 à 15:55 UTCinvestigating

   We are continuing to investigate this issue.

3. 15 février 2024 à 16:03 UTCidentified

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

4. 15 février 2024 à 16:11 UTCmonitoring

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

5. 15 février 2024 à 17:01 UTCresolved

   This incident has been resolved.

1. 31 janvier 2024 à 17:05 UTCinvestigating

   We are currently investigating this issue.

2. 31 janvier 2024 à 17:05 UTCidentified

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

3. 31 janvier 2024 à 17:07 UTCmonitoring

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

4. 31 janvier 2024 à 17:41 UTCresolved

   This incident has been resolved.