MeridianLink Outage History

The Support teams for MeridianLink Mortgage and OpenClose are experiencing phone system issues today. For assistance on Mortgage LOS and related products, please initiate a Chat or Support Case in the Resource Center. For OpenClose LOS and related products, please initiate a Support Case in the Resource Center.

MeridianLink IT is working with our support phone system provider on this issue. We hope to have a resolution soon.

A data refresh delay affecting Partner Connect vendors has been identified. Our team has investigated and deployed a solution; subsequent pipelines are running now. We apologize for any inconvenience this may have caused.

A data refresh delay affecting Partner Connect vendors has been identified. Our team is investigating and working toward resolution. We apologize for any inconvenience this may have caused.

We have identified the cause of the issue impacting fraud warning resolution. Our teams are actively working on a fix. We will continue to share updates as progress is made.

Our teams are actively working on a fix. Updated images are currently being built, after which we will deploy to testing and then move to production. We are targeting approximately 90 minutes for full restoration, barring any unexpected issues. We will continue to share updates as progress is made.

We have identified the cause of the issue impacting fraud warning resolution and intermittent latency. Our teams are actively working on a fix and are currently completing the build. Once finalized, we will proceed through testing and then deployment to production. We will continue to provide updates as progress is made.

Our development team began deploying a fix to the Shared Production servers at 12 PM PT. We’ve started with WS and SECURE, followed by CS and ES. Each cluster will take approximately 15–20 minutes. The remaining Shared Production servers will receive the fix after hours today, as only minimal impact has been reported on those environments. No downtime is expected. Users may be signed out during deployment but can simply log back in. Thank you for your patience as we work to resolve this issue.

We have identified the cause of the issue: the inability to resolve fraud warnings. Our teams are working on a resolution and taking steps to restore normal operation. [Brief mitigation or workaround, if available.] We will continue to share updates as progress.

We have identified the cause of the issue impacting fraud warning resolution. Our teams are actively working on a fix. We will continue to share updates as progress is made.

Our teams are actively working on a fix. Updated images are currently being built, after which we will deploy to testing and then move to production. We are targeting approximately 90 minutes for full restoration, barring any unexpected issues. We will continue to share updates as progress is made.

We have identified the cause of the issue impacting fraud warning resolution and intermittent latency. Our teams are actively working on a fix and are currently completing the build. Once finalized, we will proceed through testing and then deployment to production. We will continue to provide updates as progress is made.

This issue will be fixed today 5/27/26 after a hot fix deployment at 6:30pm PT.

Following a system update released on May 19, users are encountering errors when attempting to create or save drafts in the Workflow Configuration tool. The error references HMDA-related data fields (e.g., sHmdaIncome) and prevents workflow changes from being saved. Our engineering team is actively working on a targeted data correction that will update the affected workflow records to align with the new field types. This fix does not require a full software release and can be applied directly. No previously saved loan data is affected — this is limited to the workflow configuration tool. As soon as we have more information, we will update you here.

Development is working on a fix for this issue. As soon as we have more information, we will update you here.

The PriceMyLoan team has advised that the loading of rates for today for Plains Commerce Bank has been delayed. As soon as today's rates have been loaded, we will update you here.

IT have identified the issue and recovered the database. Reports that were previously requested may have encountered errors; however, the issue has been resolved. New report requests should now generate successfully.

We have identified the cause of the issue impacting MagicWrighter ACH 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. MagicWrighter confirmed an issue on their side and is currently working to resolve it. We will continue to share updates as we receive additional information.

We have identified the cause of the issue impacting the IMM RTS eSignature integration. A fix for this issue will be deployed to all shared Production environments after business hours today. We will continue to share updates as progress.

A data refresh delay affecting Partner Connect vendors has been identified. Our team is investigating and working toward resolution. We apologize for any inconvenience this may have caused.

We are continuing to work on a fix for this issue.

We have identified the cause and are rerunning subsequent pipelines. This is estimated to be completed in 4- 6 hours. We apologize for the inconvenience caused to your downstream processes.

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

Dear Clients, We are aware of the tax transcripts link not connecting to the IRS portal. We advise contacting your IRS rep to register the new Meridianlink IPs.

We are continuing to work on a fix for this issue.

Experian is currently investigating reports of consumer credit pull failures impacting multiple clients, where requests are returning a TCP SYSTEM UNAVAILABLE error. Their teams are actively reviewing service health and will provide updates on impact and restoration as soon as possible. We will continue to share updates as we receive additional information.

We are continuing to work on a fix for this issue.

Our team has identified the root cause of this morning’s data refresh delay affecting the Insight Consumer and Opening data source. We are actively deploying a fix and expect data refreshes to complete by 2:00 PM EST. We sincerely apologize for the inconvenience this may cause and appreciate your patience as we work to restore normal processing.

The Compliance Eagle credentials issue has been identified, and we are validating our solution. We will provide another update as soon as we have additional information.