Störungsverlauf von Lithic

1. 3. September 2026 um 20:13 UTCidentified

   Wir sehen erhöhte 500 Antworten und erhöhte Latenz auf POST /v1/tokenizations/{tokenization token}/deaktivieren für Mastercard-Tokenizations, beginnend um 13:00 UTC. Dies wird durch eine Verschlechterung der MDES Customer Service API von Mastercard verursacht. Mastercard hat das Problem erkannt und arbeitet daran.

2. 3. September 2026 um 22:08 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 26. August 2026 um 12:26 UTCresolved

   Die Kartenautorisierungsverarbeitung wurde zwischen 11:53 und 11:59 UTC teilweise abgebaut. Das Problem ist gelöst.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. August 2026 um 19:31 UTCidentified

   Ein Visa-Netzwerkproblem hat die Abstimmung verzögert. - Settlement API-Daten werden verzögert - Das Problem wird durch das Netzwerk verursacht - Kunden, die Abrechnungssummen benötigen, sollten den Endpunkt der Netzwerksummen verwenden

2. 23. August 2026 um 03:04 UTCmonitoring

   - Wir haben alle fehlenden Datensätze zur Settlement API hinzugefügt - Die Abwicklungs-API ist immer noch nicht vollständig, da Transaktions- und Ereignis-Token fehlen, da wir noch nicht alle Clearings von Visa erhalten haben - Die Gesamtbeträge auf dem zusammenfassenden Endpunkt sind korrekt und vollständig. - Wir werden die fehlenden Daten hinzufügen, wenn sie verfügbar sind

3. 23. August 2026 um 03:05 UTCmonitoring

   Wir werden weiterhin auf weitere Probleme achten.

4. 23. August 2026 um 12:39 UTCresolved

   Gelöst — Verzögerte Visa BASE II Clearings Aug 22, 19:03 UTC – Aug 23, 07:19 UTC Wir haben eine Verzögerung beim Empfang von Visa-Clearing-Nachrichten festgestellt, die durch ein Problem im Netzwerk von Visa verursacht wurde. Diese verzögerte Verarbeitung von Visa-Abwicklungsdaten in der Settlement API (SAPI) für Transaktionen, die am 22. August gemeldet wurden. Wer war betroffen: Kunden, die sich auf SAPI für Visa verlassen, informieren sich über Transaktionen am 22. August. Andere Netzwerke waren nicht betroffen, und die aggregierten Abrechnungssummen (über den Endpunkt der Netzwerksummen) blieben durchgehend genau. Was wir taten: Wir überwachten, wie Visa ihren Rückstand durcharbeitete, und sobald klar wurde, dass die Verzögerung über das normale Verarbeitungsfenster hinausreichen würde, veröffentlichten wir verfügbare Abrechnungsdaten. Die Summensummen waren jederzeit korrekt und vollständig. Einzelne Abrechnungsdaten waren jedoch unvollständig: Es fehlten Transaktions- und Ereignis-Token-Referenzen, da diese Referenzen nur angehängt werden können, sobald die entsprechende Verrechnung von Visa erhalten und über die Transaktions-API verarbeitet wurde. Da die Clearings von Visa weiterhin eintrafen, füllten wir die fehlenden Referenzen aus, bis jeder Rekord vollständig war. Resolution: Ab 07:19 UTC am 23. August wurden alle fehlenden Visa BASE II-Freigaben empfangen und bearbeitet. Die Settlement-API-Daten für den 22. August sind jetzt vollständig und korrekt.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 3. Juli 2026 um 22:10 UTCinvestigating

   Some customers are experiencing delays in receiving a subset of Mastercard clearing and dispute data. We are investigating the issue.

2. 3. Juli 2026 um 23:43 UTCresolved

   Mastercard processing issues have been identified, resolved, and backlog processing is complete. This incident is resolved.

1. 15. Juni 2026 um 15:15 UTCinvestigating

   Customers may experience elevated error rates and timeouts, including intermittent failures when provisioning cards and creating cards with dynamic card art or a qr code.

2. 15. Juni 2026 um 16:15 UTCidentified

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

3. 15. Juni 2026 um 18:38 UTCidentified

   We are currently implementing a fix. Please note, this will cause 1-5 minutes of downtime.

4. 15. Juni 2026 um 19:13 UTCmonitoring

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

5. 15. Juni 2026 um 20:34 UTCresolved

   This incident has been resolved.

1. 8. Juni 2026 um 12:50 UTCresolved

   Api partially degraded and timing out 9:55-10:10 UTC. Customers may have experienced elevated intermittent timeouts and errors.

1. 2. Juni 2026 um 17:49 UTCmonitoring

   We are investigating an issue that is causing a delay in clearing events from Mastercard.

2. 2. Juni 2026 um 19:30 UTCresolved

   Mastercard clearing files containing errors resulted in delayed processing of Mastercard clearings for 2026-06-02. As of 18:00 UTC all clearing events and associated Settlement API records were complete. Network Totals data was marked as complete at 19:25 UTZ.

1. 14. Mai 2026 um 15:19 UTCresolved

   Between 22:02–22:07 ET on May 13, authorization decisions were handled by card network stand-in processing rather than Lithic. Customers may have seen approvals or declines that differed from normal Lithic behavior during this window.

1. 1. Mai 2026 um 21:23 UTCidentified

   Visa is experiencing an incident affecting VisaNet Clearing and Settlement file delivery. This is causing delays in our Settlement Summary completion and Settlement API data. We are actively monitoring the situation and will update this page as we learn more.

2. 1. Mai 2026 um 23:41 UTCresolved

   This incident has been resolved.

1. 22. April 2026 um 16:45 UTCinvestigating

   We are currently investigating an issue causing increased latency in delivery of transaction webhooks for some customers. Authorization processing is unaffected.

2. 22. April 2026 um 16:52 UTCmonitoring

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

3. 22. April 2026 um 17:54 UTCresolved

   This incident has been resolved.

1. 22. April 2026 um 14:11 UTCinvestigating

   We are investigating an issue that is preventing cards from being added to digital wallets.

2. 22. April 2026 um 15:30 UTCidentified

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

3. 22. April 2026 um 15:34 UTCmonitoring

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

4. 22. April 2026 um 15:58 UTCresolved

   This incident has been resolved.

1. 7. April 2026 um 17:58 UTCresolved

   We experienced an issue with our sandbox environment where card authorizations were failing and API requests were returning unexpected errors. Our engineering team identified the root cause and restored service.

1. 2. April 2026 um 01:33 UTCinvestigating

   We are investigating an issue that may cause unexpected declines in cards that were created in the last 30 minutes.

2. 2. April 2026 um 01:49 UTCidentified

   We've identified the issue and are seeing improvements in behavior across the network.

3. 2. April 2026 um 02:08 UTCresolved

   This incident has been resolved.

1. 24. Februar 2026 um 16:30 UTCmonitoring

   Between 16:12 UTC and 16:21 UTC, some ACH transactions were unexpectedly declined. We are working to identify the root cause and scope of impact.

2. 24. Februar 2026 um 17:06 UTCinvestigating

   We have identified an issue that is causing unexpected declines on some programs and are currently investigating.

3. 24. Februar 2026 um 17:17 UTCmonitoring

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

4. 24. Februar 2026 um 18:59 UTCresolved

   This incident has been resolved.

1. 22. Februar 2026 um 18:11 UTCresolved

   We observed elevated response errors from our public API between 16:18 UTC and 16:38 UTC. The issue has since been resolved. Transaction processing was not affected.

1. 17. Februar 2026 um 17:49 UTCinvestigating

   We are currently experiencing an issue causing unexpected declines on some newly created cards. Our team is actively investigating. We will provide updates as more information becomes available.

2. 17. Februar 2026 um 17:58 UTCresolved

   We detected an issue that caused unexpected declines on cards that were created between 2026-02-17 17:05 UTC and 2026-02-17 17:53 UTC. The issue has been since resolved, and cards created during that time can now transact as expected.

1. 4. Februar 2026 um 19:02 UTCinvestigating

   We detected an issue that caused unexpected declines on cards that were created between 2026-02-04 17:48 UTC and 2026-02-04 18:37 UTC. The issue has been since resolved, and cards created during that time can now transact as expected.

2. 4. Februar 2026 um 19:04 UTCresolved

   This incident has been resolved.

1. 16. Dezember 2025 um 20:42 UTCresolved

   Cards created between 2025-12-16 20:05 and 20:25 were unable to transact until this was resolved at 20:25 UTC.

1. 26. November 2025 um 00:33 UTCresolved

   A change deployed on our end caused tokenizations to be declined between 2025-11-25 00:15:00 and 2025-11-25 02:19:00 UTC. The issue has since been fully resolved, and tokenization behavior has returned to normal.

1. 11. November 2025 um 00:47 UTCinvestigating

   We are currently investigating an issue that may be causing unexpected declines on MasterCard authorizations.

2. 11. November 2025 um 01:09 UTCinvestigating

   We are continuing to investigate unexpected declines and are working with our network partners on a resolution.

3. 11. November 2025 um 01:57 UTCidentified

   We have identified the issue causing unexpected declines on authorizations and are actively working with our network partners to implement a resolution.

4. 11. November 2025 um 04:03 UTCidentified

   We apologize for the delay. We can confirm that a fix will be implemented soon and will provide an ETA once we receive confirmation from our network partners.

5. 11. November 2025 um 06:28 UTCmonitoring

   A fix has been deployed and we are seeing improvement in authorizations across the network.

6. 11. November 2025 um 06:38 UTCresolved

   Working with our network partners, we have resolved an issue that was affecting a portion of MasterCard authorizations for one specific issuer. Normal processing has resumed