Blend 장애 기록

1. 2026년 8월 13일 오후 2:05 UTCinvestigating

   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. 2026년 8월 13일 오후 3:05 UTCinvestigating

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

3. 2026년 8월 13일 오후 3: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. 2026년 8월 13일 오후 5: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. 2026년 8월 13일 오후 7:55 UTCresolved

   This incident has been resolved.

1. 2026년 8월 10일 오후 8: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. 2026년 8월 10일 오후 8:43 UTCidentified

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

3. 2026년 8월 10일 오후 9: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. 2026년 8월 11일 오후 2: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. 2026년 7월 31일 오후 2:19 UTCidentified

   하이브리드 및 RON의 폐쇄 패키지를 완료하는 상태 업데이트 및 기능에 영향을 미치는 문제를 확인했습니다. Docusign은 또한 자신의 상태 페이지에 이러한 실패를보고, https://status.docusign.com/. 우리는 상황을 밀접하게 감시하고 더 많은 정보로 업데이트를 제공할 것입니다.

2. 2026년 7월 31일 오후 4:12 UTCidentified

   우리는 현재 블렌드에서 하이브리드 및 RON 폐쇄 패키지를 완료 할 수있는 능력에 영향을 미치는 Docusign outage를 모니터링하고 있습니다. Docusign은 조사를 계속하고이 사건의 상태를 확인하고 상태 페이지에 https://status.docusign.com/. 우리는 상황을 밀접하게 감시하고 더 많은 정보로 업데이트를 제공할 것입니다. 그날에 영향을 미칠 수 있는 모든 결산을 권합니다.

3. 2026년 7월 31일 오후 5:38 UTCidentified

   더 조사 후에, 우리는 닫히는에 영향을 미치는 2개의 분리된 문제점을 확인했습니다: Blend Signing Room의 RON 마감: DocuSign은 현재 서명을 완료하기 위해 notaries의 능력에 영향을 미치는 서비스 평가를 보고 있습니다. 이것은 7 월 30에서 시작 19:53 UTC and can be monitored on the DocuSign Status page (https://status.docusign.com/). Hybrid Closes, Disclosures 및 eSign Functionality를 활용하십시오. 정전은 문서에 적용된 eSignatures를 방지하는 문서 서비스에서 큰 큐를 발생시킵니다. 이 하이브리드 폐쇄 워크플로우뿐만 아니라 Disclosure Services에 영향을 미치며 eSign 기능에 의존하는 흐름을 따릅니다. Borrowers는 여전히 문서를 완료 할 수 있지만 서명 응용 프로그램 및 작업 상태 업데이트는이 시간에 올바르게 처리되지 않습니다. 그동안, 우리는 이 문제점이 해결될 때까지 종이 결산 및 파멸으로 진행하는 것이 좋습니다.

4. 2026년 7월 31일 오후 6:33 UTCidentified

   우리 팀은 여전히 혼합 환경에서 DocuSign e-sign 가용성 문제의 뿌리 원인을 조사하지만, 우리는 DocuSign이 목요일 저녁, 7 월 30 일에 회복 완화의 일부로받은 이벤트의 높은 볼륨과 관련된 영향을 믿는다. 우리의 팀은 현재 DocuSign을 통해 생산 e-sign 가용성을 재개하기 위해 복구 전략을 구현하기 위해 최고의 다음 단계를 결정하고 있습니다. DocuSign 내에서 문서의 e-signing을 허용하지만 서명 및 패키지 완료 이벤트는 DocuSign 및 Blend 사이에 성공적으로 처리되지 않으며 문서 e-sign 작업이 성공적으로 완료되지 않습니다. 우리는 우리가 우리의 팀이 더 많은 정보를 가지고 있기 때문에 더 많은 업데이트를 공유할 것입니다.

5. 2026년 7월 31일 오후 7:45 UTCresolved

   우리는 DocuSign와 Blend 사이의 서명 및 패키지 완료 이벤트의 백로를 통해 우리의 끝에 처리 용량을 확장했습니다. 이 백로그는 이제 완전히 처리되고 문서 e-sign 작업은 완료 상태를 성공적으로 반영하고 있습니다. RON, Hybrid Closes, Disclosures 및 eSign 기능을 사용하여 흐름을 따라 정상적으로 작동됩니다. 우리는이 문제를 통해 일하면서 당신의 인내심을 주셔서 감사합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 29일 오전 3:09 UTCinvestigating

   블렌드 플랫폼은 현재 사용할 수 없습니다. 우리의 제품 및 엔지니어링 팀은 적극적으로 투자하고 우리는 곧 잦은 상태를 제공 할 것입니다.

2. 2026년 7월 29일 오전 3:34 UTCinvestigating

   우리는 우리가 믿는 가장 최근 출시를 다시 롤링하는 과정에서 생산 액세스 차단을 해제 할 것입니다. 우리는 다음 10 분에 완료됩니다.

3. 2026년 7월 29일 오전 4:02 UTCmonitoring

   우리는 방출 목록 뒤를 확인했습니다 생산 가용성이 있습니다. 우리는 블렌딩 빌더 플랫폼에 대출을 위한 이 정전만 충격 생산 접근을 확인했으며, Lending Platform은 완전히 운영됩니다. 우리는 블렌드 빌더 플랫폼에서 트래픽의 성능을 모니터링하고 있지만 8 : 40pm PT에 따라 완전히 작동 할 것으로 예상됩니다.

4. 2026년 7월 29일 오전 4:12 UTCmonitoring

   블렌딩 빌더 플랫폼의 트래픽에 대한 모든 블렌드 모니터는 전체 생산 가용성 및 성능 복구를 보여주고 이제 완전히 작동됩니다

5. 2026년 7월 29일 오후 7:00 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 23일 오후 4:47 UTCinvestigating

   Encompass Partner Document Delivery (PDD) 통합의 일부 사용자가이 시간에 경험할 수 있다는 문제가 있습니다. 우리 팀은 뿌리 원인을 적극적으로 조사하고 가능한 한 빨리 문제를 해결하기 위해 노력하고 있습니다. 우리는 당신의 인내를 평가합니다.

2. 2026년 7월 23일 오후 5:05 UTCinvestigating

   Encompass Partner Document Delivery(PDD) 통합으로 지연되는 문제의 인식입니다. API 성능이 지연될 수 있습니다. 우리 팀은 뿌리 원인을 적극적으로 조사하고 가능한 한 빨리 문제를 해결하기 위해 노력하고 있습니다. 우리는 당신의 인내를 평가합니다.

3. 2026년 7월 23일 오후 6:29 UTCinvestigating

   Encompass Partner Document Delivery(PDD) 통합을 통해 지연되는 문제를 조사하고 있습니다. 이 시간 동안 API 성능이 지연 될 수 있습니다. 우리는 가능한 한 빨리이 문제를 해결하기 위해 노력하고 있습니다. 우리는 당신의 인내를 평가합니다.

4. 2026년 7월 23일 오후 8:11 UTCinvestigating

   우리의 엔지니어링 팀은 Encompass Partner Document Delivery (PDD) 통합으로 지연되는 문제를 적극적으로 조사합니다. 우리는 뿌리 원인을 격리하고 가능한 한 빨리 해결하기 위해 노력하고 있습니다. 더 많은 정보로 업데이트를 계속 제공 할 것입니다.

5. 2026년 7월 23일 오후 10:02 UTCresolved

   블렌드 엔지니어링 팀은 Encompass Partner Document Delivery (PDD) 통합에 영향을 미치는 간헐적 지연의 원인을 확인하고 서비스가 정상으로 돌아 왔습니다. 우리의 엔지니어링 팀은 안정성을 복원하기 위해 완화를 구현하고 문제가 재발하지 않도록 환경을 모니터링합니다. 우리는 또한 통합의 탄력성을 더 강화하기 위해 추가 개선 작업을 계속하고 있습니다. 우리는이 문제를 해결하기 위해 일하면서 당신의 인내심을 주셔서 감사합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 22일 오후 4:38 UTCinvestigating

   우리는 현재 사용자가 블렌딩 패키지를 보낼 수없는 문제점을 조사하고 있습니다. 우리의 팀은 뿌리 원인을 확인하고 가능한 한 빨리 정상적인 기능을 복원하기 위해 적극적으로 노력하고 있습니다. 우리는 상황을 밀접하게 감시하고 더 많은 정보를 더 유효한 제공할 것입니다.

2. 2026년 7월 22일 오후 5:52 UTCmonitoring

   우리는 폐쇄 패키지를 보낼 수있는 능력에 영향을 미치는 문제를 발견했습니다. 수정이 배포되었습니다, 우리는 적극적으로 기능을 완전히 복원 된 것을 확인하기 위해 시스템을 모니터링하고 있습니다. 우리는 문제가 완전히 해결되면 또 다른 업데이트를 제공합니다

3. 2026년 7월 22일 오후 9:09 UTCresolved

   이 문제에 대한 수정은 이제 배포되었습니다, 우리는 문제가 완전히 해결된다는 것을 믿는다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 22일 오후 4: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. 2026년 6월 22일 오후 5: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. 2026년 6월 22일 오후 7: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. 2026년 6월 22일 오후 3: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. 2026년 6월 22일 오후 6: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. 2026년 6월 10일 오후 5: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. 2026년 6월 10일 오후 5: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. 2026년 6월 10일 오후 6: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. 2026년 6월 10일 오후 8: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. 2026년 6월 10일 오후 10:02 UTCresolved

   This incident has been resolved.

1. 2026년 6월 5일 오후 7: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. 2026년 6월 5일 오후 8: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. 2026년 6월 5일 오후 11: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. 2026년 6월 8일 오후 2:04 UTCresolved

   This incident has been resolved.

1. 2026년 5월 13일 오후 3: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. 2026년 5월 13일 오후 3:55 UTCresolved

   This incident has been resolved.

1. 2026년 4월 24일 오후 4: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. 2026년 4월 24일 오후 6: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. 2026년 4월 25일 오후 1:49 UTCresolved

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

1. 2026년 4월 9일 오후 4: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. 2026년 4월 9일 오후 4:32 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 4월 9일 오후 6: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. 2026년 4월 9일 오후 8: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. 2026년 4월 9일 오후 8: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. 2026년 4월 8일 오후 4: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. 2026년 4월 8일 오후 6: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. 2026년 4월 8일 오후 9: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. 2026년 4월 9일 오후 2:11 UTCresolved

   This incident has been resolved.

1. 2026년 3월 5일 오후 10: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. 2026년 3월 5일 오후 11: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. 2026년 3월 5일 오후 11: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. 2026년 3월 6일 오전 4:22 UTCresolved

   This incident has been resolved.

1. 2026년 3월 2일 오후 7: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. 2026년 3월 2일 오후 8: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. 2026년 3월 2일 오후 10:55 UTCresolved

   This incident has been resolved.

1. 2026년 2월 11일 오후 3: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. 2026년 2월 11일 오후 5:05 UTCresolved

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

1. 2026년 1월 20일 오후 6: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. 2026년 1월 20일 오후 8: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. 2026년 1월 21일 오전 12:59 UTCresolved

   This incident has been resolved.

1. 2026년 1월 20일 오후 3:13 UTCinvestigating

   We are currently investigating api failures.

2. 2026년 1월 20일 오후 4: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. 2026년 1월 21일 오전 12:59 UTCresolved

   This incident has been resolved.

1. 2026년 1월 14일 오후 1: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. 2026년 1월 14일 오후 2:21 UTCinvestigating

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

3. 2026년 1월 14일 오후 3:11 UTCidentified

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

4. 2026년 1월 14일 오후 3: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. 2026년 1월 14일 오후 4: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. 2026년 1월 14일 오후 5: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. 2026년 1월 14일 오후 5: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. 2026년 1월 14일 오후 6: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. 2026년 1월 14일 오후 8: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. 2026년 1월 14일 오후 9: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. 2026년 1월 14일 오후 10: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. 2026년 1월 15일 오전 1: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. 2026년 1월 15일 오전 2:56 UTCmonitoring

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

14. 2026년 1월 17일 오전 12:17 UTCresolved

    This incident has been resolved.