MeridianLink Outage History

Started Oct 21, 2026, 05:16 PM UTC· resolved Oct 21, 2026, 07:02 PM UTC

1. identified Oct 21, 2026, 05:16 PM UTC

   PriceMyLoan is experiencing issues today loading today's rates for some investors. Development is working resolving this issue. We will post updates as they become available.

2. resolved Oct 21, 2026, 07:02 PM UTC

   This issue was resolved at 11:15 AM PT / 2:15 PM ET

Read the full incident report →

Started Oct 20, 2026, 08:23 PM UTC· resolved Oct 21, 2026, 02:50 PM UTC

1. investigating Oct 20, 2026, 08:23 PM UTC

   MeridianLink is aware that in some cases loans created in Mortgage Access are not submitting immediately to Mortgage LOS or OpenClose LOS. This is impacting only some clients. If your loan is shown as "submitted" in Mortgage Access but you are not finding the loan in the LOS, please allow a few hours for the loan to appear. We are currently working on resolving this temporary issue.

2. identified Oct 20, 2026, 10:03 PM UTC

   Development has identified the issue and will be deploying a hot fix tonight 10/20/26 to resolve the submission delays.

3. resolved Oct 21, 2026, 02:50 PM UTC

   This has been resolved. Loans that failed to submit before today will need to be submitted again.

Read the full incident report →

Started Oct 20, 2026, 08:08 PM UTC· resolved Oct 21, 2026, 01:55 AM UTC

1. investigating Oct 20, 2026, 08:08 PM UTC

   We are currently investigating an issue where applications are not appearing in the ACH Pending and ACH Batch queues.

2. identified Oct 20, 2026, 08:54 PM UTC

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

3. monitoring Oct 20, 2026, 09:44 PM UTC

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

4. resolved Oct 21, 2026, 01:55 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 19, 2026, 02:10 PM UTC· resolved Oct 19, 2026, 04:10 PM UTC

1. investigating Oct 19, 2026, 02:10 PM UTC

   The pricing engine, PriceMyLoan, is experiencing errors when loading FNMA rates today resulting in a delay in loading today's FNMA rate sheets. The team is working to expedite this issue. Once rates have been updated, we will inform you.

2. resolved Oct 19, 2026, 04:10 PM UTC

   The issue has been resolved, and all services are operating normally. Thank you for your patience while our teams worked to address this issue. If you continue to experience any problems, please contact Support.

Read the full incident report →

Started Oct 19, 2026, 01:03 PM UTC· resolved Oct 23, 2026, 07:42 PM UTC

1. investigating Oct 19, 2026, 01:03 PM UTC

   We are aware of reports from some clients that certain Data Connect tables are not refreshing as expected. The following tables are currently affected: - da_funding - da_application_individual_account - da_applicants_custom_questions This delay will not cause your daily processes to fail. However, any downstream reports that use these tables may not show the most recent data until the issue is resolved. Our team is investigating the issue and will share an update with next steps as soon as more information is available. We apologize for any inconvenience and appreciate your patience.

2. investigating Oct 19, 2026, 04:09 PM UTC

   Our team is still investigating the refresh delay affecting Data Connect tables Downstream reports that use these tables may still show older data until the issue is resolved. We’ll post another update as soon as we have more information. Thank you for your patience.

3. monitoring Oct 19, 2026, 08:51 PM UTC

   While investigating, our team found additional Data Connect tables that were not refreshing as expected. The affected tables have now been fixed and will be refreshing normally going forward. What you may notice: For the affected tables, you may notice around 9 extractions, with missing data stored in the 2026-10-19 mid day extraction. da_funding: The missing data for da_funding will be filled in during tomorrow’s scheduled refresh. Your daily processes will keep running normally. We’re monitoring the tables to make sure refreshes continue as expected, and we’ll post another update after tomorrow’s refresh finishes. Thank you for your patience.

4. monitoring Oct 20, 2026, 04:23 PM UTC

   We’re still monitoring a refresh issue that could affect a number of Data Connect tables. Our team has identified the following 37 tables that were not refreshing as expected: da_applicants_custom_questions da_applicants_truncated da_application_account_last_modified da_application_individual_account da_application_individual_account_custom_questions da_bl_specific_loan_info da_ml_property_info da_pl_specific_loan_info da_vl_specific_dealership_processing da_vl_specific_loan_info da_vl_specific_vehicle da_company_current_address da_company_mailing_address da_current_address da_current_employment da_declarations da_mailing_address da_monthly_debt da_monthly_income da_other_income da_previous_employment da_funding da_insurance_options da_custom_questions da_price_adjustments da_transaction_entity da_transaction_user_int da_underwriting_info da_spouse_current_address da_spouse_current_employment da_spouse_custom_questions da_spouse_declarations da_spouse_mailing_address da_spouse_monthly_debt da_spouse_monthly_income da_spouse_other_income da_spouse_previous_employment Clients on the earlier extraction time who reported missing data from the list of tables above should now see refreshed data. This delay was caused by a pipeline failure that our team fixed this morning, after the scheduled delivery time. This group will have data available at the expected time going forward (12 AM PST/ 3 AM EST). All other clients would have received data in this mornings refresh for the tables above. The following 5 tables are still not refreshed and are expected to be fixed by tomorrow’s refresh: da_audit_summary da_disbursements_check da_disbursements_deposit da_disbursements_fee da_disbursements_loan We apologize for the inconvenience and will post another update once the remaining tables are refreshed. If you run into any other issues, please submit a support ticket through our support portal.

5. identified Oct 21, 2026, 04:56 PM UTC

   We’re continuing to work on the refresh issue affecting a number of Data Connect tables. Since our last update, we have fixed the remaining 5 tables and found the cause of the delay in the other 37. Those tables are still one day behind, and we’re working to bring them current. We’ve also found a separate issue affecting clients with DEMO/BETA pipelines. These tables are now refreshing as expected and available on your pipeline to pull: da_audit_summary da_disbursements_check da_disbursements_deposit da_disbursements_fee da_disbursements_loan To prevent any gaps, this morning’s refresh included data from 10/14 through 10/20 (partial day) for these tables. You do not need to change your current data extraction process. The 37 tables below are still one day behind. Root cause: Our team found that a table used to capture data changes was not being refreshed at the correct frequency. The fix for this is in progress. We are now working to deliver the remaining missing day of data to your pipeline. da_applicants_custom_questions da_applicants_truncated da_application_account_last_modified da_application_individual_account da_application_individual_account_custom_questions da_bl_specific_loan_info da_ml_property_info da_pl_specific_loan_info da_vl_specific_dealership_processing da_vl_specific_loan_info da_vl_specific_vehicle da_company_current_address da_company_mailing_address da_current_address da_current_employment da_declarations da_mailing_address da_monthly_debt da_monthly_income da_other_income da_previous_employment da_funding da_insurance_options da_custom_questions da_price_adjustments da_transaction_entity da_transaction_user_int da_underwriting_info da_spouse_current_address da_spouse_current_employment da_spouse_custom_questions da_spouse_declarations da_spouse_mailing_address da_spouse_monthly_debt da_spouse_monthly_income da_spouse_other_income da_spouse_previous_employment DEMO/BETA pipelines: Clients with access to DEMO/BETA pipelines are also not seeing refreshed data in the 37 tables above. This is a separate issue. We have identified the cause and are working on a fix. Once it’s in place, we will deliver data for these tables from 10/14 to the present clients do not have a gap. We will share updates and ETA as soon as possible. We apologize for the inconvenience. If you run into any other issues, please submit a support ticket through our support portal.

6. monitoring Oct 22, 2026, 12:46 AM UTC

   Our team has fixed the issues behind this incident. This includes the refresh delay affecting the 37 Data Connect tables and the separate issue affecting clients with DEMO pipelines. All affected tables should now be refreshing as expected. What you may notice: You may see multiple extractions for 10/21. These come from backend testing we ran while validating the pipeline fix. If you use our Python scripts, no action is needed. The scripts will import all of the extractions correctly. If you use a custom process, please make sure it pulls every 10/21 extraction so that no data is missed. We’ll keep monitoring the refreshes and plan to close this incident tomorrow morning. Thank you for your patience. If you run into any issues, please submit a support ticket through our support portal.

7. identified Oct 22, 2026, 03:40 PM UTC

   We’ve found duplicate records in yesterday’s (10/21-10/22) refresh of the 37 Data Connect tables listed in our previous updates. Our team is investigating the cause and working on a fix. Because of this, we are no longer planning to close this incident this morning. We’ll post another update with a resolution and any steps you may need to take as soon as we have them. We apologize for the inconvenience and appreciate your patience. If you run into any other issues, please submit a support ticket through our support portal.

8. monitoring Oct 22, 2026, 08:30 PM UTC

   We’ve fixed the duplicate records in last night’s refresh of the 37 affected Data Connect tables. We’ve also fixed a separate delay that affected clients on the earlier extraction time. Details on each are below. Duplicate records in the 37 tables: We removed the duplicate records from the affected partition in last night’s refresh. We also fixed the backend code that caused the duplication, so it won’t happen again. If you use our Python scripts, no action is needed. Tomorrow’s refresh will remove the duplicate records from the affected partition automatically. If you use a custom process, please pull the latest extraction again to get the corrected version without duplicates. Missing data for clients on the earlier extraction time (12 AM PST / 3 AM EST): Some of these clients reported missing data this morning. This was caused by an internal pipeline failure, which we fixed at around 9 AM EST. The missing data is now available on the pipeline. If you use our Python scripts, no action is needed. The data will flow through your pipeline automatically. If you use a custom process and did not pull the missing extraction this morning, please pull it now or in the next 7 days. We’ll keep monitoring the refreshes and post another update once we confirm everything is running as expected. We apologize for the inconvenience and appreciate your patience. If you run into any other issues, please submit a support ticket through our support portal.

9. investigating Oct 23, 2026, 01:52 PM UTC

   We’ve received client reports of missing records in the da_applicants_truncated table. Our initial review shows that this mainly affects clients on the earlier extraction time (12 AM PST / 3 AM EST). Our team is reviewing the pipeline to find the cause. We are also checking whether any other tables are affected. We’ll post another update once we know the cause, which tables are affected, and next steps. We apologize for the inconvenience and appreciate your patience.

10. resolved Oct 23, 2026, 07:42 PM UTC

    The issue brought up today is a byproduct of changes that update our pipelines so we can support faster refreshes and larger data loads in the future. These changes are necessary to continue to maintain service time expectations of the product. To help, we will be implementing a change today to hide this byproduct for these crucial tables. In short, items on the older pipeline refresh an hour later than the new one and so we will restrict old pipeline data to only reflect records also in the new pipeline. This will prevent their issue from this morning. Data available in the current load has been moved forward to make sure that records in both pipelines are lined up with each other. If you rerun the sync process you will see these gaps are filled. We apologize for any inconvenience and appreciate your patience as we worked to resolve these issues.

Read the full incident report →

Started Oct 16, 2026, 12:43 PM UTC· resolved Oct 16, 2026, 09:06 PM UTC

1. investigating Oct 16, 2026, 12:43 PM UTC

   We’re looking into an issue where queries against 37 Data Connect tables fail with this error: "DS_INVALID_RESPONSE_FROM_DS_SERVER: The http response returned invalid json" Impact: -Data reads on the 37 tables listed below fail. Schema and metadata queries (for example, information_schema) still work. -All other tables in the share are working normally. -These tables were last ingested successfully on October 15, 2026. Data from that load and earlier is unaffected, but no new data can be pulled from these tables until this is fixed. Our engineering team is investigating at this time and we will follow up once this issue is resolved. We’re sorry for the disruption this may cause to your downstream processes.

2. identified Oct 16, 2026, 03:05 PM UTC

   We’ve found the root cause of todays incident. Our partition scheme was updated for a few tables which prevented successful connection when attempting to refresh your data. That’s why the service returned invalid responses when those tables were read. We’re now repartitioning the affected tables with the correct configuration. We expect the fix to be finished in about 2 hours. You don’t need to do anything for now. Once the fix is in place, please re-run your process. We’ll post another update when the work is done.

3. identified Oct 16, 2026, 05:36 PM UTC

   Repartitioning the affected tables is taking longer than expected. The work is still in progress with our engineers. We’ll post another update by then, or sooner if anything changes. Until the fix is finished, data reads on the affected tables will keep failing. Please hold off on re-running ingestion for these tables until we confirm the fix is complete. We’re sorry for the extended disruption.

4. resolved Oct 16, 2026, 09:06 PM UTC

   This issue is resolved. All affected tables have been repartitioned with the correct configuration, and data pulls are working normally again. What you need to do: Re-run your ingestion jobs to catch up on data since October 15. We apologize that this took longer to fix than we first estimated, and for the disruption to your data pipelines. If you still see errors on any of these tables, please contact Support and include the table name and the error message.

Read the full incident report →

Started Oct 15, 2026, 02:38 PM UTC· resolved Oct 15, 2026, 06:29 PM UTC

1. investigating Oct 15, 2026, 02:38 PM UTC

   We are currently investigating reports of slow page loading and delays in Instascreen, including Manage Client Users and other affected areas. Some users may see spinning or loading indicators when accessing these pages. Our team is actively working on the issue. We will post updates here as we learn more.

2. resolved Oct 15, 2026, 06:29 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 28, 2026, 07:28 PM UTC· resolved Sep 28, 2026, 09:06 PM UTC

1. investigating Sep 28, 2026, 07:28 PM UTC

   We are actively working to replace the FIS BizChex certificate and will provide an update as soon as the replacement is complete. Thank you for your patience.

2. resolved Sep 28, 2026, 09:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 23, 2026, 07:27 PM UTC· resolved Sep 25, 2026, 02:13 PM UTC

1. identified Sep 23, 2026, 07:27 PM UTC

   We are currently experiencing an outage with our Partner Connect service due to an issue affecting our source storage account. Our engineering team is actively working with Databricks to resolve this issue. What's happening: Data Connect and Partner Connect is temporarily unavailable What's Affected: Delta Share access to the following tables: derogatory_summary company_info trade_summary credit_report public_record cc_specific_loan_info spouse applicants_address_ssn consumer_vehicle_processings Workaround: While we work to resolve the underlying storage account issue, you can continue your data refresh process by modifying your scripts to exclude the tables listed above. Your pipeline should complete successfully once these tables are removed from your pull requests. We apologize for this disruption and appreciate your patience as we work to resolve this as quickly as possible. Please reach out via support if you have any questions or concerns.

2. resolved Sep 25, 2026, 02:13 PM UTC

   The underlying storage account issue has been successfully resolved by our support team at Databricks who have been working with our engineering team. Data Connect service is now fully operational and all affected tables are once again accessible.

Read the full incident report →

Started Sep 21, 2026, 01:09 PM UTC· resolved Sep 22, 2026, 01:15 PM UTC

1. identified Sep 21, 2026, 01:09 PM UTC

   A data refresh delay affecting Partner Connect vendors has been identified. Our team has found the cause of the issue and subsequent pipelines are now running. We apologize for any inconvenience this may cause.

2. resolved Sep 22, 2026, 01:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 18, 2026, 01:40 PM UTC· resolved Sep 18, 2026, 05:22 PM UTC

1. investigating Sep 18, 2026, 01:40 PM UTC

   We are currently experiencing an outage with our Partner Connect service due to an issue affecting our source storage account. Our engineering team is actively working to resolve this issue. What's happening: Partner Connect is temporarily unavailable What's Affected: Delta Share access to the following tables: derogatory_summary company_info trade_summary credit_report public_record cc_specific_loan_info spouse applicants_address_ssn consumer_vehicle_processings Workaround: While we work to resolve the underlying storage account issue, you can continue your data refresh process by modifying your scripts to exclude the tables listed above. Your pipeline should complete successfully once these tables are removed from your pull requests. We apologize for this disruption and appreciate your patience as we work to resolve this as quickly as possible. Please reach out via support if you have any questions or concerns.

2. investigating Sep 18, 2026, 04:09 PM UTC

   Our engineering team is working directly with Microsoft Azure and Databricks support to diagnose and remediate the storage account issue. We will prioritize this resolution and provide updates as we make progress. We sincerely apologize for this disruption to your operations. If you have questions, concerns, or need assistance implementing the workaround, please contact our support team.

3. monitoring Sep 18, 2026, 05:16 PM UTC

   Update: The underlying storage account issue has been successfully resolved by our support team at Databricks who have been working with our engineering team. Partner Connect service is now fully operational and all affected tables are once again accessible. What You Need to Do: -You can resume your normal data refresh processes immediately -If you had modified your scripts to exclude affected tables, you can restore them and rerun your pipelines Affected Tables (Now Available): derogatory_summary company_info trade_summary credit_report public_record cc_specific_loan_info spouse applicants_address_ssn consumer_vehicle_processings Ongoing Monitoring: Our engineering team will continue to actively monitor the system to ensure stability and detect any potential issues. Support: If you experience any issues when rerunning your pipelines, please reach out via support if you have any questions or concerns. We apologize for this disruption and appreciate your patience as we work to resolve this as quickly as possible.

4. resolved Sep 18, 2026, 05:22 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 18, 2026, 12:47 PM UTC· resolved Sep 18, 2026, 05:22 PM UTC

1. investigating Sep 18, 2026, 12:47 PM UTC

   We are currently experiencing an outage with our Data Connect service due to an issue affecting our source storage account. Our engineering team is actively working to resolve this issue. What's happening: Data Connect is temporarily unavailable What's Affected: Delta Share access to the following tables: da_derogatory_summary da_company_info da_trade_summary da_credit_report da_public_record da_cc_specific_loan_info da_spouse da_applicants_address_ssn da_consumer_vehicle_processings Workaround: While we work to resolve the underlying storage account issue, you can continue your data refresh process by modifying your scripts to exclude the tables listed above. Your pipeline should complete successfully once these tables are removed from your pull requests. We apologize for this disruption and appreciate your patience as we work to resolve this as quickly as possible. Please reach out via support if you have any questions or concerns.

2. investigating Sep 18, 2026, 04:09 PM UTC

   Our engineering team is working directly with Microsoft Azure and Databricks support to diagnose and remediate the storage account issue. We will prioritize this resolution and provide updates as we make progress. We sincerely apologize for this disruption to your operations. If you have questions, concerns, or need assistance implementing the workaround, please contact our support team.

3. monitoring Sep 18, 2026, 05:15 PM UTC

   Update: The underlying storage account issue has been successfully resolved by our support team at Databricks who have been working with our engineering team. Data Connect service is now fully operational and all affected tables are once again accessible. What You Need to Do: -You can resume your normal data refresh processes immediately -If you had modified your scripts to exclude affected tables, you can restore them and rerun your pipelines Affected Tables (Now Available): da_derogatory_summary da_company_info da_trade_summary da_credit_report da_public_record da_cc_specific_loan_info da_spouse da_applicants_address_ssn da_consumer_vehicle_processings Ongoing Monitoring: Our engineering team will continue to actively monitor the system to ensure stability and detect any potential issues. Support: If you experience any issues when rerunning your pipelines, please reach out via support if you have any questions or concerns. We apologize for this disruption and appreciate your patience as we work to resolve this as quickly as possible.

4. resolved Sep 18, 2026, 05:22 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 17, 2026, 04:48 PM UTC· resolved Sep 17, 2026, 08:08 PM UTC

1. identified Sep 17, 2026, 04:48 PM UTC

   Our team is actively investigating the cause of a data refresh delay affecting the Insight Mortgage data source. They have estimated that this will be resolved in approximately 2 hours and 30 minutes. We sincerely apologize for the inconvenience this may cause and appreciate your patience as we work to restore normal processing.

2. resolved Sep 17, 2026, 08:08 PM UTC

   Insight Mortgage data source data is now refreshed, please reach out if there are any issues!

Read the full incident report →

Started Sep 17, 2026, 02:03 PM UTC· resolved Sep 18, 2026, 01:37 PM UTC

1. identified Sep 17, 2026, 02:03 PM UTC

   We have identified the cause of the issue impacting Meridianlink Consumer: locked applications. Our teams are working on a resolution and taking steps to restore normal operation. The current workaround is to exit the application and reopen it, or unlock the application. We will continue to share updates as progress.

2. identified Sep 17, 2026, 03:06 PM UTC

   We have identified the cause of the issue impacting Meridianlink Consumer: locked applications. Our teams are working on a resolution and taking steps to restore normal operation. We will continue to share updates as progress.

3. identified Sep 17, 2026, 03:32 PM UTC

   Our developers have identified the issue and are working on a fix, which we expect to deploy tonight. In the meantime, please continue using the workaround provided.

4. resolved Sep 18, 2026, 01:37 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 17, 2026, 12:56 PM UTC· resolved Sep 21, 2026, 01:04 PM UTC

1. investigating Sep 17, 2026, 12:56 PM UTC

   A data refresh delay affecting Partner Connect vendors has been identified. Our team is currently reviewing the cause of the delay. Affected tables are the following: - Tables referencing Credit Report data - Tables referencing comment fields (Internal Comments, Stipulation Comments, etc.) We apologize for any inconvenience this may have caused. We will follow up with more information once available.

2. identified Sep 17, 2026, 08:11 PM UTC

   The issue is identified and we are running subsequent pipelines. Unfortunately, this updated data will not be available until tomorrows refresh. We will continue to post updates as the refresh is in progress.

3. identified Sep 18, 2026, 05:18 PM UTC

   We are continuing to run subsequent pipelines. Unfortunately, this updated data will not be available until tomorrows refresh. We will continue to post updates as the refresh is in progress.

4. resolved Sep 21, 2026, 01:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 16, 2026, 01:02 PM UTC· resolved Sep 16, 2026, 01:55 PM UTC

1. identified Sep 16, 2026, 01:02 PM UTC

   We have identified the cause of the issue impacting our Resources Center (Client Portal) and confirmed it is related to a third‑party vendor dependency. Our vendor partner is actively working on a resolution, and we are closely coordinating with them to support progress and minimize impact. This issue is impacting both Chat and Salesforce cases. We are currently experiencing latency and intermittent errors. We will continue to share updates as we receive additional information.

2. resolved Sep 16, 2026, 01:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 09, 2026, 07:11 PM UTC· resolved Sep 09, 2026, 09:30 PM UTC

1. investigating Sep 09, 2026, 07:11 PM UTC

   Our team is actively investigating the cause of a data refresh delay affecting the Insight Consumer and Opening data source. We sincerely apologize for the inconvenience this may cause and appreciate your patience as we work to restore normal processing.

2. resolved Sep 09, 2026, 09:30 PM UTC

   Insight Consumer and Opening data source data is now refreshed, please reach out if there are any issues!

Read the full incident report →

Started Sep 09, 2026, 01:35 PM UTC· resolved Sep 10, 2026, 02:20 PM UTC

1. identified Sep 09, 2026, 01:35 PM UTC

   We experienced a delay in today's Data Connect refresh. Affected pipelines are rerunning and should complete within approximately 3 hours. Clients on our earlier run times can rerun their pipelines now for data. We will provide an update as soon as possible. We sincerely apologize for the inconvenience this may cause.

2. identified Sep 09, 2026, 03:48 PM UTC

   We have now also identified an issue where the materialized views for certain tables are causing the pipeline to fail for all clients. We are investigating the cause of this issue and will follow up once we have more information.

3. identified Sep 09, 2026, 08:19 PM UTC

   Current Situation: We've identified the root cause of the Data Connect service issue. What's Affected: Delta Share access to the following tables: da_derogatory_summary da_company_info da_trade_summary da_credit_report da_public_record da_cc_specific_loan_info da_spouse da_applicants_address_ssn da_consumer_vehicle_processings Data Refresh Status: All data has been fully refreshed and is current. Workaround: While we work to resolve the underlying storage account issue, you can continue your data refresh process by modifying your scripts to exclude the tables listed above. Your pipeline should complete successfully once these tables are removed from your pull requests. Resolution: Our engineering team is actively coordinating with our internal infrastructure teams to resolve the storage account configuration issue. We will provide updates as progress is made and will notify you immediately once full access is restored. We apologize for this disruption and appreciate your patience and flexibility.

4. resolved Sep 10, 2026, 02:20 PM UTC

   We can confirm that the Data Connect outage that was affecting your data pulls is now resolved. Our engineering and infrastructure teams worked with Databricks to identify and fix the underlying problem. What You Need to Do: Please rerun your pipelines this morning to pull in any data that was missed during the outage from yesterday and today. If you run into any issues or have questions, please contact us through our Meridianlink Support Portal. We apologize for the disruption and appreciate your patience as we worked towards a resolution.

Read the full incident report →

Started Sep 04, 2026, 02:36 PM UTC· resolved Sep 04, 2026, 05:19 PM UTC

1. investigating Sep 04, 2026, 02:36 PM UTC

   We have received reports that Dealertrack e-Contracting is not functioning properly. In addition, some clients have reported that decisioning updates are not being reflected in Dealertrack as expected.

2. identified Sep 04, 2026, 02:36 PM UTC

   Our team has investigated the reports and confirmed that Dealertrack has been notified of the issue. We are working with them to determine the root cause and obtain additional information regarding resolution efforts.

3. monitoring Sep 04, 2026, 02:38 PM UTC

   We will continue to monitor the situation and provide updates as additional information becomes available.

4. resolved Sep 04, 2026, 05:19 PM UTC

   Dealertrack has informed us that the issue has been resolved. As of approximately 11:30 AM EST, services should be functioning normally. Please review and let us know if you continue to experience any issues.

Read the full incident report →

Started Aug 28, 2026, 10:28 PM UTC· resolved Aug 29, 2026, 04:45 PM UTC

1. investigating Aug 28, 2026, 10:28 PM UTC

   Clients are report issues when pulling Experian Credit. You may see a 'System Unavailable' message in the credit report when attempting to view. We are investigating this and will reach out to Experian as well.

2. investigating Aug 29, 2026, 12:01 AM UTC

   Experian is currently investigating reports of credit pull issues. We will provide updates as additional information becomes available.

3. monitoring Aug 29, 2026, 12:11 AM UTC

   The errors appear to have been resolved. Please try ordering credit again.

4. resolved Aug 29, 2026, 04:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 14, 2026, 10:28 PM UTC· resolved Aug 14, 2026, 10:56 PM UTC

1. investigating Aug 14, 2026, 10:28 PM UTC

   We have received reports of Equifax OFAC error message on credit report: EQUIFAX OFAC ALERT: TRANSACTION PROCESSING ERROR - {PII} OFAC DATA SOURCE IS CURRENTLY UNAVAILABLE. Equifax has been notified about this issue.

2. monitoring Aug 14, 2026, 10:39 PM UTC

   We are beginning to see successful traffic again. We are monitoring before confirming that this issue is fully resolved.

3. resolved Aug 14, 2026, 10:56 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 14, 2026, 03:10 PM UTC· resolved Aug 14, 2026, 03:45 PM UTC

1. investigating Aug 14, 2026, 03:10 PM UTC

   We are currently investigating an issue where clients on the CS server are receiving a "Not Found" message when trying to run reports.

2. resolved Aug 14, 2026, 03:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 23, 2026, 03:44 PM UTC· resolved Jul 23, 2026, 09:14 PM UTC

1. investigating Jul 23, 2026, 03:44 PM UTC

   Clients are reporting issues with launching IMM. We are also investigating this.

2. identified Jul 23, 2026, 03:48 PM UTC

   We are actively working with our cloud provider to restore network connectivity to parts of our service.

3. identified Jul 23, 2026, 04:17 PM UTC

   We are continuing to investigate reports of IMM eSigning errors affecting Meridianlink Consumer and Opening. Our teams remain actively engaged and are working to identify the underlying cause and fully understand the scope of impact. At this time, there is no change in status, but our investigation with our cloud provider remains a high priority. We will continue to share updates as additional information becomes available.

4. identified Jul 23, 2026, 04:30 PM UTC

   Microsoft is investigating an issue affecting connectivity to Azure services for a subset of customers in the West US region. Impacted customers may experience intermittent issues when accessing Azure services. We will provide more information as it becomes available. If you want to be notified about emerging issues where you haven't yet been confirmed as an impacted customer, you can consume the RSS feed from the Azure Status Page: https://azure.status.microsoft/en-us/status

5. identified Jul 23, 2026, 05:29 PM UTC

   We're currently experiencing a service disruption caused by an issue with Microsoft's infrastructure. Microsoft has identified the potential source of the problem and is actively working to resolve it by rerouting traffic to healthy systems and monitoring recovery in real time. They will continue to evaluate the effectiveness of mitigation, assess customer impact, and investigate contributing factors, and will provide additional information as soon as it becomes available. We're staying close to Microsoft's response to bring services back to full availability as quickly as possible. We'll share updates here as new information becomes available.

6. monitoring Jul 23, 2026, 06:58 PM UTC

   Services have been restored and IMM is back up and running. We'll continue to monitor closely to ensure everything remains stable. If you're still experiencing issues, please submit a support ticket and our team will follow up promptly. Thank you for your patience.

7. resolved Jul 23, 2026, 09:14 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 23, 2026, 03:36 PM UTC· resolved Jul 23, 2026, 09:15 PM UTC

1. investigating Jul 23, 2026, 03:36 PM UTC

   Clients are reporting various issues while trying to book to core. Our teams are investigating this as well.

2. identified Jul 23, 2026, 03:47 PM UTC

   We are actively working with our cloud provider to restore network connectivity to parts of our service.

3. identified Jul 23, 2026, 04:18 PM UTC

   We are continuing to investigate reports of Core Booking errors affecting Meridianlink Consumer and Opening. Our teams remain actively engaged and are working to identify the underlying cause and fully understand the scope of impact. At this time, there is no change in status, but our investigation with our cloud provider remains a high priority. We will continue to share updates as additional information becomes available.

4. identified Jul 23, 2026, 04:30 PM UTC

   Microsoft is investigating an issue affecting connectivity to Azure services for a subset of customers in the West US region. Impacted customers may experience intermittent issues when accessing Azure services. We will provide more information as it becomes available. If you want to be notified about emerging issues where you haven't yet been confirmed as an impacted customer, you can consume the RSS feed from the Azure Status Page: https://azure.status.microsoft/en-us/status

5. identified Jul 23, 2026, 05:29 PM UTC

   We're currently experiencing a service disruption caused by an issue with Microsoft's infrastructure. Microsoft has identified the potential source of the problem and is actively working to resolve it by rerouting traffic to healthy systems and monitoring recovery in real time. They will continue to evaluate the effectiveness of mitigation, assess customer impact, and investigate contributing factors, and will provide additional information as soon as it becomes available. We're staying close to Microsoft's response to bring services back to full availability as quickly as possible. We'll share updates here as new information becomes available.

6. monitoring Jul 23, 2026, 06:45 PM UTC

   Services have been restored and Core Integration services are back up and running. We'll continue to monitor closely to ensure everything remains stable. If you're still experiencing issues, please submit a support ticket and our team will follow up promptly. Thank you for your patience.

7. resolved Jul 23, 2026, 09:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 23, 2026, 03:30 PM UTC· resolved Jul 23, 2026, 09:14 PM UTC

1. investigating Jul 23, 2026, 03:30 PM UTC

   Portal Production and Demo environments are currently down. Our team is actively investigating and will post an update within 30 minutes. We apologize for the disruption and appreciate your patience.

2. identified Jul 23, 2026, 03:47 PM UTC

   We are actively working with our cloud provider to restore network connectivity to parts of our service.

3. identified Jul 23, 2026, 04:17 PM UTC

   We are continuing to investigate reports of AppPortal loading issues affecting Meridianlink Consumer and Opening. Our teams remain actively engaged and are working to identify the underlying cause and fully understand the scope of impact. At this time, there is no change in status, but our investigation with our cloud provider remains a high priority. We will continue to share updates as additional information becomes available.

4. identified Jul 23, 2026, 04:30 PM UTC

   Microsoft is investigating an issue affecting connectivity to Azure services for a subset of customers in the West US region. Impacted customers may experience intermittent issues when accessing Azure services. We will provide more information as it becomes available. If you want to be notified about emerging issues where you haven't yet been confirmed as an impacted customer, you can consume the RSS feed from the Azure Status Page: https://azure.status.microsoft/en-us/status

5. identified Jul 23, 2026, 05:28 PM UTC

   We're currently experiencing a service disruption caused by an issue with Microsoft's infrastructure. Microsoft has identified the potential source of the problem and is actively working to resolve it by rerouting traffic to healthy systems and monitoring recovery in real time. They will continue to evaluate the effectiveness of mitigation, assess customer impact, and investigate contributing factors, and will provide additional information as soon as it becomes available. We're staying close to Microsoft's response to bring services back to full availability as quickly as possible. We'll share updates here as new information becomes available.

6. monitoring Jul 23, 2026, 06:33 PM UTC

   Services have been restored and AppPortal is back up and running. We'll continue to monitor closely to ensure everything remains stable. If you're still experiencing issues, please submit a support ticket and our team will follow up promptly. Thank you for your patience.

7. resolved Jul 23, 2026, 09:14 PM UTC

   This incident has been resolved.

Read the full incident report →