Lithic had 48 outages in the last 2 years totaling 110h 11m of downtime — averaging 2 incidents per month.
There were 48 Lithic outages since June 18, 2024 totaling 110h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
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.
This incident has been resolved.
We are currently investigating an issue causing increased latency in delivery of transaction webhooks for some customers. Authorization processing is unaffected.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating an issue that is preventing cards from being added to digital wallets.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are investigating an issue that may cause unexpected declines in cards that were created in the last 30 minutes.
We've identified the issue and are seeing improvements in behavior across the network.
This incident has been resolved.
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.
We have identified an issue that is causing unexpected declines on some programs and are currently investigating.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
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.
Cards created between 2025-12-16 20:05 and 20:25 were unable to transact until this was resolved at 20:25 UTC.
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.
We are currently investigating an issue that may be causing unexpected declines on MasterCard authorizations.
We are continuing to investigate unexpected declines and are working with our network partners on a resolution.
We have identified the issue causing unexpected declines on authorizations and are actively working with our network partners to implement a resolution.
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.
A fix has been deployed and we are seeing improvement in authorizations across the network.
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
We have identified an issue on our end causing newly provisioned cards to be unable to transact, beginning with cards created after 17:34 UTC 2025-11-04
A fix has been implemented and we are monitoring the results.
The issue has been resolved and all cards are now able to transact.
Lithic Dashboard is experiencing continued degradation and we are working on further mitigations. Due to the ongoing AWS outage we are experiencing some service degradation as a result of impact to some of our vendors: - We are still experiencing some delay in KYB status updates - Tokenizations and OTP have been processed successfully throughout the day, however some intermittent impact may have occurred due to impact to our SMS and email OTP vendors
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
API and Dashboard operations returned to normal functionality. We are still monitoring an issue where a small number of digital wallet tokenizations are being declined unexpectedly.
This incident has been resolved.
We are currently investigating an issue that may delay the return of transaction data.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing elevated errors in AMEX tokenizations. This is causing tokenizations on AMEX to be declined.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have been made aware of an issue that caused unexpected card tokenization declines between 19:10 UTC and 20:30 UTC. During this time, cardholders were unable to add cards to digital wallets.
We are currently investigating an issue that may be causing delays in outgoing webhooks.
This incident has been resolved.
We are seeing slightly degraded/delayed Webhook delivery for some customers, but that authorization processing is unaffected. We are investigating and working on remediating.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A small number of customers may have experienced interruptions with KYC service between 13:20 to 13:40 UTC today.
We are currently investigating an issue that is causing the API to not respond. We will provide an update shortly.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
Issue with API calls now resolved. Transaction processing was never affected. Systems operating normally; monitoring continues.
This incident has been resolved.
We are currently investigating an issue that is causing a slight increase of authorization declines.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have been made aware of an issue that caused a service interruption to /v1/cards endpoints between 18:05 UTC to 18:06 UTC.
We are currently experience a delay receiving clearing data from VISA for settlement date 2025-04-12. Authorizations are unaffected. Clients should be aware that Transaction API data for their VISA programs may be incomplete for 2025-04-12. Settlement API data for VISA with a settlement date of 2025-04-12 is also delayed. The issue is under investigation by VISA.
VISA is still actively investigating the issue, and believes the root cause is identified. As of now there is no definitive timeline for resolution. The issue now affects clearing data for 2025-04-13.
VISA has positively identified the issue, and declared a global incident affecting clearing and settlement. Their support team has communicated that backlogged clearing records will start being delivered overnight tonight.
Clearing data for 2025-04-14 has arrived complete, the original issue appears fixed by VISA. Delayed clearing data for 2025-04-12 and 2025-04-13 has started to arrive. Clients will see backdated events posting into the transactions API for those dates.
VISA clearing data for 2025-04-12 has now been completely processed. VISA clearing data for 2025-04-13 is complete, however some records have been duplicated. Corrections to back out the duplicates will be posted shortly.
All corrections have been processed for 2025-04-13. Transaction data and settlement data are complete in API. We are continuing to monitor and verify.
This incident has been resolved.
We are investigating an issue that may cause a delay in updating the state of a card
A fix has been deployed and the issue has been resolved. The delays occurred between 15:45 UTC to 16:13 UTC.