MeridianLink Statuspage

All Systems Operational

About This Site

This Statuspage provides the status of MeridianLink's products.
Customers may click "Subscribe to Updates" and select specific Product Components to receive email notifications if there is a service disruption.

MeridianLink Consumer / MeridianLink Opening ? Operational
Consumer App Operational Status Operational
Consumer App Credit Reports Operational
Consumer App Fraud Prevention Vendors Operational
Consumer App Indirect Auto Integrations Operational
Consumer App Vehicle Valuation Operational
Consumer App Underwriting & Pricing Engine Operational
Consumer App - Other Partner Integrations Operational
Consumer App Core Integration Operational
Consumer App Documents Operational
Consumer App Reports Operational
MeridianLink Mortgage Operational
Mortgage App LOS Operational
Mortgage App EDocs Operational
Mortgage App Pricing Engine (PML) Operational
Mortgage App Integrations Operational
Mortgage App Reporting ? Operational
Mortgage App TPO Portal Operational
MeridianLink Mortgage Credit Link Operational
Mortgage Credit Link App Operational Status Operational
Mortgage Credit Link Credit Integrations Operational
Mortgage Credit Link Additional Product Integrations Operational
MeridianLink Collect Operational
Collect App Operational Status Operational
Collect App Internal Integrations ? Operational
Collect App External Integrations ? Operational
MeridianLink Portal Operational
Portal App Operational Status Operational
Portal App Credit Reports Operational
Portal App Fraud Prevention Vendors Operational
Portal App eSign Operational
Portal App Underwriting & Pricing Engine Operational
Portal App - Other Partner Integrations Operational
Portal App Core Integration Operational
Portal App Portal Manager Operational
Portal App SSO Operational
Portal App Documents Operational
MeridianLink DecisionLender Operational
DecisionLender4 App Operational Status Operational
DecisionLender4 Reporting DBS Operational
DecisionLender4 Partner Integrations Operational
DecisionLender3.5 App Operational Status Operational
DecisionLender3.5 Reporting DBS Operational
DecisionLender3.5 Partner Integrations Operational
MeridianLink Engage Operational
Engage App Operational Status Operational
MeridianLink Insight Operational
Insight Operational Status Operational
Data Refresh Operational
TazWorks Operational
InstaScreen Operational Status Operational
InstaScreen Partner Integrations Operational
QuickApp Pro/QuickLease Pro Operational Status Operational
Trade House Data Searches Operational
MeridianLink Business Operational
Atlas Platform Operational
Credit Card Application Operational
Business Lending Application ? Operational
Offer and Closing Operational
Cloudflare Cloudflare Workers Operational
Cloudflare CDN/Cache Operational
MeridianLink Mortgage OpenClose/Optics/CAW Operational
OpenClose Operational
OpenClose Pricing Engine (DecisionAssist) Operational
Mortgage Optics Operational
ConsumerAssist Web Operational
MeridianLink Mortgage Access Operational
Mortgage Access Operational
MeridianLink ACTion Operational
ACTion App Operational Status Operational
ACTion Reporting DBS Operational
ACTion Third Party integrations Operational
MeridianLink Access Operational
Access Operational Status Operational
Partner Integrations Operational
General Operational
Global Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Oct 28, 2025

No incidents reported today.

Oct 27, 2025

No incidents reported.

Oct 26, 2025
Completed - The scheduled maintenance has been completed.
Oct 26, 23:00 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 26, 19:00 PDT
Scheduled - We will be performing system maintenance to resolve known issues on all shared production server environments - after business hours. This maintenance is scheduled for 7 pm (PT). During this time, each environment will be down for approximately 30-40 minutes. Note: CS will begin at 8PM (PT), the Secure, HS and WS server maintenance will start at 9 pm (PT).
Oct 24, 11:46 PDT
Oct 25, 2025
Resolved - This incident has been resolved.
Oct 25, 05:41 PDT
Identified - To address the widget sorting issue, the team is actively collaborating with Sisense to implement a resolution.

Planned Action:
A system upgrade is scheduled for today at 5:30 PM PT to deploy the necessary updates and improvements. During this maintenance window, the platform will be temporarily unavailable for approximately 5 hours while we complete the upgrade.

User Impact:
Users may notice that the Insight Platform will be down during this time.

Next Steps:
We will provide a final update once the maintenance is complete and full functionality has been restored.

Oct 24, 10:32 PDT
Investigating - Description:
Users are experiencing errors when attempting to use the sort function within dashboard widgets. The issue appears to occur across multiple dashboards and may impact data visualization or rendering.

Impact:
Sorting within affected widgets causes display errors or prevents the widget from loading correctly, potentially disrupting user access to accurate, ordered data.

Possible Cause:
Preliminary investigation indicates that the issue is related to the widget’s sorting functionality, which may be conflicting with underlying data configurations or query parameters. Our team is actively working to get this resolved.

Proposed Fix / Workaround:
As a temporary workaround, removing the sort option from affected dashboards may prevent the error and allow widgets to load as expected.

Oct 21, 12:15 PDT
Oct 24, 2025
Completed - The scheduled maintenance has been completed.
Oct 24, 02:00 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 23, 19:00 PDT
Scheduled - We will be performing system maintenance on EPL and Dedicated production environments - after business hours. This is to install the MS security patch for the current month.

This maintenance is scheduled to begin at 7 pm (PT) for east coast environments. For other environments we will proceed with the update after COB for that timezone. During this time, each environment will be down for approximately 30-40 minutes.

Oct 13, 09:06 PDT
Oct 23, 2025
Oct 22, 2025

No incidents reported.

Oct 21, 2025
Resolved - This incident has been resolved.
Oct 21, 11:26 PDT
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 21, 10:39 PDT
Identified - The issue has been identified and rate sheets are getting processed.
Oct 21, 10:19 PDT
Update - We are continuing to investigate this issue.
Oct 21, 10:12 PDT
Investigating - Clients may be experiencing delays in rate sheet updates. We are aware of this issue and are actively investigating. This situation is being closely monitored and we will provide updates within the next 60 min or as the situation warrants.
Oct 21, 09:59 PDT
Oct 20, 2025
Resolved - Socure has provided the following update:

We’re pleased to share that all Socure services have now fully recovered and are operating normally. We are currently serving 100% of traffic without any issues, and all system latencies and performance metrics have returned to expected levels.

Our engineering and operations teams will continue to work closely with AWS to conduct a comprehensive root cause analysis (RCA) of the incident. We will share the RCA publicly within the next few days once this review is complete.

We appreciate your patience and understanding throughout this event and thank you for your continued trust in Socure.

Oct 20, 16:06 PDT
Update - Socure has provided the following update:

We are pleased to report continued progress in restoring full service availability. All Socure services are currently operating at over 99% availability, and latency has returned to normal processing levels across our platform.

Our DocV service and other critical systems are performing well and have stabilized following earlier AWS-related disruptions. While operations have largely normalized, we are continuing to work diligently to increase availability to a full 100% and ensure sustained performance consistency.

Our teams remain in close coordination with AWS as they complete their recovery efforts and continue to monitor all systems closely to ensure optimal reliability.

We appreciate your patience and partnership throughout this incident and will provide a final update once all services have been fully restored to 100% operational status.

Oct 20, 16:00 PDT
Update - Socure has provided the following update:

We continue to work closely with AWS as their service recovery progresses and are seeing significant improvements across all Socure services. Overall system availability and performance have continued to improve steadily throughout the day.

At this time, we have successfully restored 99% of all traffic, and latencies across our services continue to improve. Our systems are stable, and our teams are actively monitoring performance to ensure continued reliability and responsiveness.

Our DocV service has also shown strong recovery and should now be mostly restored, with only minimal residual impact observed. While AWS Secrets Manager and Security Token Service (STS) continue to experience intermittent networking issues on the AWS side, these are no longer materially affecting our operations.

We will continue to monitor system performance closely and work with AWS to validate complete recovery.
Thank you for your continued patience and understanding throughout this incident. We remain committed to ensuring full stability and optimal performance across all Socure services.

Oct 20, 14:38 PDT
Update - Socure has provided the following update:

We continue to work closely with AWS to address the issues impacting system performance. AWS has reported that approximately 97 of their services remain impacted, though they are showing steady signs of recovery across multiple regions.

We are now seeing improved service availability across all Socure services, with overall traffic and response rates continuing to stabilize. Our systems remain performant, and our engineering teams are closely monitoring service health to ensure consistent reliability and full recovery.

Our DocV service continues to experience some authentication failures, primarily due to ongoing issues within AWS Secrets Manager and AWS Security Token Service (STS). While the underlying AWS services are now functional, they continue to be affected by networking issues on the AWS side, intermittently impacting authentication and credential access. These issues are gradually dissipating as AWS continues to recover.

To further mitigate impact, we have implemented targeted workarounds, including bypassing certain problematic AWS services that previously caused HMAC authentication failures, which has helped improve stability and reduce errors.

AWS continues to make steady progress toward full restoration across their infrastructure, and we are actively validating improvements in real time.

We appreciate your continued patience and understanding as AWS completes its recovery. Our teams remain fully engaged and are treating this matter with the highest urgency to ensure all Socure services return to full operational stability.

Oct 20, 14:00 PDT
Update - Socure has provided the following update:

We continue to work closely with AWS to address the underlying issues impacting system performance. AWS has reported that over 105 of their services remain affected, extending beyond EC2, Lambda, and other core infrastructure components. These widespread disruptions have contributed to intermittent service degradation across multiple AWS regions.
Despite these challenges, we have made significant progress and have successfully restored service availability to approximately 97% of all traffic. Our systems are stable, and our engineering teams continue to closely monitor performance while implementing targeted mitigations.
With AWS’s support, we have allocated the necessary GPU resources in the US-EAST-2 region to support our DocV service. However, DocV remains partially degraded due to ongoing issues with AWS Secrets Manager and AWS Security Token Service (STS), both of which continue to affect authentication and credential access.
To reduce the remaining impact, our teams have implemented additional mitigations, bypassing certain problematic AWS services that were causing HMAC authentication failures. These measures are resulting in steady improvements to DocV performance and overall system stability.
AWS has communicated that they expect most affected services to be fully restored within the next hour, and we are beginning to see continued signs of recovery across our platform. We remain in constant contact with AWS to validate progress and ensure all services return to full operational status as quickly as possible.
We understand how critical reliability is for our customers and continue to treat this issue with the highest priority. We will provide further updates as AWS confirms full recovery.

Oct 20, 12:41 PDT
Update - Socure has provided the following update:

We continue to work closely with AWS to address the underlying issues impacting system performance. AWS has reported that over 105 of their services are currently impacted, extending beyond EC2, Lambda, and other previously affected components. These disruptions are contributing to intermittent service degradations across multiple AWS regions.
Despite these challenges, we have made substantial progress and have successfully restored service availability to approximately 97% of all traffic. Our systems remain stable, and our teams continue to monitor performance and optimize recovery efforts.
With AWS’s support, we were able to allocate the necessary GPU resources in the US-EAST-2 region to support our DocV service. However, DocV remains partially degraded due to ongoing issues within AWS Secrets Manager and AWS Security Token Service (STS), both of which are critical for authentication and secure access to service credentials. These dependencies are continuing to affect DocV’s ability to fully recover.
AWS has informed us that they expect most affected services to return to full availability within the next two hours. We are in constant communication with their engineering teams to validate recovery progress and expedite the full restoration of all impacted Socure services.
We understand the importance of reliability and uptime for our customers and are treating this situation with the highest urgency. We will continue to provide timely updates as AWS progresses toward complete service restoration.

Oct 20, 12:04 PDT
Update - Socure has provided the following update:

We are actively working in close partnership with AWS to address the underlying issues currently impacting system performance. At this time, approximately 79 AWS services remain in a degraded state. The primary cause stems from issues within AWS’s Identity and Access Management (IAM), Security Token Service (STS), and Secrets Manager — all of which are critical dependencies for secure authentication and service operations.
We have made substantial progress and have now successfully restored service availability to approximately 97% of all traffic. Our teams continue to monitor performance and stability closely while working toward full recovery.
Our DocV service remains partially degraded due to GPU instance availability limitations in the US-EAST-2 region, which are required to support document verification workloads. We are working closely with AWS engineers to secure additional GPU capacity and resolve the issue as quickly as possible.
AWS has also reported that several customers are experiencing similar challenges in US-EAST-2, where EC2, Lambda, and other core services are being throttled. These broader regional limitations continue to affect our ability to perform a full failover to our disaster recovery (DR) region.
We remain in constant communication with AWS and are treating this matter with the highest urgency. Our teams are committed to achieving full service restoration as quickly as possible and will continue to share updates as more information becomes available.

Oct 20, 10:13 PDT
Update - Socure has provided the following update:

We are actively working in close partnership with AWS to address the underlying issues currently impacting system performance. At this time, approximately 79 AWS services remain in a degraded state. The primary cause stems from issues within AWS’s Identity and Access Management (IAM), Security Token Service (STS), and Secrets Manager — all of which are critical dependencies for secure authentication and service operations.
Despite these challenges, we have made significant progress and have successfully restored service availability to approximately 90% of overall traffic. Our engineering teams continue to optimize and stabilize affected components to further improve performance and reliability.
Our AWS support team has informed us that several other customers are also experiencing difficulties switching over to the US-EAST-2 region, as EC2, Lambda, and several other services are currently being throttled in that region. These limitations are contributing to our inability to perform a full failover to our disaster recovery (DR) region at this time.
We remain in continuous communication with AWS engineers and are collaborating closely to expedite resolution and achieve full service restoration as quickly as possible. We understand the critical importance of reliability for our customers and are treating this issue with the highest urgency. We will continue to provide timely updates as more information becomes available from AWS.

Oct 20, 09:37 PDT
Update - Socure has provided the following update:

We are actively working in close partnership with AWS to address the underlying issues currently impacting system performance. At this time, approximately 79 AWS services remain in a degraded state. The primary cause stems from issues within AWS’s Identity and Access Management (IAM), Security Token Service (STS), and Secrets Manager — all of which are critical dependencies for secure authentication and service operations.
Despite these challenges, we have made significant progress and have successfully restored service availability to approximately 90% of overall traffic. Our engineering teams continue to optimize and stabilize affected components to further improve performance and reliability.
Due to the ongoing AWS service disruptions, we are still unable to perform a complete failover to our disaster recovery (DR) region. However, we remain in continuous communication with AWS engineers and are collaborating closely to expedite resolution and full restoration of normal operations.
We understand how important consistent reliability is for our customers, and we are treating this as our top priority. We will continue to provide timely updates as additional information becomes available from AWS.

Oct 20, 08:54 PDT
Identified - Clients are reporting issues when trying to pull Socure reports.

Socure has acknowledged this problem with the following statement:
Impact: Service availability remains around 65%, with intermittent failures and increased latency across several components.
We continue to see service instability as the AWS outage persists. AWS has reported a global IAM service issue, which is currently preventing us from executing certain recovery and failover actions — including initiating a full disaster recovery (DR) transition.
The failures are not isolated to specific servers or paths, and we are observing unpredictable request behavior originating from AWS’s infrastructure. Our team remains actively engaged and is monitoring system performance closely while coordinating with AWS to restore full availability.

MeridianLink will provide updates when they're received from Socure directly.

Oct 20, 08:19 PDT
Resolved - The latest update on the AWS status page:

[RESOLVED] Increased Error Rates and Latencies
Oct 20 3:53 PM PDT Between 11:49 PM PDT on October 19 and 2:24 AM PDT on October 20, we experienced increased error rates and latencies for AWS Services in the US-EAST-1 Region. Additionally, services or features that rely on US-EAST-1 endpoints such as IAM and DynamoDB Global Tables also experienced issues during this time. At 12:26 AM on October 20, we identified the trigger of the event as DNS resolution issues for the regional DynamoDB service endpoints. After resolving the DynamoDB DNS issue at 2:24 AM, services began recovering but we had a subsequent impairment in the internal subsystem of EC2 that is responsible for launching EC2 instances due its dependency on DynamoDB. As we continued to work through EC2 instance launch impairments, Network Load Balancer health checks also became impaired, resulting in network connectivity issues in multiple services such as Lambda, DynamoDB, and CloudWatch. We recovered the Network Load Balancer health checks at 9:38 AM. As part of the recovery effort, we temporarily throttled some operations such as EC2 instance launches, processing of SQS queues via Lambda Event Source Mappings, and asynchronous Lambda invocations. Over time we reduced throttling of operations and worked in parallel to resolve network connectivity issues until the services fully recovered. By 3:01 PM, all AWS services returned to normal operations. Some services such as AWS Config, Redshift, and Connect continue to have a backlog of messages that they will finish processing over the next few hours. We will share a detailed AWS post-event summary.

Oct 20, 16:04 PDT
Monitoring - The latest update on the AWS status page:

Oct 20 2:48 PM PDT We have restored EC2 instance launch throttles to pre-event levels and EC2 launch failures have recovered across all Availability Zones in the US-EAST-1 Regions. AWS services which rely on EC2 instance launches such as Redshift are working through their backlog of EC2 instance launches successfully and we anticipate full recovery of the backlog over the next two hours. We can confirm that Connect is handling new voice and chat sessions normally. There is a backlog of analytics and reporting data that we must process and anticipate that we will have worked through the backlog over the next two hours.

MeridianLink will continue monitoring the situation but most third party services that relied on AWS should be restored.

Oct 20, 15:03 PDT
Update - The latest update on the AWS status page is:

Oct 20 1:52 PM PDT We have continued to reduce throttles for EC2 instance launches in the US-EAST-1 Region and we continue to make progress toward pre-event levels in all Availability Zones (AZs). AWS services such as ECS and Glue, which rely on EC2 instance launches will recover as the successful instance launch rate improves. We see full recovery for Lambda invocations and are working through the backlog of queued events which we expect to be full processed in approximately in the next two hours.

Oct 20, 14:02 PDT
Update - The latest update on the AWS status page is:
Oct 20 12:15 PM PDT We continue to observe recovery across all AWS services, and instance launches are succeeding across multiple Availability Zones in the US-EAST-1 Regions.

We will continue monitoring their status page as well as the effected vendors.

Oct 20, 12:48 PDT
Identified - If you'd like to monitor the situation directly, you can do so via https://health.aws.amazon.com/health/status
Oct 20, 10:49 PDT
Investigating - We are monitoring other services disrupted by the AWS outage.
Those services are not limited to the following:
Zest
Experian Crosscore
JD Power

Oct 20, 09:24 PDT
Resolved - Based on the AWS status here https://health.aws.amazon.com/health/status we are marking this incident as Resolved.
Oct 20, 14:39 PDT
Identified - AWS is still reporting service issues causing degraded performance. To check on AWS status visit https://health.aws.amazon.com/health/status
Oct 20, 11:55 PDT
Investigating - Mortgage Access POS uses AWS (Amazon Web Services). AWS reported a partial global outage this morning. As a result, Mortgage Access users may experience degraded performance depending on their geographical location. Users can confirm this via a site such as https://downdetector.com/status/aws-amazon-web-services/
Oct 20, 10:24 PDT
Resolved - This incident has been resolved. Reports should be functioning normally now.
Oct 20, 13:29 PDT
Identified - We’re currently experiencing a temporary issue with the Reporting feature in the DecisionLender platform due to an AWS outage. To help minimize delays once service is restored, we kindly ask that clients pause any new report attempts for now, as they may contribute to a growing backlog.
Our team is actively monitoring the situation, and we’ll continue to share updates as they become available. Thank you for your patience and understanding.

Oct 20, 08:34 PDT
Oct 19, 2025

No incidents reported.

Oct 18, 2025

No incidents reported.

Oct 17, 2025

No incidents reported.

Oct 16, 2025

No incidents reported.

Oct 15, 2025
Completed - The scheduled maintenance has been completed.
Oct 15, 23:00 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 15, 19:00 PDT
Scheduled - We will be performing system maintenance on all shared production server environments - after business hours. This maintenance is scheduled for 7 pm (PT). During this time, each environment will be down for approximately 30-40 minutes. Note: CS will begin at 8PM (PT), the Secure, HS and WS server maintenance will start at 9 pm (PT).
Oct 13, 09:06 PDT
Resolved - Reports are now running as expected.
Oct 15, 09:40 PDT
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 15, 08:44 PDT
Identified - The issue has been identified and a fix is being implemented.
Oct 15, 08:17 PDT
Investigating - Customers are reporting that they're seeing a NOT FOUND under the Status for Custom & Standard Reports. We are investigating this.
Oct 15, 07:56 PDT
Oct 14, 2025

No incidents reported.