MeridianLink Outage History

MeridianLink is up right now

Pingoru has recorded 122 incidents for MeridianLink: 122 in the last 12 months and 26 in the last 90 days.

Source: status.meridianlink.com

122incidents recorded
122last 12 months
26last 90 days
16 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOct7
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct19%
Pingoru began tracking MeridianLink in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202613251 of 720 (35%)
May 20261093 of 744 (13%)
June 202614244 of 720 (34%)
July 20261581 of 744 (11%)
August 2026422 of 744 (3%)
September 202615203 of 720 (28%)
October 20267115 of 590 (19%)

Incidents, newest first

Minor July 23, 2026 ML Consumer/Opening - Experian Bureau Pull Issues - Bureau is Not Available 5h 47m Consumer App Credit Reports

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

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

    Clients are reporting issues with pulling Experian, receiving 'Bureau is Not Available messages. We are investigating this. Please use a backup bureau if you have one configured.

  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:16 PM UTC

    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.

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

  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:44 PM UTC

    Services have been restored and Experian pulls 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:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 23, 2026 ML Consumer/Opening - Authorize.net Funding Errors 7h 43m Consumer App - Other Partner Integrations

Started Jul 23, 2026, 02:51 PM UTC· resolved Jul 23, 2026, 10:35 PM UTC

  1. investigating Jul 23, 2026, 02:51 PM UTC

    We are currently investigating reports of Authorize.net funding errors. Clients are reporting that they receive Failed to fund: Response is nothing when trying to process DA app funding.

  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:14 PM UTC

    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.

  4. identified Jul 23, 2026, 04:29 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, 09:25 PM UTC

    This issue has been resolved. Our engineering team identified the root cause as a validation error introduced by a recent code change, which was corrected. Functionality with Authorize.net has been fully restored. We apologize for the disruption and appreciate your patience while we worked through this.

  7. resolved Jul 23, 2026, 10:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 23, 2026 Data Connect Refresh Delay 15h 30m Data Connect Refresh Status

Started Jul 23, 2026, 03:54 AM UTC· resolved Jul 23, 2026, 07:25 PM UTC

  1. investigating Jul 23, 2026, 03:54 AM UTC

    Our team has identified a possible issue that may cause a delay in the upcoming Data Connect refresh. We are working to ensure that the data is available on time for all clients however clients taking advantage of the earlier pull time may be affected. We will provide an update as soon as possible. We sincerely apologize for the inconvenience this may cause.

  2. monitoring Jul 23, 2026, 02:52 PM UTC

    The pipeline is now connecting successfully and over 95% of our clients have refreshed data available to pull from the pipeline now. We will continue to update once everyone is able to rerun their pipelines. We sincerely apologize for the inconvenience this may cause.

  3. resolved Jul 23, 2026, 07:25 PM UTC

    The refresh is now available, please re-run your pipeline. We apologize for the inconvenience this caused to your daily processes today. Please reach out via support if you run into any issues.

Read the full incident report →

Major July 20, 2026 TazWorks: DataLink/Compass/Transunion MVR Results not Returning 3h 43m InstaScreen Partner Integrations

Started Jul 20, 2026, 04:34 PM UTC· resolved Jul 20, 2026, 08:18 PM UTC

  1. investigating Jul 20, 2026, 04:34 PM UTC

    We have reached out to DataLink/Compass/Transunion

  2. monitoring Jul 20, 2026, 07:54 PM UTC

    It appears that MVR results are returning form DataLink/Compass/TransUnion

  3. resolved Jul 20, 2026, 08:18 PM UTC

    We received confirmation from DataLink/Compass/Transunion that the issue has been fixed on their side

Read the full incident report →

Minor July 20, 2026 ML Consumer - Connection error occurs with Precise ID 1d 5h Consumer App Fraud Prevention Vendors

Started Jul 20, 2026, 01:55 PM UTC· resolved Jul 21, 2026, 07:21 PM UTC

  1. investigating Jul 20, 2026, 01:55 PM UTC

    We are currently investigating reports of errors affecting Precise ID. Our teams are actively reviewing the situation and working to better understand the scope. We will provide updates as additional information becomes available.

  2. investigating Jul 20, 2026, 03:00 PM UTC

    We are continuing to investigate reports of errors affecting Precise ID. Our teams are actively reviewing the situation and working to better understand the scope. We will provide updates as additional information becomes available.

  3. monitoring Jul 20, 2026, 03:40 PM UTC

    We have identified the cause of the issue impacting Experian Precise ID. Experian is working on a resolution and taking steps to restore normal operation. They identified an IP address and have updated their allow list.

  4. monitoring Jul 20, 2026, 08:22 PM UTC

    Experian is still investigating this on their end.

  5. resolved Jul 21, 2026, 07:21 PM UTC

    Our IT team has implemented additional firewall whitelisting for a new URL provided by Experian, which has resolved the recent connectivity issues. Action required for offsite clients: Please have your IT team open your firewall to allow communication to/from gateway.experian.com. If you continue to experience issues after making this change, please reach out to our support team.

Read the full incident report →

Major July 14, 2026 ML Consumer/Opening - DocuSign Authentication Issue 3h 58m Consumer App - Other Partner Integrations

Started Jul 14, 2026, 06:15 PM UTC· resolved Jul 14, 2026, 10:14 PM UTC

  1. identified Jul 14, 2026, 06:15 PM UTC

    Some clients are reporting issues with DocuSign's LexisNexis Authentication service. DocuSign has acknowledged an issue on LexisNexis' end with that vendor acknowledgement as well. You can view direct status updates via DocuSign here: https://status.docusign.com/

  2. monitoring Jul 14, 2026, 07:20 PM UTC

    LexisNexis has reported resolving the issue. DocuSign is continuing to monitor.

  3. monitoring Jul 14, 2026, 07:20 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jul 14, 2026, 10:14 PM UTC

    DocuSign has resolved this one their end: https://status.docusign.com/incidents/1tjv34l5z9mx

Read the full incident report →

Minor July 10, 2026 Data Connect Data Refresh Delay 9h 55m Data Connect Refresh Status

Started Jul 10, 2026, 01:35 PM UTC· resolved Jul 10, 2026, 11:31 PM UTC

  1. investigating Jul 10, 2026, 01:35 PM UTC

    Impact: Data Connect morning refresh is currently still processing for clients on both pull times. This may impact downstream processes. What's happening: The scheduled morning refresh for Data Connect is taking longer than expected and is still in progress for clients across both pull time windows. Our team is actively monitoring the pipeline and working to resolve this as quickly as possible. What we're doing: - Continuously monitoring the refresh pipeline - Investigating the root cause of the delay - Working to complete processing so clients can rerun their processes What you need to do: Please hold off on rerunning your processes until we notify you that the refresh has completed. We will provide an update as soon as clients are able to proceed. We sincerely apologize for this delay and any inconvenience it may cause to your downstream processes. We're committed to resolving this quickly and will provide a full update shortly.

  2. identified Jul 10, 2026, 08:50 PM UTC

    Our team has identified the cause of the refresh delay and are working on pushing a code change to mitigate this issue. We will continue updating once you are able to rerun your process.

  3. resolved Jul 10, 2026, 11:31 PM UTC

    The refresh is now available, clients may notice multiple extraction run dates for 7/9-710. We apologize for the inconvenience this caused to your daily processes today. Please reach out via support if you run into any issues.

Read the full incident report →

Minor July 8, 2026 Missing CREDIT_CARD_BOOKING_DATE_UTC column in DA_CC_SPECIFIC_LOAN_INFO table | Data Connect 6h 52m Data Connect Operational Status

Started Jul 08, 2026, 03:39 PM UTC· resolved Jul 08, 2026, 10:31 PM UTC

  1. investigating Jul 08, 2026, 03:39 PM UTC

    The CREDIT_CARD_BOOKING_DATE_UTC column is currently unavailable in the DA_CC_SPECIFIC_LOAN_INFO table. This may affect downstream processes and reports. Our team is investigating and will restore access as quickly as possible.

  2. monitoring Jul 08, 2026, 06:47 PM UTC

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

  3. resolved Jul 08, 2026, 10:31 PM UTC

    Missing column is now available, tomorrows refresh will bring in missing data. We apologize for the inconvenience caused! Please reach out via support for any issues.

Read the full incident report →

Notice July 2, 2026 MeridianLink Mortgage - Pipeline Display Issue 2h 4m Mortgage App LOS, Mortgage App Reporting

Started Jul 02, 2026, 04:38 PM UTC· resolved Jul 02, 2026, 06:43 PM UTC

  1. investigating Jul 02, 2026, 04:38 PM UTC

    Date Identified: July 2, 2026 Status: Under Investigation We are aware of an issue affecting Pipeline Views in Mortgage LOS where not all loan files are displaying as expected. In some cases, the Pipeline View is showing a significantly lower number of loans than what exists in the corresponding status. For example, a pipeline may display 48 loans when 173 loans should be present based on their current status. What this means for you: Loan files are not missing or lost — they remain in the system and are accessible. The issue is limited to how loans are being displayed within the Pipeline View. Our team is actively investigating the root cause and working toward a resolution. We will provide updates as more information becomes available. If you have questions or need assistance locating specific loans in the meantime, please contact your support representative.

  2. identified Jul 02, 2026, 04:41 PM UTC

    If you are experiencing this issue, the workaround is to replace Loan Progress with Loan Status in your Report Editor. Loan Progress should not be used if your operator is "equal to" - you should use Loan Status instead.

  3. monitoring Jul 02, 2026, 05:57 PM UTC

    Client Call to Action We have identified the cause of the recent Pipeline Report issue and are actively implementing a correction. What happened? A system update related to Loan Progress changed how this field functions within Custom Reports. As a result, reports that use Loan Progress as a direct comparison (Must Equal or Must Not Equal) may not return the expected loans in the pipeline. What clients need to do: Review any Custom Reports that use Loan Progress and update the criteria as follows: -- If the report uses Loan Progress = Must Equal or Must Not Equal, replace Loan Progress with Loan Status. -- Continue using Loan Progress only for range-based criteria such as: Greater Than Greater Than or Equal To Less Than Less Than or Equal To Current Status: Our Development team is running a process to update affected loan files and restore expected report results. However, clients should still update their Custom Reports to align with the intended use of the Loan Progress field, as it will no longer function as it did previously for direct comparisons. Recommended Action: Please review and update affected Custom Reports at your earliest convenience to ensure accurate Pipeline Report results moving forward.

  4. resolved Jul 02, 2026, 06:43 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 →

Notice July 2, 2026 MeridianLink PriceMyLoan - rates delayed today 3h 58m Mortgage Access, OpenClose Pricing Engine (PriceMyLoan), Mortgage App Pricing Engine (PML)

Started Jul 02, 2026, 02:00 PM UTC· resolved Jul 02, 2026, 05:58 PM UTC

  1. investigating Jul 02, 2026, 02:00 PM UTC

    PriceMyLoan is experiencing issues this morning loading today's rates. Development is working on identifying and resolving this issue. We will post updates as they become available.

  2. investigating Jul 02, 2026, 04:17 PM UTC

    There is no change to report at this time regarding the issue affecting PriceMyLoan. Investigation efforts remain ongoing, and our teams continue to actively work toward identifying the cause. We will continue to share updates on a regular cadence, even if no additional information is available. We understand the impact this may have and appreciate your continued patience as we work toward resolution.

  3. monitoring Jul 02, 2026, 04:26 PM UTC

    A fix has been implemented for the issue affecting PriceMyLoan and we are actively monitoring the environment to ensure stability. At this time, services are operating normally. We will continue monitoring and provide confirmation once the incident is fully resolved.

  4. resolved Jul 02, 2026, 05:58 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 →

Minor June 26, 2026 Data Connect da_cc_specific_loan_info table not refreshed 5h 50m Data Connect Refresh Status

Started Jun 26, 2026, 05:50 PM UTC· resolved Jun 26, 2026, 11:41 PM UTC

  1. identified Jun 26, 2026, 05:50 PM UTC

    We have identified an issue affecting the da_cc_specific_loan_info table where data is not refreshing as expected. Our engineering team is actively working on a fix and we will provide an update once refreshed data is confirmed available. We appreciate your patience and apologize for any impact this may have on your downstream processes.

  2. monitoring Jun 26, 2026, 09:07 PM UTC

    A fix has been deployed for the da_cc_specific_loan_info table and a full table reload is currently in progress for all clients. This reload ensures that no data is missing from your environment as a result of this issue. The reloaded data is expected to be available in approximately 3 hours. No action is required on your end. If you would like to re-run your process once the table reload is complete you may do so, or you can pull the data as normal in tomorrow's extraction. We appreciate your patience and apologize for any inconvenience this may have caused.

  3. resolved Jun 26, 2026, 11:41 PM UTC

    The full table reload for da_cc_specific_loan_info is now complete and data is available for all clients. If you have not already re-run your process, you may do so now or continue to pull data as normal in tomorrow's extraction. Thank you for your patience.

Read the full incident report →

Minor June 23, 2026 Encrypted SSN Values Displayed in Partner Connect Tables 14m Partner Connect Operational Status

Started Jun 23, 2026, 08:35 PM UTC· resolved Jun 23, 2026, 08:49 PM UTC

  1. identified Jun 23, 2026, 08:35 PM UTC

    Summary: We are aware of an issue where some clients are seeing encrypted SSN values in various Partner Connect tables instead of the expected decrypted values. Our engineering team is actively investigating and working to restore normal behavior.

  2. resolved Jun 23, 2026, 08:49 PM UTC

    Partner Connect vendors are now able to see decrypted SSNs in the pipeline.

Read the full incident report →

Minor June 22, 2026 Encrypted SSN Values Displayed in Data Connect and Partner Connect Tables 1d 5h Data Connect Operational Status, Partner Connect Operational Status

Started Jun 22, 2026, 03:00 PM UTC· resolved Jun 23, 2026, 08:31 PM UTC

  1. investigating Jun 22, 2026, 03:00 PM UTC

    Summary: We are aware of an issue where some clients are seeing encrypted SSN values in various Data Connect and Partner Connect tables instead of the expected decrypted values. Our engineering team is actively investigating and working to restore normal behavior. Impact: Clients accessing SSN fields via Data Connect and Partner Connect may see encrypted values rather than decrypted values. Current Status: Our development team has identified the issue and is actively working on a resolution. We will provide updates as progress is made.

  2. identified Jun 22, 2026, 05:59 PM UTC

    Data Connect clients can now rerun their pipelines to pull in decrypted SSNs. Our team is now working to implement a fix for Partner Connect.

  3. resolved Jun 23, 2026, 08:31 PM UTC

    Partner Connect vendors are now able to see decrypted SSNs in the pipeline.

Read the full incident report →

Critical June 19, 2026 Problems with Experian credit reports 33m DecisionLender4 Partner Integrations

Started Jun 19, 2026, 03:48 PM UTC· resolved Jun 19, 2026, 04:22 PM UTC

  1. investigating Jun 19, 2026, 03:48 PM UTC

    We are currently working with Experian to investigate and resolve this issue. Impact: All new credit requests submitted today (06/19/2026) are returning a “CreditReport is empty” message.

  2. identified Jun 19, 2026, 03:50 PM UTC

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

  3. resolved Jun 19, 2026, 04:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 18, 2026 ML Consumer/Opening Insight - Data Refresh Delay 2h 58m Data Refresh, Insight for Consumer and Opening

Started Jun 18, 2026, 12:43 PM UTC· resolved Jun 18, 2026, 03:42 PM UTC

  1. investigating Jun 18, 2026, 12:43 PM UTC

    We are experiencing a temporary data refresh delay. The technical team is actively working on the issue and we will share an update as soon as it’s resolved. Affected Data Source: Insight Consumer and Opening

  2. resolved Jun 18, 2026, 03:42 PM UTC

    The issue affecting Insight data refresh 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 →

Notice June 11, 2026 MeridianLink Mortgage and OpenClose Support Phone System Issues 3h 49m OpenClose, Mortgage App LOS

Started Jun 11, 2026, 02:50 PM UTC· resolved Jun 11, 2026, 06:39 PM UTC

  1. identified Jun 11, 2026, 02:50 PM UTC

    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.

  2. identified Jun 11, 2026, 04:32 PM UTC

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

  3. resolved Jun 11, 2026, 06:39 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 →

Minor June 9, 2026 DecisionLender – Duplicate Applications with RouteOne 1d 22h DecisionLender4 Partner Integrations

Started Jun 09, 2026, 05:53 PM UTC· resolved Jun 11, 2026, 04:11 PM UTC

  1. investigating Jun 09, 2026, 05:53 PM UTC

    We are currently receiving reports of duplicate applications being created in DL4 via RouteOne. RouteOne is actively working with them to investigate and address the issue, if it is still occurring.

  2. monitoring Jun 11, 2026, 12:28 AM UTC

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

  3. resolved Jun 11, 2026, 04:11 PM UTC

    There shouldn’t be any further issues. We will also continue to monitor for any further occurrences and keep you informed of progress.

Read the full incident report →

Notice June 5, 2026 PriceMyLoan - rates for Paramount Residential Mortgage are delayed 2h 25m Mortgage Access, OpenClose Pricing Engine (PriceMyLoan), Mortgage App Pricing Engine (PML)

Started Jun 05, 2026, 06:08 PM UTC· resolved Jun 05, 2026, 08:33 PM UTC

  1. investigating Jun 05, 2026, 06:08 PM UTC

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

  2. resolved Jun 05, 2026, 08:33 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 →

Minor June 5, 2026 ML Community - Unauthorized Request error. 7d 2h Consumer App - Other Partner Integrations

Started Jun 05, 2026, 02:56 PM UTC· resolved Jun 12, 2026, 05:11 PM UTC

  1. investigating Jun 05, 2026, 02:56 PM UTC

    We are currently investigating reports of an "Unauthorized Request Error" when attempting to access the MeridianLink Community. Our teams are actively reviewing the situation and working to better understand the scope. We will provide updates as additional information becomes available.

  2. investigating Jun 05, 2026, 04:12 PM UTC

    We are continuing to investigate reports of an "Unauthorized Request Error" when attempting to access the MeridianLink Community. 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 are ongoing and a high priority. We will continue to share updates as additional information becomes available.

  3. investigating Jun 05, 2026, 05:28 PM UTC

    We are continuing to investigate reports of an "Unauthorized Request Error" when attempting to access the MeridianLink Community. We are working with the vendor for the Community, and it has been escalated on their end. 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 are ongoing and a high priority. We will continue to share updates as additional information becomes available.

  4. investigating Jun 08, 2026, 12:46 PM UTC

    We are currently investigating reports of an "Unauthorized Request Error" when attempting to access the MeridianLink Community with the Vendor. Our teams are actively reviewing the situation and working to better understand the scope. We will provide updates as additional information becomes available.

  5. investigating Jun 08, 2026, 02:52 PM UTC

    We are currently investigating reports of an “Unauthorized Request” error when accessing the MeridianLink Community. We are actively working with our vendor to identify the root cause. Workaround: In the meantime, users can bypass SSO and access the Community directly using: https://connect.meridianlink.com/entry/password If a user does not already have a password set, they can select “Forgot Password” to create or reset it using the same email address associated with their product account. Our teams are actively working to understand the scope and impact of this issue. We will continue to share updates as more information becomes available.

  6. identified Jun 09, 2026, 11:02 PM UTC

    We have identified the cause of the login issue impacting access to the ML Community. The issue has been traced to a recent change made by our vendor (Vanilla) affecting the SSO redirect behavior. The vendor is actively working on a fix and will provide further updates as progress is made. In the meantime, users can continue to access the Community by using the direct login workaround: https://connect.meridianlink.com/entry/password. We will share additional updates as soon as more information becomes available.

  7. identified Jun 11, 2026, 10:15 PM UTC

    We have identified the cause of the login issue impacting access to the ML Community. The issue has been traced to a recent change made by our vendor (Vanilla) affecting the SSO redirect behavior. The vendor is actively working on a fix and will provide further updates as progress is made. In the meantime, users can continue to access the Community by using the direct login workaround: https://connect.meridianlink.com/entry/password Temporary Workaround Update: - If a user does not already have a password set, they can select “Forgot Password” to create or reset it using the same email address associated with their product account. - After logging in, users will land on the Mortgage Community page, which may appear blank due to permission settings. - To access the Consumer Community, click the globe icon in the top-right corner and select the appropriate community. We will share additional updates as soon as more information becomes available.

  8. resolved Jun 12, 2026, 05:11 PM UTC

    Vanilla has resolved the issue. All Consumer environments have been successfully tested and are now working as expected.

Read the full incident report →

Minor June 3, 2026 Partner Connect - Data Refresh Delay 23h 50m Partner Connect Data Refresh

Started Jun 03, 2026, 08:48 PM UTC· resolved Jun 04, 2026, 08:39 PM UTC

  1. identified Jun 03, 2026, 08:48 PM UTC

    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.

  2. resolved Jun 04, 2026, 08:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 28, 2026 ML Consumer/Opening: Latency on the Shared Production Servers 1d 2h Consumer App Operational Status

Started May 28, 2026, 12:59 PM UTC· resolved May 29, 2026, 03:00 PM UTC

  1. investigating May 28, 2026, 12:59 PM UTC

    We are currently investigating reports of latency affecting production servers. Our teams are actively reviewing the situation and working to better understand the scope. We will provide updates as additional information becomes available. Next update: as soon as we have more details

  2. investigating May 28, 2026, 01:47 PM UTC

    We are continuing to investigate reports of server latency affecting production. 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 are ongoing and a high priority. We will continue to share updates as additional information becomes available.

  3. identified May 28, 2026, 03:30 PM UTC

    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.

  4. identified May 28, 2026, 04:11 PM UTC

    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.

  5. identified May 28, 2026, 05:32 PM UTC

    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.

  6. identified May 28, 2026, 07:03 PM UTC

    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.

  7. monitoring May 28, 2026, 08:14 PM UTC

    The fix has been deployed. Please confirm if performance has returned to normal for your users. If you have an open case, send us an update.

  8. resolved May 29, 2026, 03:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 28, 2026 ML Consumer/Opening: Shared Production - Missing Resolve Fraud Option for IVL Apps 1d 2h Consumer App Fraud Prevention Vendors

Started May 28, 2026, 12:52 PM UTC· resolved May 29, 2026, 03:00 PM UTC

  1. investigating May 28, 2026, 12:52 PM UTC

    We are currently investigating reports of being unable to resolve fraud warnings affecting ML Consumer IVL loans. Our teams are actively reviewing the situation and working to better understand the scope. We will provide updates as additional information becomes available. Next update: as soon as we have more details

  2. identified May 28, 2026, 01:44 PM UTC

    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.

  3. identified May 28, 2026, 02:57 PM UTC

    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.

  4. identified May 28, 2026, 04:11 PM UTC

    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.

  5. identified May 28, 2026, 05:32 PM UTC

    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.

  6. monitoring May 28, 2026, 08:46 PM UTC

    We are deploying a fix tonight across all shared production environments for the Missing Resolve Fraud option in IVL apps. Maintenance is scheduled to begin at 7 PM PT, with each environment expected to be down for approximately 30–40 minutes. CS will begin at 8 PM PT. Secure, HS, and WS environments will begin at 9 PM PT.

  7. monitoring May 29, 2026, 12:29 PM UTC

    The fix deployment was completed. We are following up to confirm that the missing Resolve Fraud option is now working as expected. If you have an open case with Support, please add a comment to confirm the issue has been resolved on your end.

  8. resolved May 29, 2026, 03:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 27, 2026 Mortgage Access - clients reporting spouse data removed upon loan submission 19h 12m Mortgage Access

Started May 27, 2026, 07:39 PM UTC· resolved May 28, 2026, 02:52 PM UTC

  1. investigating May 27, 2026, 07:39 PM UTC

    We are currently investigating this issue for Mortgage Access POS.

  2. identified May 27, 2026, 11:22 PM UTC

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

  3. resolved May 28, 2026, 02:52 PM UTC

    This issue has been resolved.

Read the full incident report →

Major May 26, 2026 TazInsights is current down 2h 46m InstaScreen Partner Integrations

Started May 26, 2026, 05:41 PM UTC· resolved May 26, 2026, 08:27 PM UTC

  1. investigating May 26, 2026, 05:41 PM UTC

    We have contacted Sisense (vendor) to troubleshoot the outage

  2. resolved May 26, 2026, 08:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 20, 2026 MeridianLink Mortgage - Error When Saving Workflow Drafts 22h 34m Mortgage App LOS

Started May 20, 2026, 06:09 PM UTC· resolved May 21, 2026, 04:43 PM UTC

  1. identified May 20, 2026, 06:09 PM UTC

    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.

  2. identified May 21, 2026, 10:08 AM UTC

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

  3. resolved May 21, 2026, 04:43 PM UTC

    This issue was resolved with a hot fix the night of 5/20/26.

Read the full incident report →