Blend Outage History

Started Sep 07, 2026, 04:59 PM UTC· resolved Sep 07, 2026, 08:01 PM UTC

1. investigating Sep 07, 2026, 04:59 PM UTC

   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.

2. investigating Sep 07, 2026, 05:58 PM UTC

   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.

3. investigating Sep 07, 2026, 06:46 PM UTC

   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.

4. resolved Sep 07, 2026, 08:01 PM UTC

   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.

Read the full incident report →

Started Sep 04, 2026, 08:27 PM UTC· resolved Sep 05, 2026, 11:41 AM UTC

1. monitoring Sep 04, 2026, 08:27 PM UTC

   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.

2. monitoring Sep 04, 2026, 10:01 PM UTC

   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.

3. monitoring Sep 04, 2026, 10:41 PM UTC

   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.

4. monitoring Sep 05, 2026, 01:17 AM UTC

   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.

5. resolved Sep 05, 2026, 11:41 AM UTC

   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.

Read the full incident report →

Started Aug 13, 2026, 02:05 PM UTC· resolved Aug 13, 2026, 07:55 PM UTC

1. investigating Aug 13, 2026, 02:05 PM UTC

   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.

2. investigating Aug 13, 2026, 03:05 PM UTC

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

3. identified Aug 13, 2026, 03:41 PM UTC

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

4. monitoring Aug 13, 2026, 05:30 PM UTC

   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.

5. resolved Aug 13, 2026, 07:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 10, 2026, 08:28 PM UTC· resolved Aug 11, 2026, 02:50 PM UTC

1. identified Aug 10, 2026, 08:28 PM UTC

   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.

2. identified Aug 10, 2026, 08:31 PM UTC

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

3. identified Aug 10, 2026, 08:43 PM UTC

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

4. identified Aug 10, 2026, 09:16 PM UTC

   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.

5. resolved Aug 11, 2026, 02:50 PM UTC

   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.

Read the full incident report →

Started Jul 31, 2026, 02:19 PM UTC· resolved Jul 31, 2026, 07:45 PM UTC

1. identified Jul 31, 2026, 02:19 PM UTC

   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.

2. identified Jul 31, 2026, 04:12 PM UTC

   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.

3. identified Jul 31, 2026, 05:38 PM UTC

   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.

4. identified Jul 31, 2026, 06:33 PM UTC

   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.

5. resolved Jul 31, 2026, 07:45 PM UTC

   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.

Read the full incident report →

Started Jul 29, 2026, 03:09 AM UTC· resolved Jul 29, 2026, 07:00 PM UTC

1. investigating Jul 29, 2026, 03:09 AM UTC

   The Blend platform is currently unavailable. Our product and engineering teams are actively investigating and we will provide frequent status updates shortly.

2. investigating Jul 29, 2026, 03:34 AM UTC

   We are in the process of rolling back the most recent release that we believe will unblock production access. We anticipate this being complete in the next 10 minutes.

3. monitoring Jul 29, 2026, 04:02 AM UTC

   We have confirmed the release roll back has addressed production availability. We confirmed that this outage only impact production access for loans on the Blend Builder Platform, and that the Lending Platform is fully operational. We are monitoring the performance of traffic on the Blend Builder Platform, but expect this to be fully operational as on 8:40pm PT.

4. monitoring Jul 29, 2026, 04:12 AM UTC

   All Blend monitors for traffic on the Blend Builder Platform are showing full production availability and performance recovery and are fully operational now

5. resolved Jul 29, 2026, 07:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 23, 2026, 04:47 PM UTC· resolved Jul 23, 2026, 10:02 PM UTC

1. investigating Jul 23, 2026, 04:47 PM UTC

   We're aware of an issue that some users of our Encompass Partner Document Delivery (PDD) integration may be experiencing at this time. Our team is actively investigating the root cause and working to resolve the issue as quickly as possible. We appreciate your patience.

2. investigating Jul 23, 2026, 05:05 PM UTC

   We're aware of an issue that is causing delays with our Encompass Partner Document Delivery (PDD) integration. API performance may be delayed. Our team is actively investigating the root cause and working to resolve the issue as quickly as possible. We appreciate your patience.

3. investigating Jul 23, 2026, 06:29 PM UTC

   We are continuing to investigate the issue that is causing delays with our Encompass Partner Document Delivery (PDD) integration. During this time API performance may be delayed. We are working to resolve this issue as quickly as possible. We appreciate your patience.

4. investigating Jul 23, 2026, 08:11 PM UTC

   Our Engineering team continues to actively investigate the issue causing delays with our Encompass Partner Document Delivery (PDD) integration. We are making progress in isolating the root cause and are working to implement a resolution as quickly as possible. We will continue to provide updates as more information becomes available.

5. resolved Jul 23, 2026, 10:02 PM UTC

   The Blend Engineering Team has identified the cause of the intermittent delays affecting our Encompass Partner Document Delivery (PDD) integration, and service has returned to normal. Our Engineering team has implemented mitigations to restore stability and will continue to monitor the environment closely to ensure the issue does not recur. We are also continuing work on additional improvements to further strengthen the resiliency of the integration. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Started Jul 22, 2026, 04:38 PM UTC· resolved Jul 22, 2026, 09:09 PM UTC

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

   We are currently investigating an issue where users may be unable to send closing packages to Blend. Our team is actively working to identify the root cause and restore normal functionality as quickly as possible. We will continue to monitor the situation closely and provide further updates as more information becomes available.

2. monitoring Jul 22, 2026, 05:52 PM UTC

   We have identified an issue impacting the ability to send closing packages. A fix has been deployed, and we are actively monitoring the system to confirm that sending functionality has been fully restored. We will provide another update once the issue is fully resolved

3. resolved Jul 22, 2026, 09:09 PM UTC

   The fix for this issue has now been deployed, and we believe the matter is fully resolved.

Read the full incident report →

Started Jun 22, 2026, 04:37 PM UTC· resolved Jun 22, 2026, 07:57 PM UTC

1. monitoring Jun 22, 2026, 04:37 PM UTC

   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.

2. monitoring Jun 22, 2026, 05:33 PM UTC

   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.

3. resolved Jun 22, 2026, 07:57 PM UTC

   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.

Read the full incident report →

Started Jun 22, 2026, 03:00 PM UTC· resolved Jun 22, 2026, 06:52 PM UTC

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

   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.

2. resolved Jun 22, 2026, 06:52 PM UTC

   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.

Read the full incident report →

Started Jun 10, 2026, 05:06 PM UTC· resolved Jun 10, 2026, 10:02 PM UTC

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

   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.

2. investigating Jun 10, 2026, 05:35 PM UTC

   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.

3. investigating Jun 10, 2026, 06:41 PM UTC

   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 issues, please continue to submit tickets to Blend Support with details about the behavior you are encountering. This information is helping our teams 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.

4. monitoring Jun 10, 2026, 08:48 PM UTC

   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.

5. resolved Jun 10, 2026, 10:02 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 05, 2026, 07:11 PM UTC· resolved Jun 08, 2026, 02:04 PM UTC

1. identified Jun 05, 2026, 07:11 PM UTC

   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.

2. identified Jun 05, 2026, 08:57 PM UTC

   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.

3. monitoring Jun 05, 2026, 11:22 PM UTC

   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.

4. resolved Jun 08, 2026, 02:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 13, 2026, 03:21 PM UTC· resolved May 13, 2026, 03:55 PM UTC

1. investigating May 13, 2026, 03:21 PM UTC

   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.

2. resolved May 13, 2026, 03:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 24, 2026, 04:21 PM UTC· resolved Apr 25, 2026, 01:49 PM UTC

1. identified Apr 24, 2026, 04:21 PM UTC

   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.

2. monitoring Apr 24, 2026, 06:56 PM UTC

   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.

3. resolved Apr 25, 2026, 01:49 PM UTC

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

Read the full incident report →

Started Apr 09, 2026, 04:26 PM UTC· resolved Apr 09, 2026, 08:07 PM UTC

1. investigating Apr 09, 2026, 04:26 PM UTC

   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.

2. investigating Apr 09, 2026, 04:32 PM UTC

   We are continuing to investigate this issue.

3. investigating Apr 09, 2026, 06:27 PM UTC

   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.

4. investigating Apr 09, 2026, 08:06 PM UTC

   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.

5. resolved Apr 09, 2026, 08:07 PM UTC

   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.

Read the full incident report →

Started Apr 08, 2026, 04:54 PM UTC· resolved Apr 09, 2026, 02:11 PM UTC

1. investigating Apr 08, 2026, 04:54 PM UTC

   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.

2. identified Apr 08, 2026, 06:22 PM UTC

   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.

3. monitoring Apr 08, 2026, 09:36 PM UTC

   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.

4. resolved Apr 09, 2026, 02:11 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 05, 2026, 10:00 PM UTC· resolved Mar 06, 2026, 04:22 AM UTC

1. investigating Mar 05, 2026, 10:00 PM UTC

   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.

2. identified Mar 05, 2026, 11:03 PM UTC

   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.

3. monitoring Mar 05, 2026, 11:34 PM UTC

   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.

4. resolved Mar 06, 2026, 04:22 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 02, 2026, 07:48 PM UTC· resolved Mar 02, 2026, 10:55 PM UTC

1. investigating Mar 02, 2026, 07:48 PM UTC

   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.

2. monitoring Mar 02, 2026, 08:40 PM UTC

   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.

3. resolved Mar 02, 2026, 10:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 11, 2026, 03:50 PM UTC· resolved Feb 11, 2026, 05:05 PM UTC

1. investigating Feb 11, 2026, 03:50 PM UTC

   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.

2. resolved Feb 11, 2026, 05:05 PM UTC

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

Read the full incident report →

Started Jan 20, 2026, 06:35 PM UTC· resolved Jan 21, 2026, 12:59 AM UTC

1. investigating Jan 20, 2026, 06:35 PM UTC

   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.

2. monitoring Jan 20, 2026, 08:00 PM UTC

   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.

3. resolved Jan 21, 2026, 12:59 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 20, 2026, 03:13 PM UTC· resolved Jan 21, 2026, 12:59 AM UTC

1. investigating Jan 20, 2026, 03:13 PM UTC

   We are currently investigating api failures.

2. monitoring Jan 20, 2026, 04:45 PM UTC

   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.

3. resolved Jan 21, 2026, 12:59 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 14, 2026, 01:38 PM UTC· resolved Jan 17, 2026, 12:17 AM UTC

1. investigating Jan 14, 2026, 01:38 PM UTC

   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.

2. investigating Jan 14, 2026, 02:21 PM UTC

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

3. identified Jan 14, 2026, 03:11 PM UTC

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

4. identified Jan 14, 2026, 03:28 PM UTC

   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.

5. identified Jan 14, 2026, 04:03 PM UTC

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

6. identified Jan 14, 2026, 04:35 PM UTC

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

7. monitoring Jan 14, 2026, 05:05 PM UTC

   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.

8. monitoring Jan 14, 2026, 05:46 PM UTC

   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.

9. monitoring Jan 14, 2026, 06:42 PM UTC

   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.

10. monitoring Jan 14, 2026, 08:28 PM UTC

    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.

11. monitoring Jan 14, 2026, 09:25 PM UTC

    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.

12. monitoring Jan 14, 2026, 10:45 PM UTC

    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.

13. monitoring Jan 15, 2026, 01:18 AM UTC

    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.

14. monitoring Jan 15, 2026, 02:56 AM UTC

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

15. resolved Jan 17, 2026, 12:17 AM UTC

    This incident has been resolved.

Read the full incident report →

Started Jan 13, 2026, 08:23 PM UTC· resolved Jan 13, 2026, 09:52 PM UTC

1. investigating Jan 13, 2026, 08:23 PM UTC

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

2. investigating Jan 13, 2026, 08:45 PM UTC

   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.

3. investigating Jan 13, 2026, 09:01 PM UTC

   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.

4. investigating Jan 13, 2026, 09:22 PM UTC

   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.

5. resolved Jan 13, 2026, 09:52 PM UTC

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

Read the full incident report →

Started Nov 26, 2025, 04:14 AM UTC· resolved Dec 01, 2025, 04:30 PM UTC

1. investigating Nov 26, 2025, 04:14 AM UTC

   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.

2. resolved Dec 01, 2025, 04:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 25, 2025, 04:40 PM UTC· resolved Nov 25, 2025, 09:02 PM UTC

1. monitoring Nov 25, 2025, 04:40 PM UTC

   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 [email protected]

2. resolved Nov 25, 2025, 09:02 PM UTC

   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.

Read the full incident report →