Historial de interrupciones de Blend

1. August 13, 2026 at 2:05 PM UTCinvestigating

   Blend está experimentando problemas con Closings que fluyen de Encompass a Blend a través de EPC y PDD. Estamos investigando activamente la cuestión y seguiremos actualizando a medida que avance la situación. Los clientes que usan el plug-in KM no son afectados.

2. August 13, 2026 at 3:05 PM UTCinvestigating

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

3. August 13, 2026 at 3:41 PM UTCidentified

   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. August 13, 2026 at 5:30 PM UTCmonitoring

   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. August 13, 2026 at 7:55 PM UTCresolved

   This incident has been resolved.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 10, 2026 at 8:31 PM UTCidentified

   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. August 10, 2026 at 8:43 PM UTCidentified

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

3. August 10, 2026 at 9:16 PM UTCidentified

   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.

4. August 11, 2026 at 2:50 PM UTCresolved

   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.

1. July 31, 2026 at 2:19 PM UTCidentified

   Hemos confirmado un problema que está afectando la actualización de estado y la capacidad de completar paquetes de cierre para cierres híbridos y RON en Blend. Docusign también ha informado de estos fallos en su página de estado, https://status.docusign.com/. Estamos monitoreando la situación de cerca y proporcionaremos una actualización a medida que se disponga de más información.

2. July 31, 2026 at 4:12 PM UTCidentified

   Continuamos monitoreando el outage Docusign que está afectando actualmente la capacidad de completar paquetes de cierre para cierres híbridos y RON en Blend. Docusign continúa su investigación y puede comprobar el estado de este incidente también en su página de estado, https://status.docusign.com/. Estamos monitoreando la situación de cerca y proporcionaremos una actualización a medida que se disponga de más información. Mientras tanto, como precaución, recomendamos que se publique cualquier cierre que pueda ser impactado hoy.

3. July 31, 2026 at 5:38 PM UTCidentified

   Tras nuevas investigaciones, hemos identificado dos cuestiones separadas que afectan a los cierres: RON Closings in Blend Signing Room: DocuSign está reportando una degradación del servicio que está afectando la capacidad de los notarios para completar una firma. This began on Jul 30 at 19:53 UTC and can be monitored on the DocuSign Status page (https://status.docusign.com/). Ropas híbridas, revelaciones y seguimiento usando eSign Funcionalidad: La salida está causando una gran cola en nuestro servicio de documentos, lo que impide que las eSignatures se apliquen a los documentos. Esto está impactando los flujos de trabajo de cierre híbrido, así como los Servicios de Divulgación y los flujos de seguimiento que dependen de la funcionalidad de eSign. Los prestamistas todavía pueden completar documentos, pero las actualizaciones de la solicitud de firma y el estado de tarea no se procesan correctamente en este momento. Mientras tanto, recomendamos proceder con cierres de papel y divulgaciones hasta que se resuelva esta cuestión.

4. July 31, 2026 at 6:33 PM UTCidentified

   Nuestro equipo sigue investigando la causa raíz del problema de disponibilidad de firmas electrónicas DocuSign en entornos Blend, pero creemos que el impacto está relacionado con un alto volumen de eventos recibidos por DocuSign como parte de una mitigación de la recuperación a su salida el jueves 30 de julio. Nuestro equipo está determinando los mejores próximos pasos para implementar una estrategia de recuperación para reanudar la disponibilidad de e-sign de producción a través de DocuSign. La experiencia actual en el uso de prestatarios permite la firma electrónica de documentos dentro de DocuSign, sin embargo, los eventos de finalización de firmas y paquetes no se están procesando con éxito entre DocuSign y Blend, y como resultado, las tareas de firma electrónica del documento no se están estableciendo para completar con éxito. Compartiremos más actualizaciones tan pronto como nuestros equipos tengan más información.

5. July 31, 2026 at 7:45 PM UTCresolved

   Ampliamos la capacidad de procesamiento en nuestro final para trabajar a través del atraso de eventos de firma y de terminación de paquetes entre DocuSign y Blend. Este atraso se ha tramitado plenamente y las tareas de la firma electrónica del documento reflejan con éxito el estado de terminación. RON, Hybrid Closings, Disclosures y Follow Up flujos usando la funcionalidad eSign funcionan normalmente. Gracias por su paciencia mientras trabajamos a través de este tema.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 29, 2026 at 3:09 AM UTCinvestigating

   La plataforma Blend no está disponible actualmente. Nuestros equipos de productos e ingeniería están investigando activamente y proporcionaremos actualizaciones de estado frecuentes en breve.

2. July 29, 2026 at 3:34 AM UTCinvestigating

   Estamos en el proceso de recuperar la liberación más reciente que creemos que desbloqueará el acceso a la producción. Esperamos que esto esté completo en los próximos 10 minutos.

3. July 29, 2026 at 4:02 AM UTCmonitoring

   Hemos confirmado que el rollo de liberación ha abordado la disponibilidad de producción. Confirmamos que esta salida sólo impacta el acceso a la producción de préstamos en la Plataforma de Constructores de Blend, y que la Plataforma de Lending está plenamente operativa. Estamos monitoreando el desempeño del tráfico en la Plataforma Blend Builder, pero esperamos que esto sea totalmente operativo a las 8:40pm PT.

4. July 29, 2026 at 4:12 AM UTCmonitoring

   Todos los monitores Blend para el tráfico en la plataforma Blend Builder están mostrando disponibilidad de producción completa y recuperación de rendimiento y están plenamente operativos ahora

5. July 29, 2026 at 7:00 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 23, 2026 at 4:47 PM UTCinvestigating

   Somos conscientes de un problema que algunos usuarios de nuestra integración en la entrega de documentos de socio (PDD) pueden estar experimentando en este momento. Nuestro equipo está investigando activamente la causa raíz y trabajando para resolver el problema lo antes posible. Apreciamos su paciencia.

2. July 23, 2026 at 5:05 PM UTCinvestigating

   Somos conscientes de un problema que está causando retrasos con nuestra integración en la entrega de documentos de socio (PDD). El rendimiento de la API puede retrasarse. Nuestro equipo está investigando activamente la causa raíz y trabajando para resolver el problema lo antes posible. Apreciamos su paciencia.

3. July 23, 2026 at 6:29 PM UTCinvestigating

   Continuamos investigando la cuestión que está causando retrasos con nuestra integración en la entrega de documentos de socio (PDD). Durante este tiempo, el rendimiento de API puede retrasarse. Estamos trabajando para resolver este problema lo antes posible. Apreciamos su paciencia.

4. July 23, 2026 at 8:11 PM UTCinvestigating

   Nuestro equipo de Ingeniería continúa investigando activamente el problema causando retrasos con nuestra integración en la entrega de documentos de socio (PDD). Estamos progresando en aislar la causa raíz y estamos trabajando para implementar una resolución lo más rápido posible. Seguiremos proporcionando actualizaciones a medida que se disponga de más información.

5. July 23, 2026 at 10:02 PM UTCresolved

   El Equipo de Ingeniería de Blend ha identificado la causa de las demoras intermitentes que afectan a nuestra integración de la Entrega de Documentos de Socios (PDD) y el servicio ha vuelto a la normalidad. Nuestro equipo de ingeniería ha implementado mitigacións para restaurar la estabilidad y seguirá monitoreando el medio ambiente de cerca para asegurar que la cuestión no se repita. También seguimos trabajando en mejoras adicionales para fortalecer aún más la resiliencia de la integración. Gracias por su paciencia mientras trabajamos para resolver este problema.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 22, 2026 at 4:38 PM UTCinvestigating

   Actualmente estamos investigando un problema donde los usuarios pueden ser incapaces de enviar paquetes de cierre a Blend. Nuestro equipo está trabajando activamente para identificar la causa raíz y restaurar la funcionalidad normal lo antes posible. Seguiremos vigilando de cerca la situación y proporcionaremos más actualizaciones a medida que se disponga de más información.

2. July 22, 2026 at 5:52 PM UTCmonitoring

   Hemos identificado un problema que impacta la capacidad de enviar paquetes de cierre. Se ha implementado una solución, y estamos monitoreando activamente el sistema para confirmar que el envío de funcionalidad ha sido restaurado completamente. Vamos a proporcionar otra actualización una vez que el problema esté completamente resuelto

3. July 22, 2026 at 9:09 PM UTCresolved

   La solución para esta cuestión ha sido desplegada y creemos que la cuestión está totalmente resuelta.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 22, 2026 at 4:37 PM UTCmonitoring

   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. June 22, 2026 at 5:33 PM UTCmonitoring

   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. June 22, 2026 at 7:57 PM UTCresolved

   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.

1. June 22, 2026 at 3:00 PM UTCmonitoring

   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. June 22, 2026 at 6:52 PM UTCresolved

   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.

1. June 10, 2026 at 5:06 PM UTCinvestigating

   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. June 10, 2026 at 5:35 PM UTCinvestigating

   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. June 10, 2026 at 6:41 PM UTCinvestigating

   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.

4. June 10, 2026 at 8:48 PM UTCmonitoring

   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. June 10, 2026 at 10:02 PM UTCresolved

   This incident has been resolved.

1. June 5, 2026 at 7:11 PM UTCidentified

   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. June 5, 2026 at 8:57 PM UTCidentified

   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. June 5, 2026 at 11:22 PM UTCmonitoring

   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. June 8, 2026 at 2:04 PM UTCresolved

   This incident has been resolved.

1. May 13, 2026 at 3:21 PM UTCinvestigating

   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. May 13, 2026 at 3:55 PM UTCresolved

   This incident has been resolved.

1. April 24, 2026 at 4:21 PM UTCidentified

   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. April 24, 2026 at 6:56 PM UTCmonitoring

   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. April 25, 2026 at 1:49 PM UTCresolved

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

1. April 9, 2026 at 4:26 PM UTCinvestigating

   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. April 9, 2026 at 4:32 PM UTCinvestigating

   We are continuing to investigate this issue.

3. April 9, 2026 at 6:27 PM UTCinvestigating

   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. April 9, 2026 at 8:06 PM UTCinvestigating

   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. April 9, 2026 at 8:07 PM UTCresolved

   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.

1. April 8, 2026 at 4:54 PM UTCinvestigating

   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. April 8, 2026 at 6:22 PM UTCidentified

   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. April 8, 2026 at 9:36 PM UTCmonitoring

   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. April 9, 2026 at 2:11 PM UTCresolved

   This incident has been resolved.

1. March 5, 2026 at 10:00 PM UTCinvestigating

   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. March 5, 2026 at 11:03 PM UTCidentified

   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. March 5, 2026 at 11:34 PM UTCmonitoring

   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. March 6, 2026 at 4:22 AM UTCresolved

   This incident has been resolved.

1. March 2, 2026 at 7:48 PM UTCinvestigating

   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. March 2, 2026 at 8:40 PM UTCmonitoring

   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. March 2, 2026 at 10:55 PM UTCresolved

   This incident has been resolved.

1. February 11, 2026 at 3:50 PM UTCinvestigating

   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. February 11, 2026 at 5:05 PM UTCresolved

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

1. January 20, 2026 at 6:35 PM UTCinvestigating

   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. January 20, 2026 at 8:00 PM UTCmonitoring

   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. January 21, 2026 at 12:59 AM UTCresolved

   This incident has been resolved.

1. January 20, 2026 at 3:13 PM UTCinvestigating

   We are currently investigating api failures.

2. January 20, 2026 at 4:45 PM UTCmonitoring

   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. January 21, 2026 at 12:59 AM UTCresolved

   This incident has been resolved.

1. January 14, 2026 at 1:38 PM UTCinvestigating

   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. January 14, 2026 at 2:21 PM UTCinvestigating

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

3. January 14, 2026 at 3:11 PM UTCidentified

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

4. January 14, 2026 at 3:28 PM UTCidentified

   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. January 14, 2026 at 4:35 PM UTCidentified

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

6. January 14, 2026 at 5:05 PM UTCmonitoring

   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.

7. January 14, 2026 at 5:46 PM UTCmonitoring

   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.

8. January 14, 2026 at 6:42 PM UTCmonitoring

   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.

9. January 14, 2026 at 8:28 PM UTCmonitoring

   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.

10. January 14, 2026 at 9:25 PM UTCmonitoring

    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.

11. January 14, 2026 at 10:45 PM UTCmonitoring

    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.

12. January 15, 2026 at 1:18 AM UTCmonitoring

    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.

13. January 15, 2026 at 2:56 AM UTCmonitoring

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

14. January 17, 2026 at 12:17 AM UTCresolved

    This incident has been resolved.