Histórico de interrupções do Lithic

1. 3 Gwengolo 2026 da 20:13 UTCidentified

   Estamos vendo elevadas 500 respostas e aumento da latência em POST /v1/tokenizations/{tokenization token}/desativate para Mastercard tokenizations, começando por volta das 13:00 UTC. Isso é causado por uma degradação na API de Serviço ao Cliente da Mastercard. Mastercard reconheceu o problema e está a trabalhar nele.

2. 3 Gwengolo 2026 da 22:08 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 26 Eost 2026 da 12:26 UTCresolved

   O processamento da autorização de cartão foi parcialmente degradado entre 11:53 e 11:59 UTC. A questão foi resolvida.

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Eost 2026 da 19:31 UTCidentified

   A questão da rede de vistos atrasou a reconciliação. - Os dados da API de liquidação serão atrasados - A questão é causada pela rede - Os clientes que necessitam de totais de liquidação devem utilizar o endpoint de totais de rede

2. 23 Eost 2026 da 03:04 UTCmonitoring

   - Adicionámos todos os registos em falta à API de liquidação. - A API de liquidação ainda não está completa porque está faltando tokens de transação e tokens de evento porque ainda não recebemos todas as compensação do Visa - As quantidades totais no endpoint sumário são correctas e completas. - Vamos adicionar os dados em falta quando estiver disponível

3. 23 Eost 2026 da 03:05 UTCmonitoring

   Continuamos monitorando quaisquer outros problemas.

4. 23 Eost 2026 da 12:39 UTCresolved

   Resolvido — Atrasado Base de Vistos II 22 de agosto de 19:03 UTC – 23 de agosto de 07:19 UTC Identificou-se um atraso no recebimento de mensagens de compensação Visa, causado por um problema na rede Visa. Este atraso no processamento de dados de liquidação de vistos na API de liquidação (SAPI) para transações relatadas em 22 de agosto. Quem foi afetado: Clientes que dependem do SAPI para reconhecimento Visa em transações de 22 de agosto. Outras redes não foram afetadas, e os totais de liquidação agregada (através do objetivo de totais de rede) permaneceram precisos ao longo de todo o período. O que fizemos: Nós monitoramos como Visa trabalhou através de seu backlog, e uma vez que ficou claro que o atraso se estenderia após a janela normal de processamento, nós divulgamos dados de liquidação disponíveis. Os totais sumários foram corretos e completos em todos os momentos. No entanto, os dados dos registos de liquidação individuais estavam incompletos: faltavam referências de transacções e de fichas de eventos, uma vez que essas referências só podem ser anexadas quando a compensação correspondente tiver sido recebida do visto e processada através da API de transacção. Como as clareiras do Visa continuaram a chegar, preenchemos as referências que faltavam até que todos os registos estivessem completos. Resolução: A partir das 07:19 UTC em 23 de agosto, todas as clareiras Visa BASE II foram recebidas e processadas. Os dados da API de liquidação para 22 de agosto agora estão completos e precisos.

Traduzido automaticamente da atualização oficial do incidente.

1. 3 Gouere 2026 da 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 Gouere 2026 da 23:43 UTCresolved

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

1. 15 Mezheven 2026 da 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 Mezheven 2026 da 16:15 UTCidentified

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

3. 15 Mezheven 2026 da 18:38 UTCidentified

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

4. 15 Mezheven 2026 da 19:13 UTCmonitoring

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

5. 15 Mezheven 2026 da 20:34 UTCresolved

   This incident has been resolved.

1. 8 Mezheven 2026 da 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 Mezheven 2026 da 17:49 UTCmonitoring

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

2. 2 Mezheven 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 23:41 UTCresolved

   This incident has been resolved.

1. 22 Ebrel 2026 da 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 Ebrel 2026 da 16:52 UTCmonitoring

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

3. 22 Ebrel 2026 da 17:54 UTCresolved

   This incident has been resolved.

1. 22 Ebrel 2026 da 14:11 UTCinvestigating

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

2. 22 Ebrel 2026 da 15:30 UTCidentified

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

3. 22 Ebrel 2026 da 15:34 UTCmonitoring

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

4. 22 Ebrel 2026 da 15:58 UTCresolved

   This incident has been resolved.

1. 7 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 01:49 UTCidentified

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

3. 2 Ebrel 2026 da 02:08 UTCresolved

   This incident has been resolved.

1. 24 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 17:06 UTCinvestigating

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

3. 24 Cʼhwevrer 2026 da 17:17 UTCmonitoring

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

4. 24 Cʼhwevrer 2026 da 18:59 UTCresolved

   This incident has been resolved.

1. 22 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 19:04 UTCresolved

   This incident has been resolved.

1. 16 Kerzu 2025 da 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 Du 2025 da 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 Du 2025 da 00:47 UTCinvestigating

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

2. 11 Du 2025 da 01:09 UTCinvestigating

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

3. 11 Du 2025 da 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 Du 2025 da 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 Du 2025 da 06:28 UTCmonitoring

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

6. 11 Du 2025 da 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