Cronologia delle interruzioni di Sezzle

1. 19 ottobre 2026 alle ore 00:13 UTCinvestigating

   Stiamo vivendo tassi di errore elevati sul nostro Gateway e API core.

2. 19 ottobre 2026 alle ore 00:19 UTCinvestigating

   Stiamo continuando a indagare su questo problema.

3. 19 ottobre 2026 alle ore 00:19 UTCidentified

   Il problema è stato identificato e si sta attuando una correzione.

4. 19 ottobre 2026 alle ore 00:19 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati.

5. 19 ottobre 2026 alle ore 00:45 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 5 luglio 2026 alle ore 17:52 UTCinvestigating

   We are currently investigating this issue.

2. 5 luglio 2026 alle ore 18:03 UTCidentified

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

3. 5 luglio 2026 alle ore 18:31 UTCmonitoring

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

4. 5 luglio 2026 alle ore 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 luglio 2026 alle ore 19:32 UTCresolved

   This incident has been resolved.

1. 3 maggio 2026 alle ore 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 aprile 2026 alle ore 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 aprile 2026 alle ore 05:44 UTCresolved

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

1. 9 febbraio 2026 alle ore 19:12 UTCinvestigating

   We are currently investigating this issue.

2. 9 febbraio 2026 alle ore 19:30 UTCidentified

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

3. 9 febbraio 2026 alle ore 19:36 UTCmonitoring

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

4. 9 febbraio 2026 alle ore 19:36 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 9 febbraio 2026 alle ore 19:52 UTCresolved

   This incident has been resolved.

1. 29 gennaio 2026 alle ore 23:14 UTCinvestigating

   We are currently investigating this issue.

2. 29 gennaio 2026 alle ore 23:15 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 gennaio 2026 alle ore 23:15 UTCidentified

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

4. 29 gennaio 2026 alle ore 23:15 UTCidentified

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

5. 29 gennaio 2026 alle ore 23:17 UTCmonitoring

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

6. 29 gennaio 2026 alle ore 23:21 UTCmonitoring

   We are continuing to monitor for any further issues.

7. 29 gennaio 2026 alle ore 23:32 UTCresolved

   This incident has been resolved.

1. 2 gennaio 2026 alle ore 17:27 UTCinvestigating

   We have identified the issue and a rollback is underway

2. 2 gennaio 2026 alle ore 17:28 UTCidentified

   The issue has been identified and a solution is being merged

3. 2 gennaio 2026 alle ore 17:28 UTCinvestigating

   We are currently investigating this issue.

4. 2 gennaio 2026 alle ore 17:31 UTCmonitoring

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

5. 2 gennaio 2026 alle ore 17:32 UTCresolved

   This incident has been resolved.

1. 23 luglio 2025 alle ore 16:55 UTCinvestigating

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

2. 23 luglio 2025 alle ore 16:59 UTCidentified

   A faulty query was recently merged and has been reverted.

3. 23 luglio 2025 alle ore 17:05 UTCmonitoring

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

4. 23 luglio 2025 alle ore 17:11 UTCresolved

   All services are fully operational again

1. 18 febbraio 2025 alle ore 08:22 UTCinvestigating

   We are currently investigating this issue.

2. 18 febbraio 2025 alle ore 08:34 UTCinvestigating

   Mitigation efforts put in place and partial recovery

3. 18 febbraio 2025 alle ore 09:55 UTCidentified

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

4. 18 febbraio 2025 alle ore 10:35 UTCmonitoring

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

5. 18 febbraio 2025 alle ore 12:11 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 18 febbraio 2025 alle ore 12:16 UTCresolved

   This incident has been resolved.

1. 28 ottobre 2024 alle ore 17:35 UTCinvestigating

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

2. 28 ottobre 2024 alle ore 17:45 UTCmonitoring

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

3. 28 ottobre 2024 alle ore 18:40 UTCresolved

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

1. 17 ottobre 2024 alle ore 14:52 UTCinvestigating

   We are currently investigating this issue.

2. 17 ottobre 2024 alle ore 14:58 UTCidentified

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

3. 17 ottobre 2024 alle ore 14:59 UTCmonitoring

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

4. 17 ottobre 2024 alle ore 15:47 UTCresolved

   This incident has been resolved.

1. 12 settembre 2024 alle ore 21:53 UTCinvestigating

   We are currently investigating this issue.

2. 12 settembre 2024 alle ore 22:04 UTCmonitoring

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

3. 12 settembre 2024 alle ore 22:15 UTCresolved

   This incident has been resolved.

1. 29 agosto 2024 alle ore 09:37 UTCinvestigating

   We are currently investigating an issue.

2. 29 agosto 2024 alle ore 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 agosto 2024 alle ore 10:30 UTCinvestigating

   The issue has been resolved.

4. 29 agosto 2024 alle ore 10:31 UTCresolved

   This incident has been resolved.

1. 28 agosto 2024 alle ore 22:00 UTCinvestigating

   We are currently investigating this issue.

2. 28 agosto 2024 alle ore 22:06 UTCidentified

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

3. 28 agosto 2024 alle ore 22:06 UTCmonitoring

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

4. 28 agosto 2024 alle ore 22:39 UTCresolved

   This incident has been resolved.

1. 31 luglio 2024 alle ore 21:46 UTCinvestigating

   We are currently investigating this issue.

2. 31 luglio 2024 alle ore 21:46 UTCidentified

   We have identified the issue and applying the fix now.

3. 31 luglio 2024 alle ore 21:50 UTCmonitoring

   A fix has been applied and we are monitoring the results

4. 31 luglio 2024 alle ore 22:34 UTCresolved

   This incident has been resolved.

1. 30 luglio 2024 alle ore 16:19 UTCinvestigating

   We are currently investigating this issue.

2. 30 luglio 2024 alle ore 16:22 UTCidentified

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

3. 30 luglio 2024 alle ore 16:23 UTCmonitoring

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

4. 30 luglio 2024 alle ore 16:54 UTCresolved

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

1. 19 luglio 2024 alle ore 13:38 UTCidentified

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

2. 19 luglio 2024 alle ore 18:49 UTCidentified

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

3. 19 luglio 2024 alle ore 18:50 UTCresolved

   This incident has been resolved.

1. 25 aprile 2024 alle ore 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 aprile 2024 alle ore 21:42 UTCmonitoring

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

3. 25 aprile 2024 alle ore 22:13 UTCresolved

   This incident has been resolved.

1. 15 febbraio 2024 alle ore 15:38 UTCinvestigating

   We are currently investigating this issue.

2. 15 febbraio 2024 alle ore 15:55 UTCinvestigating

   We are continuing to investigate this issue.

3. 15 febbraio 2024 alle ore 16:03 UTCidentified

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

4. 15 febbraio 2024 alle ore 16:11 UTCmonitoring

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

5. 15 febbraio 2024 alle ore 17:01 UTCresolved

   This incident has been resolved.

1. 31 gennaio 2024 alle ore 17:05 UTCinvestigating

   We are currently investigating this issue.

2. 31 gennaio 2024 alle ore 17:05 UTCidentified

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

3. 31 gennaio 2024 alle ore 17:07 UTCmonitoring

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

4. 31 gennaio 2024 alle ore 17:41 UTCresolved

   This incident has been resolved.