Historial de interrupciones de Lithic

1. 3 de septiembre de 2026 a las 20:13 UTCidentified

   Estamos viendo altas 500 respuestas y mayor latencia en POST /v1/tokenizations/{tokenization token}/deactivar para las tokenizaciones de Mastercard, comenzando alrededor de las 13:00 UTC. Esto es causado por una degradación en la API de servicio de atención al cliente MDES de Mastercard. Mastercard ha reconocido la cuestión y está trabajando en ella.

2. 3 de septiembre de 2026 a las 22:08 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 26 de agosto de 2026 a las 12:26 UTCresolved

   El procesamiento de la autorización de la tarjeta fue parcialmente degradado entre 11:53 y 11:59 UTC. La cuestión se ha resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 22 de agosto de 2026 a las 19:31 UTCidentified

   Un problema de la red Visa ha retrasado la reconciliación. - Los datos de API de liquidación se retrasarán - El problema es causado por la red - Los clientes que necesitan un total de liquidación deben utilizar el punto final de la red

2. 23 de agosto de 2026 a las 3:04 UTCmonitoring

   - Hemos añadido todos los registros perdidos a la API de liquidación - La API de liquidación todavía no está completa porque falta fichas de transacción y fichas de eventos porque todavía no hemos recibido todos los claros de Visa - Las cantidades totales en el punto final resumido son correctas y completas. - Agregaremos los datos perdidos cuando esté disponible

3. 23 de agosto de 2026 a las 3:05 UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

4. 23 de agosto de 2026 a las 12:39 UTCresolved

   Resueltos — Delayed Visa BASE II Clearings 22 de agosto de 19:03 UTC – 23 de agosto de 07:19 UTC Identificamos un retraso en la recepción de mensajes de compensación de Visa, causado por un problema en la red de Visa. Este tratamiento retardado de los datos de liquidación de Visas en la API de liquidación (SAPI) para las transacciones reportadas el 22 de agosto. Quién fue afectado: Los clientes que confían en SAPI para Visa recon en las transacciones de Aug 22. Otras redes no se vieron afectadas, y los totales de asentamientos globales (a través del punto final de la red) siguieron siendo exactos en todas partes. Lo que hicimos: Vigilamos mientras Visa funcionaba a través de su atraso, y una vez que quedó claro el retraso se extendería más allá de la ventana de procesamiento normal, liberamos datos de liquidación disponibles. Los totales sumarios fueron correctos y completos en todo momento. Sin embargo, los detalles individuales de los registros de liquidación eran incompletos: faltaban referencias de transacción y de token de eventos, ya que esas referencias sólo se pueden adjuntar una vez que se haya recibido la correspondiente compensación de Visa y procesada a través de la API de transacción. A medida que los claros de Visa continuaron llegando, respaldamos las referencias perdidas hasta que todos los registros estaban completos. Resolución: Al 07:19 UTC el 23 de agosto, se han recibido y procesado todas las exenciones de Visa BASE II desaparecidas. Solución de datos de API para el 22 de agosto ahora es completo y preciso.

Traducido automáticamente desde la actualización oficial del incidente.

1. 3 de julio de 2026 a las 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 de julio de 2026 a las 23:43 UTCresolved

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

1. 15 de junio de 2026 a las 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 de junio de 2026 a las 16:15 UTCidentified

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

3. 15 de junio de 2026 a las 18:38 UTCidentified

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

4. 15 de junio de 2026 a las 19:13 UTCmonitoring

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

5. 15 de junio de 2026 a las 20:34 UTCresolved

   This incident has been resolved.

1. 8 de junio de 2026 a las 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 de junio de 2026 a las 17:49 UTCmonitoring

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

2. 2 de junio de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 23:41 UTCresolved

   This incident has been resolved.

1. 22 de abril de 2026 a las 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 de abril de 2026 a las 16:52 UTCmonitoring

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

3. 22 de abril de 2026 a las 17:54 UTCresolved

   This incident has been resolved.

1. 22 de abril de 2026 a las 14:11 UTCinvestigating

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

2. 22 de abril de 2026 a las 15:30 UTCidentified

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

3. 22 de abril de 2026 a las 15:34 UTCmonitoring

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

4. 22 de abril de 2026 a las 15:58 UTCresolved

   This incident has been resolved.

1. 7 de abril de 2026 a las 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 de abril de 2026 a las 1:33 UTCinvestigating

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

2. 2 de abril de 2026 a las 1:49 UTCidentified

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

3. 2 de abril de 2026 a las 2:08 UTCresolved

   This incident has been resolved.

1. 24 de febrero de 2026 a las 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 de febrero de 2026 a las 17:06 UTCinvestigating

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

3. 24 de febrero de 2026 a las 17:17 UTCmonitoring

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

4. 24 de febrero de 2026 a las 18:59 UTCresolved

   This incident has been resolved.

1. 22 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 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 de febrero de 2026 a las 19:04 UTCresolved

   This incident has been resolved.

1. 16 de diciembre de 2025 a las 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 de noviembre de 2025 a las 0: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 de noviembre de 2025 a las 0:47 UTCinvestigating

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

2. 11 de noviembre de 2025 a las 1:09 UTCinvestigating

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

3. 11 de noviembre de 2025 a las 1: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 de noviembre de 2025 a las 4: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 de noviembre de 2025 a las 6:28 UTCmonitoring

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

6. 11 de noviembre de 2025 a las 6: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