Historia awarii Blend

We have confirmed an issue affecting delivery of multi-factor authentication codes sent via SMS short code. Twilio has also reported this outage on their status page, https://status.twilio.com/. Some users may experience delays receiving their authentication code or may not receive it at all.

Twilio has observed a recovery in SMS delivery from a subset of Twilio Short Codes to network subscribers on multiple networks in the United States and are monitoring service stability. Twilio will provide another update in 2 hours or as soon as more information becomes available.

The issue affecting delivery of multi-factor authentication codes sent via SMS short code appears to be resolved. Service has recovered, and users should now be able to receive MFA codes as expected.

Cloudflare has reported an outage affecting its services. As a result, clients may experience intermittent errors, increased latency, or access issues. We are monitoring for any downstream impact to Blend services and are sharing Cloudflare's status page for the latest provider updates. Please refer to the Cloudflare status page https://www.cloudflarestatus.com for ongoing updates. We will continue to post updates here as needed.

Cloudflare has reported that traffic engineering efforts have successfully mitigated the majority of congestion and packet drops. Please refer to the linked Cloudflare status page for the latest provider updates.

We are currently investigating reports that Settlement Agents and borrowers are experiencing issues accessing closing documents. The impact includes: - Settlement Agents may be unable to complete tasks within Settlement Agent Workspace (workspace.blend.com) - Borrowers may be unable to complete tasks within their borrower portal - eSign closing packages may be blocked from being released to borrowers These issues may result in delays to scheduled closings. Our Engineering team is actively investigating the root cause and working to restore normal functionality as quickly as possible. We will provide additional updates as more information becomes available.

We are continuing to investigate an ongoing issue affecting portions of the Blend platform. While initial reports were related to closing document access, we are now seeing broader impact across multiple areas of the platform, including: General application slowness Disclosures failing to send Export failures Borrower portal and Settlement Agent Workspace performance issues Potential delays in closing-related workflows At this time, we believe a subset of clients may be affected, though our investigation is ongoing and we have not yet determined the full scope of impact. Our Engineering team is actively working to identify the root cause and restore normal platform functionality as quickly as possible. If you are experiencing any issues, please submit a ticket to Blend Support with details about the behavior you are encountering. This information will help us better understand the scope and impact of the incident. We will continue to provide updates as more information becomes available.

Our Engineering team continues to actively investigate the issues impacting portions of the Blend platform. At this time, we have not yet identified the root cause of the incident and are working to isolate the source of the issue as quickly as possible. Customers may continue to experience: General application slowness Disclosures failing to send Export failures Borrower portal and Settlement Agent Workspace performance issues Delays in closing-related workflows To help ensure scheduled closings are not delayed, Settlement Agents who need to print closing packages should contact the lender directly to obtain the necessary documents. If you are experiencing any issues, please let us know in the existing email thread if you have an open ticket for this. Otherwise, please submit a ticket to Blend Support with details about the behavior you are encountering. This information will help us better understand the scope and impact of the incident. We understand the disruption this is causing and appreciate your patience while we work to identify and resolve the issue.

We are observing improvements in platform performance and a reduction in reported issues. Our teams continue to investigate the underlying cause and are actively monitoring the environment. We are not yet ready to declare the incident fully resolved, but current indicators suggest the situation is improving. Additional details will be shared as they become available.

This incident has been resolved.

We are currently experiencing connectivity issues affecting the integration between Encompass and Blend, which is impacting the processing of disclosures. Preliminary investigation indicates this is due to a service degradation on our MuleSoft Middleware Platform (hosted by Salesforce). Our Engineering team is actively investigating the root cause and working toward a resolution. We apologize for any inconvenience this may cause and will provide further updates as new information becomes available.

Current Status: We have confirmed with ICE (Encompass) that the ongoing connectivity issue is intermittent. As a result, some disclosures are successfully routing to borrowers, while others may experience failures or delays. Please make a retry attempt if you see a failure with the issue being intermittent the retry may allow the package to be delivered. Technical Update: Salesforce (MuleSoft) support has confirmed a platform-wide service disruption on their end. The Blend Engineering team is actively engaged on a live call with Salesforce Support to prioritize and accelerate a resolution specifically for our integration pathways. We are closely monitoring the situation and will provide further updates as the joint remediation efforts progress.

We have received confirmation from ICE at approximately 3:30 PM PST that they are no longer experiencing the error that occurred this morning. Salesforce (MuleSoft) support has confirmed a platform-wide service disruption on their end. The Blend Engineering team is actively engaged with Salesforce Support to prioritize and accelerate a resolution specifically for our integration pathways. We are closely monitoring the situation and will provide further updates as the joint remediation efforts progress.

This incident has been resolved.

We are currently investigating an issue impacting Pipeline View search functionality. At this time, some users may be experiencing issues where Loan Originators and/or Loan Assignees are not appearing correctly in search results within the Pipeline View. As a result, users may be unable to effectively search and access portions of their pipeline. Our Engineering team is actively engaged and treating this as the highest priority. We will provide updates as soon as more information becomes available and work toward a resolution as quickly as possible.

This incident has been resolved.

We have been made aware of an Encompass outage that may be affecting exports, disclosure and document sync. Please visit the ICE status page for the latest updates: https://www.ice.com/status#mortgage-technology.

Encompass updated their status indicating that they are now seeing high success rates across all production user connections. They will be continuing their efforts for complete stabilization.

Encompass confirmed the issue on their end has been resolved and all services remain in a stable state.

We are currently investigating an issue impacting access to Blend Beta environments. Users may encounter a 502 error when attempting to access these environments. Our team is actively working with engineering to identify the root cause and restore normal functionality. We will provide updates as more information becomes available.

We are continuing to investigate this issue.

We are continuing to investigate the issue impacting access to Blend Beta environments. We believe we have identified the root cause, but are currently validating. Users may continue to encounter a 502 error when attempting to access these environments. Our team is actively validating the resolution to the root cause impacting Beta environments. At this time, we can confirm that only Beta environments were affected but we are continuing to monitor things and will provide more updates as they become available.

The issue impacting Blend Beta environments has been resolved, and the beta environments are now functioning normally. We will continue to monitor closely to ensure ongoing stability. Please feel free to reach out to us if you encounter any issues. Thank you for your patience while we worked through this issue.

The issue impacting Blend Beta environments has been resolved, and the beta environments are now functioning normally. We will continue to monitor closely to ensure ongoing stability. Please feel free to reach out to us if you encounter any issues. Thank you for your patience while we worked through this issue.

We are currently experiencing delays in receiving support tickets due to an issue with our ticketing system provider. The root cause has been identified as an ongoing infrastructure issue impacting Freshdesk’s mail servers, which is preventing some emails from being successfully delivered into our system. As a result, tickets sent via email may be delayed or not received. Additionally, Microsoft is currently experiencing a broader service outage, which may also be contributing to the issue. Investigations are still ongoing to fully understand the impact. Recommended action: If you need immediate assistance, please reach out to our Support team via chat to ensure your request is received. We are actively working with our partners and will continue to share updates as more information becomes available.

We are currently experiencing delays in receiving support tickets due to an issue with our ticketing system provider. The root cause has been identified as an ongoing infrastructure issue impacting Freshdesk’s mail servers, which is preventing some emails from being successfully delivered into our system. As a result, tickets sent via email may be delayed or not received. Additionally, Microsoft is currently experiencing a broader service outage, which may also be contributing to the issue. Investigations are still ongoing to fully understand the impact. Recommended action: If you need immediate assistance, please reach out to our Support team via chat to ensure your request is received. We are actively working with our partners and will continue to share updates as more information becomes available.

We are seeing signs of recovery, and tickets are beginning to flow into our system again. We are cautiously optimistic that service is being restored, but we are continuing to monitor closely. Earlier today, an issue impacting email delivery to our ticketing system prevented some messages from being successfully converted into tickets. At this time, we cannot guarantee that all communications sent via email were received or processed. Action required: Please review any requests or updates you sent today and resend them to ensure we have received and can act on them. As a reminder, our chat support has remained fully operational throughout this incident and is always available if you need immediate assistance. We appreciate your diligence and patience while we work to confirm full resolution and will continue to provide updates as we validate stability.

This incident has been resolved.

We are currently observing integration connection errors impacting document generation workflows. This issue may prevent the successful issuance of disclosures and can also impact the synchronization of disclosure status updates between Blend and the client’s LOS. Our engineering team is actively investigating the root cause and working to determine the scope and impact. We will provide additional updates as more information becomes available.

We have identified a short term update to resume successful document generation and disclosure issuance workflows. We are actively monitoring the system and working to replay events for any impacted loans. Our team is continuing to actively investigate the root cause of the integration connection errors to ensure all document generation and disclosure workflow traffic can be processed successfully. We will provide additional updates as soon as the long term root cause fix is identified.

We have confirmed that our update to address the connection issues impacting document generation and disclosures workflows has resolved the errors observed earlier today. Our team is continuing to monitor for any further errors and replay events to mitigate any impacted loans. We will update this issue to resolved once all impact loan events have been addressed.

This incident has been resolved.

We are currently investigating API Gateway issues. Some clients may see 502 Bad Gateway errors or experience disruptions with API-related functionality, including document generation, disclosures, or exports. If you encounter any of these issues, please reach out to support so we can investigate. We will provide updates as more information becomes available.

API-related functionality, including exports, document generation, and disclosures, is currently stable. We recently increased the number of API Gateway pods and continue to monitor traffic and performance. We are proactively tracking any failed exports and adjusting auto-scaling settings to maintain reliability.

This incident has been resolved.

We are currently experiencing processing delays with manually tagged Hybrid closing packages. Our engineering team is actively investigating the root cause to restore normal processing speeds. In the meantime, we recommend sending closing packages as Traditional.

Resolved but still monitoring. Continue to send Hybrid Closing packages.

Starting at approximately 10:10am PST we began observing elevated traffic partially impacting API availability. Our team is actively working on preventing impact and restoring API availability.

At approximately 10:30am PST we adjusted our API services to address an increased volume of request errors. We have observed stable successful API request traffic since then. Our teams continue to actively monitor API performance.

This incident has been resolved.

We are currently investigating api failures.

At approximately 7:40am PST we deployed updates to some internal services that resolved all observed API request errors. We are actively monitoring for any further impact.

This incident has been resolved.

Investigation - We are aware of an issue impacting all logins (email and SSO), Our team is actively investigating the root cause and will provide updates as more information becomes available.

Our team is actively investigating the root cause of the login issue and will provide updates as more information becomes available.

Our team is actively working on a solution and will provide updates as more information becomes available.

We have identified the root cause of the issue impacting all logins (email and SSO), application creation, eClose, disclosures, and Public API. Our team is actively working a solution and will provide updates as more information becomes available.

Our team has made measurable progress and is still actively working on a solution. We will provide updates as more information becomes available

We are seeing signs of improvement on logins (emails and SSOs). Our Engineering team remains actively engaged and finalizing the mitigations on the affected services (eClose, magic link logins, disclosures, and TPRs). We will share additional updates as more information becomes available.

We are seeing signs of recovery on all logins, public API, and disclosures. Our engineering team remains actively engaged and finalizing the mitigations on the affected services (eClose and TPRs). We will share additional updates as more information becomes available.

We are seeing signs of recovery on all logins and disclosures. Our engineering team remains actively engaged and finalizing the mitigations on the affected services (eClose, public API, and TPRs). We will share additional updates as more information becomes available.

We have deployed the mitigation for the production API. We are aware that site access, export, and disclosures may have been affected during the deployment process and should have been fixed. We are monitoring the environment for further stability.

Earlier today, the platform experienced an unusually large surge of external traffic impacting authentication-related services, which led to intermittent access issues. During the incident, the following services were affected: - Core authentication (email+password logins, SSO, magic links, Blend Signing Room) - Public API (including exports, disclosures, and CRM integrations) Mitigations have been applied, system load has stabilized, and services are operating normally. A small number of users may briefly notice a browser warning when logging into Blend Signing Room (RONs); this does not impact functionality and is being resolved. We are continuing to monitor closely and will provide a follow-up once stability is fully confirmed.

Resolved / Monitoring — All Blend Platform services are operating normally. System load has stabilized. No new user-facing issues have been observed. We are continuing to address residual impacts from the earlier disruption. We will continue to monitor closely to ensure sustained stability and will provide an update if there are any material changes.

Monitoring — All Blend Platform services remain operational and stable. The issue with Blend Signing Room has been resolved. We are continuing to address residual impacts from today’s disruption. Manual Hybrid eClose: Close Ops is currently unable to process manual hybrid closings for packages with a closing date of 1/14. Please send any hybrid packages closing today as Traditional. We will provide an update when manual hybrid processing is restored.

Stable — All services are operating normally. The issue affecting manual hybrid closings has been resolved.

This incident has been resolved.

We are aware of an issue currently impacting all logins(emails and SSO), app creation, eClose, disclosures, and are actively investigating the root cause.

We are aware of an issue impacting all logins (email and SSO), application creation, eClose, and disclosures. Our team is actively investigating the root cause and will provide updates as more information becomes available.

We are seeing signs of improvement across impacted services. Our Engineering team remains actively engaged and continues to investigate the root cause. We will share additional updates as more information becomes available.

We are seeing signs of recovery of Blend Platform logins (email and SSO). Our Engineering team remains actively engaged and continues to investigate Blend Signing Room (RONs) and other affected services. We will share additional updates as more information becomes available.

All affected services including Blend Signing Room (RONs) and Public API have been recovered.

Issue affecting our internal reporting data pipelines. No impact to customer business operations, and no data is being lost. However, reporting API's will not contain up-to-date data until the issue is resolved. 11/24 is the last day we have data for at the moment.

This incident has been resolved.

Blend has been made aware of an issue that may have impacted application exports where applications may have been left in "in progress" export status as a result of a temporary issue that has since been resolved. Blend is working to identify a list of potentially impacted applications apply the respective corrections. We will continue to monitor for updates and relay them as soon as they become available. In the meantime, please don't hesitate to reach back with any additional question to support@blend.com

We have identified the impacted applications and re-exported applications stuck "in progress." We have started sending out impact lists individually to any impacted clients.

We want to inform you of an active issue currently affecting the Blend platform. Automated Underwriting (AUS) requests—specifically DU and LP—are not successfully running for clients at this time. Our engineering team is actively investigating the root cause and working to restore AUS functionality as quickly as possible. We will share further updates as soon as more information becomes available. Thank you for your patience while we work to resolve this.

AUS Functionality Fully Restored We have successfully resolved and confirmed the full restoration of AUS functionality. You can now run AUS as expected. Please note that this incident was strictly confined to AUS; there were no other known or expected impacts to any other Blend features or user data. Thank you for your patience as our team worked to deploy this fix quickly. We appreciate your partnership.

We are currently experiencing an outage affecting the Blend Signing Room, making it inoperable. This issue stems from our vendor responsible for generating the Knowledge-Based Authentication (KBA) security questions. We are in close contact with the vendor and will provide an update immediately once the service is restored. In the interim, we recommend that RON signing appointments be changed to Hybrid or Traditional, or rescheduled for another day.

We are currently experiencing an outage affecting the Blend Signing Room, making it inoperable. This issue stems from our vendor responsible for generating the Knowledge-Based Authentication (KBA) security questions. We are in close contact with the vendor and will provide an update immediately once the service is restored. In the interim, we recommend that RON signing appointments be changed to Hybrid or Traditional, or rescheduled for another day.

This incident has been resolved.

A major Amazon Web Services (AWS) outage is causing widespread internet disruptions, impacting multiple apps and services, including Blend. We are continuing to investigate this issue.

We are seeing Blend services recover from the disruption and continue to monitor.

We are continuing to monitor for any further issues.

We continue to see infrastructure-related issues which continue to have an impact on the availability and performance of the Blend platform. We will update this status page at a regular interval or when we see consistent recovery across the platform.

We are continuing to investigate this issue.

While Blend has been able to recover some services, we are proceeding carefully and have not immediately enacted our disaster recovery process. This decision is intentional — cross-region disaster recovery is a complex process that carries potential risks, including data loss, impact to unaffected clients, and the possibility of slowing overall recovery for those already stabilizing. Our engineering teams are closely monitoring AWS’s progress and Blend’s own platform stability to ensure that any action we take fully protects client data and minimizes disruption. Once we have confidence in a stable recovery path, we will take any necessary next steps to restore full service safely and efficiently.

AWS continues to experience issues in the US-EAST-1 region and is actively working to deploy a fix within the next few hours. Blend’s internal teams are continuing to monitor the situation closely and are exploring the option of cutting over to another fully functional AWS region. However, this decision involves a number of considerations — including the potential risks of data loss, impact to currently unaffected clients, and overall recovery stability. We are handling this situation with the utmost care to ensure that any action taken is safe, deliberate, and in the best interest of all clients. Please continue monitoring our status page as well as the AWS Status Page https://health.aws.amazon.com/health/status for updates.

We wanted to provide you with the latest update regarding the ongoing service disruption. AWS has identified the root cause and is actively deploying a solution to restore compute resource availability. To mitigate the impact during this period, our engineering team strategically reallocated available resources to prioritize critical functions, such as application submission. While this ensured the stability of core services, it may have temporarily affected performance in other areas of the platform. We are beginning to see signs of recovery as the AWS fixes are rolled out. While service may be intermittent over the next couple of hours, AWS anticipates the deployment will be complete within approximately two hours, at which point we expect a full restoration of service.

We have recovered our baseline infrastructure capacity, and the Blend platform is now fully available. System performance has stabilized, and latencies have returned to normal levels. We are currently processing a backlog of loan applications that accumulated during the disruption and will provide an update once that backlog has been fully cleared. Thank you for your patience and understanding as we worked through this issue.

We have recovered our baseline infrastructure capacity, and the Blend platform is now fully available. System performance has stabilized, and latencies have returned to normal levels. We are currently processing a backlog of loan applications that accumulated during the disruption and will provide an update once that backlog has been fully cleared. Thank you for your patience and understanding as we worked through this issue.

Our application export queues have returned to normal levels. At this time, we believe that this incident is resolved, although some of Blend's integration partners may continue to experience issues as they recover.