Is Blend down?

We're investigating elevated error rates on Blend's external API (api.blendlabs.com). Some API requests from partner and vendor integrations are failing or completing only after retries and delays. This may impact integration-driven workflows, including document generation and loan exports to your LOS. The core Blend application is operating normally. Our engineering team is actively investigating and we'll post an update as soon as we have more information.

We've narrowed the issue to a subset of Blend-managed integration connectors. Affected customers may experience failures in loan imports, document generation, disclosure delivery, and closing workflows that depend on these integrations. Most integrations and all core Blend application functionality are operating normally. Our engineering team is working to mitigate the failures and restore the service.

We've identified the cause of errors affecting a subset of Blend-managed integration connectors. Affected customers may experience failures in loan data exports, document transfer between Blend and the LOS, and inbound LOS event delivery that updates records in Blend. Core Blend application functionality and the majority of integrations remain unaffected. Our engineering team is actively working on remediation.

We identified and reverted a configuration change that was causing request failures for a subset of Blend-managed integration connectors. All connectors are now processing normally, and core Blend application functionality was unaffected throughout. We are reviewing any events that were impacted during this window and will retry those as needed. If you have questions about specific transactions, please reach out to your Blend contact.

We are currently experiencing connectivity issues affecting the integration between TotalExpert and Blend. TotalExpert's webhook endpoint is currently returning a 503 "Service Temporarily Unavailable" response when Blend attempts to deliver webhook events. We apologize for any inconvenience this may cause and will provide further updates as new information becomes available.

We are seeing signs of recovering. Our team is currently monitoring the stability of the integration between TotalExpert and Blend and we have not seen event failures for the past 60 mins. We will provide further updates as new information becomes available.

We're continuing to see improvement in the integration between TotalExpert and Blend and remain in close contact with TotalExpert as we work toward a full resolution. We will provide a further update as new information becomes available.

We're continuing to monitor the integration between TotalExpert and Blend. Our teams remain in close contact and are reviewing additional data together as part of the ongoing investigation. Clients are encouraged to also monitor TotalExpert's status page (status.totalexpert.com) for updates from their end. We will provide a further update if there's a material change or new information becomes available.

TotalExpert has implemented a fix and confirmed stable, successful traffic on their end. We have not observed any webhook delivery failures since approximately 7:00 PM PST. We consider this incident resolved and will continue to monitor. Clients with questions about this incident, including requests for a root cause analysis, can reach out to their Blend support contact.

Blend is experiencing issues with Closings flowing from Encompass to Blend via EPC and PDD. We are actively investigating the issue and will continue to update as the situation progresses. Clients using the KM plug-in are unaffected.

We are continuing to investigate this issue and will update as the situation progresses.

We have identified the issue and are currently working on a fix. We will update this status as soon as the fix is deployed

RESOLVED- We have deployed a fix to production that resolves the issue affecting closings sent from Encompass to Blend through EPC and PDD. Closing packages can now resume being sent to Blend. We appreciate your patience while we worked to restore this functionality.

This incident has been resolved.

Per ICE Mortgage Technology's status page, some Encompass users are experiencing errors when sending Disclosures, receiving the message: "We are unable to send this request. Please ensure that you have a valid Consumer Connect site configured." ICE has identified this as related to a recent Encompass update (26.2.0.3) affecting third-party eDisclosure plugin functionality. Impact: Users may be unable to send Disclosures via Encompass on affected versions. If you are experiencing this issue, please refer to ICE's status page and contact Encompass/ICE support directly. We will continue to monitor and post updates here as we learn more.

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

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

Per ICE Mortgage Technology's status page, some Encompass users are experiencing errors when sending Disclosures, receiving the message: "We are unable to send this request. Please ensure that you have a valid Consumer Connect site configured." ICE has identified the root cause as an issue introduced in the 26.1 August Service Pack, which added a Consumer Connect site check to the Disclosure workflow. ICE is working on a fix and will provide a target release once identified. Impact: Users may be unable to send Disclosures via Encompass on affected versions. If you are experiencing this issue, please refer to ICE's status page and contact Encompass/ICE support directly for the latest updates and resolution timing. We will continue to monitor ICE's status page and post updates here as we learn more.

Per ICE Mortgage Technology's status page, a client-side fix for the Send Disclosures error has been released via critical patch 26.2.0.4, and has been deployed to both UAT and Production Encompass environments. Action required: To receive the patch, users will need to log out of the Encompass Smart Client and log back in. Several clients have confirmed service is restored after applying the patch. If you continue to experience issues sending Disclosures after logging back in, please reach out to the ICE/Encompass Support Team.

We have confirmed an issue that is impacting the status update and ability to complete closing packages for Hybrid and RON closings in Blend. Docusign has also reported these failures on their status page, https://status.docusign.com/. We are monitoring the situation closely and will provide an update as more information becomes available.

We are continuing to monitor the Docusign outage that is currently affecting the ability to complete Closing packages for Hybrid and RON closings in Blend. Docusign is continuing their investigation and you can check the status of this incident as well on their status page, https://status.docusign.com/. We are monitoring the situation closely and will provide an update as more information becomes available. In the meantime, as a precaution, we recommend papering out any closings that may be impacted today.

After further investigation, we have identified two separate issues affecting closings: RON Closings in Blend Signing Room: DocuSign is currently reporting a service degradation that is impacting notaries’ ability to complete a signing. This began on Jul 30 at 19:53 UTC and can be monitored on the DocuSign Status page (https://status.docusign.com/). Hybrid Closings, Disclosures, and Follow Up Using eSign Functionality: The outage is causing a large queue in our documents service, which is preventing eSignatures from being applied to documents. This is impacting hybrid closing workflows as well as Disclosure Services and Follow Up flows that rely on eSign functionality. Borrowers may still be able to complete documents, but signature application and task status updates are not processing correctly at this time. In the meantime, we recommend proceeding with paper closings and disclosures until this issue is resolved.

Our team is still investigating the root cause of the DocuSign e-sign availability issue in Blend environments, but we believe the impact is related to a high volume of events received by DocuSign as part of a recovery mitigation to their outage on Thursday evening, July 30th. Our team is currently determining the best next steps to implement a recovery strategy to resume production e-sign availability via DocuSign. Current borrower-facing experience does allow for the e-signing of documents within DocuSign, however the signature and package completion events are not being successfully processed between DocuSign and Blend, and as a result the document e-sign tasks are not getting set to complete successfully. We will share more updates as soon as we our teams have more information.

We scaled up processing capacity on our end to work through the backlog of signature and package completion events between DocuSign and Blend. This backlog has now fully processed, and document e-sign tasks are reflecting completion status successfully. RON, Hybrid Closings, Disclosures, and Follow Up flows using eSign functionality are operating normally. Thank you for your patience while we worked through this issue.