Histórico de interrupções do Blend

1. 13 Eost 2026 da 14:05 UTCinvestigating

   A mistura está passando por problemas com fechamentos que vão da Encompass à Blend via EPC e PDD. Estamos a investigar activamente a questão e vamos continuar a actualizar à medida que a situação avança. Os clientes que usam o plug-in KM não são afetados.

2. 13 Eost 2026 da 15:05 UTCinvestigating

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

3. 13 Eost 2026 da 15:41 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. 13 Eost 2026 da 17:30 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. 13 Eost 2026 da 19:55 UTCresolved

   This incident has been resolved.

Traduzido automaticamente da atualização oficial do incidente.

1. 10 Eost 2026 da 20:31 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. 10 Eost 2026 da 20:43 UTCidentified

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

3. 10 Eost 2026 da 21:16 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. 11 Eost 2026 da 14:50 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. 31 Gouere 2026 da 14:19 UTCidentified

   Nós confirmamos um problema que está impactando a atualização de status e a capacidade de concluir pacotes de fechamento para fechamentos Híbrido e RON em Mistura. Docusign também relatou essas falhas em sua página de status, https://status.docusign.com/. Estamos acompanhando de perto a situação e forneceremos uma atualização à medida que mais informações estiverem disponíveis.

2. 31 Gouere 2026 da 16:12 UTCidentified

   Continuamos a monitorar a falha do Docusign que está afetando atualmente a capacidade de concluir pacotes de fechamento para fechamentos Híbrido e RON em Mistura. Docusign está continuando sua investigação e você pode verificar o status deste incidente também em sua página de status, https://status.docusign.com/. Estamos acompanhando de perto a situação e forneceremos uma atualização à medida que mais informações estiverem disponíveis. Entretanto, por precaução, recomendamos que se empenhem quaisquer encerramentos que possam ser afectados hoje.

3. 31 Gouere 2026 da 17:38 UTCidentified

   Após uma investigação mais aprofundada, identificamos duas questões distintas que afectam o encerramento: RON Encerramentos na Sala de Assinatura da Blend: DocuSign está atualmente relatando uma degradação de serviço que está impactando a capacidade dos notários para concluir uma assinatura. Isso começou em 30 de julho às 19:53 UTC e pode ser monitorado na página do Estado do DocuSign (https://status.docusign.com/). Fechamentos híbridos, divulgações e acompanhamento usando a funcionalidade eSign: A interrupção está causando uma grande fila no nosso serviço de documentos, o que impede que as assinaturas eletrônicas sejam aplicadas aos documentos. Isso está impactando os fluxos de trabalho de fechamento híbrido, bem como os Serviços de Divulgação e Fluxos de Acompanhamento que dependem da funcionalidade eSign. Os tomadores de empréstimo podem ainda ser capazes de completar documentos, mas as atualizações da aplicação de assinatura e do status da tarefa não estão processando corretamente neste momento. Entretanto, recomendamos que se proceda com encerramentos de papel e divulgações até que esta questão seja resolvida.

4. 31 Gouere 2026 da 18:33 UTCidentified

   Nossa equipe ainda está investigando a causa básica da questão da disponibilidade do sinal eletrônico DocuSign em ambientes da Blend, mas acreditamos que o impacto esteja relacionado a um alto volume de eventos recebidos pela DocuSign como parte de uma mitigação da recuperação para sua interrupção na quinta-feira à noite, 30 de julho. Nossa equipe está atualmente determinando os melhores próximos passos para implementar uma estratégia de recuperação para retomar a disponibilidade de sinal eletrônico de produção via DocuSign. A experiência atual do mutuário permite a assinatura eletrônica de documentos dentro do DocuSign, no entanto os eventos de assinatura e conclusão de pacotes não estão sendo processados com sucesso entre o DocuSign e o Blend, e como resultado as tarefas de assinatura eletrônica do documento não estão sendo definidas para concluir com sucesso. Vamos compartilhar mais atualizações assim que nossas equipes tiverem mais informações.

5. 31 Gouere 2026 da 19:45 UTCresolved

   Aumentamos a capacidade de processamento da nossa parte para trabalhar através do backlog de eventos de assinatura e conclusão de pacotes entre DocuSign e Blend. Este backlog já está completamente processado, e as tarefas de e-sign do documento estão refletindo o status de conclusão com sucesso. RON, fechamentos híbridos, divulgações e fluxos de acompanhamento usando a funcionalidade eSign estão funcionando normalmente. Obrigado pela vossa paciência enquanto trabalhávamos nesta questão.

Traduzido automaticamente da atualização oficial do incidente.

1. 29 Gouere 2026 da 03:09 UTCinvestigating

   A plataforma de mistura está atualmente indisponível. Nossas equipes de produtos e engenharia estão investigando ativamente e forneceremos atualizações de status frequentes em breve.

2. 29 Gouere 2026 da 03:34 UTCinvestigating

   Estamos no processo de retroceder a versão mais recente que acreditamos que irá desbloquear o acesso à produção. Prevemos que isto seja concluído nos próximos 10 minutos.

3. 29 Gouere 2026 da 04:02 UTCmonitoring

   Confirmamos que o rolo de lançamento de volta abordou a disponibilidade de produção. Confirmamos que essa falha só impacta o acesso à produção de empréstimos na Plataforma Blend Builder e que a Plataforma de Financiamento está totalmente operacional. Estamos acompanhando o desempenho do tráfego na Plataforma Blend Builder, mas esperamos que isso esteja totalmente operacional como às 20h40 da PT.

4. 29 Gouere 2026 da 04:12 UTCmonitoring

   Todos os monitores Blend para o tráfego na plataforma Blend Builder estão mostrando total disponibilidade de produção e recuperação de desempenho e estão totalmente operacionais agora

5. 29 Gouere 2026 da 19:00 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 23 Gouere 2026 da 16:47 UTCinvestigating

   Estamos cientes de um problema que alguns usuários da nossa integração da Encompass Partner Document Delivery (PDD) podem estar experimentando neste momento. Nossa equipe está ativamente investigando a causa raiz e trabalhando para resolver o problema o mais rápido possível. Agradecemos a sua paciência.

2. 23 Gouere 2026 da 17:05 UTCinvestigating

   Estamos cientes de um problema que está causando atrasos com nossa integração da Encompass Partner Document Delivery (PDD). O desempenho da API pode ser atrasado. Nossa equipe está ativamente investigando a causa raiz e trabalhando para resolver o problema o mais rápido possível. Agradecemos a sua paciência.

3. 23 Gouere 2026 da 18:29 UTCinvestigating

   Continuamos a investigar o problema que está causando atrasos com a integração da Encompass Partner Document Delivery (PDD). Durante este tempo, o desempenho da API pode ser atrasado. Estamos a trabalhar para resolver esta questão o mais rapidamente possível. Agradecemos a sua paciência.

4. 23 Gouere 2026 da 20:11 UTCinvestigating

   Nossa equipe de Engenharia continua a investigar ativamente o problema causando atrasos com nossa integração da Encompass Partner Document Delivery (PDD). Estamos a fazer progressos na isolamento da causa principal e estamos a trabalhar para implementar uma resolução o mais rapidamente possível. Continuaremos a fornecer atualizações à medida que mais informações estiverem disponíveis.

5. 23 Gouere 2026 da 22:02 UTCresolved

   A equipe de engenharia da mistura identificou a causa dos atrasos intermitentes que afetam nossa integração da Encompass Partner Document Delivery (PDD) e o serviço voltou ao normal. Nossa equipe de Engenharia implementou mitigação para restaurar a estabilidade e continuará a monitorar o ambiente de perto para garantir que o problema não ocorra novamente. Continuamos também a trabalhar em melhorias adicionais para reforçar ainda mais a resiliência da integração. Obrigado pela vossa paciência enquanto trabalhávamos para resolver esta questão.

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Gouere 2026 da 16:38 UTCinvestigating

   Atualmente estamos investigando um problema onde os usuários podem não ser capazes de enviar pacotes de fechamento para o Blend. Nossa equipe está trabalhando ativamente para identificar a causa raiz e restaurar a funcionalidade normal o mais rápido possível. Continuaremos a acompanhar de perto a situação e a fornecer mais atualizações à medida que mais informações estiverem disponíveis.

2. 22 Gouere 2026 da 17:52 UTCmonitoring

   Identificámos um problema que afecta a capacidade de enviar pacotes de encerramento. Uma correção foi implantada, e estamos monitorando ativamente o sistema para confirmar que a funcionalidade de envio foi totalmente restaurada. Forneceremos outra atualização assim que o problema estiver totalmente resolvido

3. 22 Gouere 2026 da 21:09 UTCresolved

   A solução para esta questão foi agora posta em prática, e acreditamos que o assunto está totalmente resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Mezheven 2026 da 16:37 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. 22 Mezheven 2026 da 17:33 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. 22 Mezheven 2026 da 19:57 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. 22 Mezheven 2026 da 15:00 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. 22 Mezheven 2026 da 18:52 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. 10 Mezheven 2026 da 17:06 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. 10 Mezheven 2026 da 17:35 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. 10 Mezheven 2026 da 18:41 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. 10 Mezheven 2026 da 20:48 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. 10 Mezheven 2026 da 22:02 UTCresolved

   This incident has been resolved.

1. 5 Mezheven 2026 da 19:11 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. 5 Mezheven 2026 da 20:57 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. 5 Mezheven 2026 da 23:22 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. 8 Mezheven 2026 da 14:04 UTCresolved

   This incident has been resolved.

1. 13 Mae 2026 da 15:21 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. 13 Mae 2026 da 15:55 UTCresolved

   This incident has been resolved.

1. 24 Ebrel 2026 da 16:21 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. 24 Ebrel 2026 da 18:56 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. 25 Ebrel 2026 da 13:49 UTCresolved

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

1. 9 Ebrel 2026 da 16:26 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. 9 Ebrel 2026 da 16:32 UTCinvestigating

   We are continuing to investigate this issue.

3. 9 Ebrel 2026 da 18:27 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. 9 Ebrel 2026 da 20:06 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. 9 Ebrel 2026 da 20:07 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. 8 Ebrel 2026 da 16:54 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. 8 Ebrel 2026 da 18:22 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. 8 Ebrel 2026 da 21:36 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. 9 Ebrel 2026 da 14:11 UTCresolved

   This incident has been resolved.

1. 5 Meurzh 2026 da 22:00 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. 5 Meurzh 2026 da 23:03 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. 5 Meurzh 2026 da 23:34 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. 6 Meurzh 2026 da 04:22 UTCresolved

   This incident has been resolved.

1. 2 Meurzh 2026 da 19:48 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. 2 Meurzh 2026 da 20:40 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. 2 Meurzh 2026 da 22:55 UTCresolved

   This incident has been resolved.

1. 11 Cʼhwevrer 2026 da 15:50 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. 11 Cʼhwevrer 2026 da 17:05 UTCresolved

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

1. 20 Genver 2026 da 18:35 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. 20 Genver 2026 da 20:00 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. 21 Genver 2026 da 00:59 UTCresolved

   This incident has been resolved.

1. 20 Genver 2026 da 15:13 UTCinvestigating

   We are currently investigating api failures.

2. 20 Genver 2026 da 16:45 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. 21 Genver 2026 da 00:59 UTCresolved

   This incident has been resolved.

1. 14 Genver 2026 da 13:38 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. 14 Genver 2026 da 14:21 UTCinvestigating

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

3. 14 Genver 2026 da 15:11 UTCidentified

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

4. 14 Genver 2026 da 15:28 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. 14 Genver 2026 da 16:35 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. 14 Genver 2026 da 17:05 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. 14 Genver 2026 da 17:46 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. 14 Genver 2026 da 18:42 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. 14 Genver 2026 da 20:28 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. 14 Genver 2026 da 21:25 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. 14 Genver 2026 da 22:45 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. 15 Genver 2026 da 01:18 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. 15 Genver 2026 da 02:56 UTCmonitoring

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

14. 17 Genver 2026 da 00:17 UTCresolved

    This incident has been resolved.