MeridianLink Outage History

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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

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.

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

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.

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

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.

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

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.

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

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.

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

We are continuing to investigate reports of 'Bureau is Not Available' messages from Experian 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.

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 Please continue to use a backup bureau if you have one configured.

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.

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

We are continuing to investigate reports of Authorize.net Funding Errors affecting Meridianlink 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 investigation efforts with our cloud provider remain a high priority. We will continue to share updates as additional information becomes available.

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

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.