Lithic driftsforstyrrelser

1. 3. september 2026 kl. 20.13 UTCidentified

   Vi ser forhøjede 500 svar og øget latency på POST / v1 / Medicalization / {Medicalization _ token} / deaktivere for Mastercard Medicalizations, der begynder omkring 13: 00 UTC. Dette skyldes en nedbrydning i Mastercards MDES Customer Service API. Mastercard har erkendt spørgsmålet og arbejder på det.

2. 3. september 2026 kl. 22.08 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 26. august 2026 kl. 12.26 UTCresolved

   Behandlingen af kort blev delvist nedbrudt mellem 11: 53 og 11: 59 UTC. Spørgsmålet er løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 22. august 2026 kl. 19.31 UTCidentified

   Et Visa netværk problem har forsinket forsoning. - Afvikling API data vil blive forsinket - Problemet skyldes netværket - Kunder, der har brug for afregning totaler bør bruge netværket totaler endpoint

2. 23. august 2026 kl. 03.04 UTCmonitoring

   - Vi har tilføjet alle manglende optegnelser til Settlement API - The settlement API er stadig ikke færdig, fordi det mangler transaktion tokens og begivenhed tokens, fordi vi endnu ikke har modtaget alle clearings fra Visa - De samlede beløb på det sammenfattende endepunkt er korrekte og fuldstændige. - Vi tilføjer de manglende data, når den er tilgængelig

3. 23. august 2026 kl. 03.05 UTCmonitoring

   Vi fortsætter med at overvåge for yderligere spørgsmål.

4. 23. august 2026 kl. 12.39 UTCresolved

   Opløst - Forsinkede Visa BASE II-clearinger Aug 22, 19: 03 UTC - Aug 23, 07: 19 UTC Vi identificerede en forsinkelse i modtagelsen af Visa clearing beskeder, forårsaget af et problem på Visa 's netværk. Denne forsinkede behandling af visumafviklingsdata i afviklingsAPI (SAPI) for transaktioner indberettet den 22. august. Hvem blev påvirket: Kunder, der er afhængige af SAPI for Visa recon på aug 22 transaktioner. Andre net blev ikke påvirket, og de samlede afviklingstotaler (via nettets samlede endepunkt) forblev nøjagtige hele vejen igennem. Hvad vi gjorde: Vi overvågede som Visa arbejdede gennem deres efterslæb, og når det blev klart, at forsinkelsen ville strække sig forbi det normale behandlingsvindue, vi frigivet tilgængelige afviklingsdata. Summariske totaler var korrekte og fuldstændige til enhver tid. Oplysninger om individuelle afviklingsposter var imidlertid ufuldstændige: de manglede transaktions- og hændelsesreferencer, da disse referencer kun kan vedlægges, når den tilsvarende clearing er modtaget fra Visa og behandlet gennem transaktions- API. Da Visa 's opklaringer fortsatte med at ankomme, kom vi tilbage med de manglende referencer indtil alle records var færdige. Opløsning: Fra 07: 19 UTC den 23. aug, alle manglende Visa BASE II clearinger er blevet modtaget og behandlet. Afvikling API data til aug 22 er nu komplet og præcis.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 3. juli 2026 kl. 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 kl. 23.43 UTCresolved

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

1. 15. juni 2026 kl. 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 kl. 16.15 UTCidentified

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

3. 15. juni 2026 kl. 18.38 UTCidentified

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

4. 15. juni 2026 kl. 19.13 UTCmonitoring

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

5. 15. juni 2026 kl. 20.34 UTCresolved

   This incident has been resolved.

1. 8. juni 2026 kl. 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 kl. 17.49 UTCmonitoring

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

2. 2. juni 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 23.41 UTCresolved

   This incident has been resolved.

1. 22. april 2026 kl. 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 kl. 16.52 UTCmonitoring

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

3. 22. april 2026 kl. 17.54 UTCresolved

   This incident has been resolved.

1. 22. april 2026 kl. 14.11 UTCinvestigating

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

2. 22. april 2026 kl. 15.30 UTCidentified

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

3. 22. april 2026 kl. 15.34 UTCmonitoring

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

4. 22. april 2026 kl. 15.58 UTCresolved

   This incident has been resolved.

1. 7. april 2026 kl. 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 kl. 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 kl. 01.49 UTCidentified

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

3. 2. april 2026 kl. 02.08 UTCresolved

   This incident has been resolved.

1. 24. februar 2026 kl. 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 kl. 17.06 UTCinvestigating

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

3. 24. februar 2026 kl. 17.17 UTCmonitoring

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

4. 24. februar 2026 kl. 18.59 UTCresolved

   This incident has been resolved.

1. 22. februar 2026 kl. 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 kl. 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 kl. 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 kl. 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 kl. 19.04 UTCresolved

   This incident has been resolved.

1. 16. december 2025 kl. 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 kl. 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 kl. 00.47 UTCinvestigating

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

2. 11. november 2025 kl. 01.09 UTCinvestigating

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

3. 11. november 2025 kl. 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 kl. 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 kl. 06.28 UTCmonitoring

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

6. 11. november 2025 kl. 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