Blend 中断历史

1. 2026年8月13日 UTC 14:05investigating

   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日 UTC 15:05investigating

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

3. 2026年8月13日 UTC 15:41identified

   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日 UTC 17:30monitoring

   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日 UTC 19:55resolved

   This incident has been resolved.

1. 2026年8月10日 UTC 20:31identified

   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日 UTC 20:43identified

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

3. 2026年8月10日 UTC 21:16identified

   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日 UTC 14:50resolved

   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日 UTC 14:19identified

   我们确认了一个影响现状更新和完成Blend混合和RON关闭软件包关闭能力的问题。 Docusign还在其状态网页https://status.docusign.com/上报告了这些失败. 我们正在密切监测局势,并将在获得更多信息后提供最新情况.

2. 2026年7月31日 UTC 16:12identified

   我们正在继续监测Docusign断电情况,这正在影响在Blend完成混合和RON关闭的关闭软件包的能力。 Docusign正在继续调查,你可以在他们的状态网页https://status.docusign.com/上检查这起事件的现状. 我们正在密切监测局势,并将在获得更多信息后提供最新情况。 与此同时,为了谨慎起见,我们建议将今天可能受影响的任何结案记录.

3. 2026年7月31日 UTC 17:38identified

   经过进一步调查,我们确定了影响结案的两个不同问题: DocuSign目前报告服务退化, 影响公证人完成签名的能力。 这在协调世界时19:53从Jul 30开始,可以在DocuSign Status页面(https://status.docusign.com/)上被监控. 混合关闭、披露和使用电子标志功能跟踪: 禁用导致我们的文档服务排出一排大队,这阻碍了电子签名对文档的应用. 这影响了混合关闭工作流程以及依赖eSign功能的披露服务和后续流程。 借款人可能仍能完成文件,但签名申请和任务状态更新此时处理不当. 与此同时,我们建议在这个问题得到解决之前,继续进行结纸和披露.

4. 2026年7月31日 UTC 18:33identified

   我们的团队仍在调查Blend环境中DocuSign电子信号可用性问题的根源,但我们认为,影响与DocuSign收到的大量事件有关,这是7月30日星期四晚间缓解其停电的恢复措施的一部分。 我们的小组目前正在确定今后的最佳步骤,以执行一项恢复战略,恢复通过DocuSign生产电子信号。 目前借出者-格式化的经验确实允许在DocuSign内电子签名文件,然而在DocuSign和Blend之间没有成功处理签名和包补全事件,因此文件电子签名任务也没有被设定成功完成. 一旦我们的团队掌握了更多信息,我们将分享更多的最新情况.

5. 2026年7月31日 UTC 19:45resolved

   通过DocuSign和Blend之间积压的签名和软件包完成活动,我们提高了我们最终工作的处理能力。 这些积压现已得到全面处理,文件电子签名任务正在成功反映完成状况。 RON,混合关闭,披露,以及使用eSign功能的后继流正常运行. 谢谢你的耐心 在我们努力解决这个问题时.

自动翻译自官方事件更新。

1. 2026年7月29日 UTC 03:09investigating

   Blend平台目前无法使用. 我们的产品和工程小组正在积极调查,我们不久将提供经常的最新情况.

2. 2026年7月29日 UTC 03:34investigating

   我们正在逐步减少我们认为将解除生产准入的最近发布。 我们预计这将在今后10分钟内完成.

3. 2026年7月29日 UTC 04:02monitoring

   我们已经证实,回放量已经解决了生产供应问题。 我们确认,这一停产仅会影响Blend Builder平台的贷款生产,而且借贷平台已全面运作。 我们正监控Blend Builder平台的流量运行情况, 但预计从晚上8点40分起.

4. 2026年7月29日 UTC 04:12monitoring

   Blend Builder平台上所有流量的混合显示器正在显示全能生产可用性和性能恢复,现已全面投入使用

5. 2026年7月29日 UTC 19:00resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月23日 UTC 16:47investigating

   我们意识到一个问题 我们的Encompass Partner Document Production(PDD)整合的一些用户 此时可能正在经历一个问题. 我们的小组正在积极调查根源,并努力尽快解决这一问题。 我们感谢你的耐心.

2. 2026年7月23日 UTC 17:05investigating

   我们意识到一个问题 导致延迟 我们的合作伙伴文件交付(PDD)整合。 API的性能可能会被延迟. 我们的小组正在积极调查根源,并努力尽快解决这一问题。 我们感谢你的耐心.

3. 2026年7月23日 UTC 18:29investigating

   我们正在继续调查造成我们伙伴文件交付整合延误的问题。 在此期间,API的性能可能会被推迟. 我们正在努力尽快解决这一问题。 我们感谢你的耐心.

4. 2026年7月23日 UTC 20:11investigating

   我们的工程组继续积极调查造成我们伙伴文件交付整合延误的问题。 我们正在孤立根源方面取得进展,并正努力尽快执行一项决议。 我们将继续在获得更多信息后提供最新情况.

5. 2026年7月23日 UTC 22:02resolved

   Blend工程组查明了影响我们Encompass伙伴文件交付(PDD)整合的间歇性延误的原因,服务也恢复正常. 我们的工程小组已实施缓解措施来恢复稳定,并将继续密切监测环境,以确保这一问题不再发生。 我们还正在继续努力进行进一步改进,以进一步加强一体化的复原力。 谢谢你在我们努力解决这一问题期间的耐心.

自动翻译自官方事件更新。

1. 2026年7月22日 UTC 16:38investigating

   我们正在调查一个用户可能无法向 Blend 发送关闭包的问题 。 我们的团队正在积极开展工作,以找出根源,并尽快恢复正常的功能。 我们将继续密切监测局势,并在获得更多信息后提供进一步的最新资料.

2. 2026年7月22日 UTC 17:52monitoring

   我们已经确定了一个影响发送收尾包能力的问题。 已部署一个固定装置,我们正在积极监测该系统,以确认发送功能已完全恢复。 问题一解决,我们会再提供最新消息

3. 2026年7月22日 UTC 21:09resolved

   解决这一问题的办法现已得到落实,我们认为这一问题已得到充分解决.

自动翻译自官方事件更新。

1. 2026年6月22日 UTC 16:37monitoring

   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日 UTC 17:33monitoring

   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日 UTC 19:57resolved

   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日 UTC 15:00monitoring

   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日 UTC 18:52resolved

   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日 UTC 17:06investigating

   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日 UTC 17:35investigating

   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日 UTC 18:41investigating

   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日 UTC 20:48monitoring

   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日 UTC 22:02resolved

   This incident has been resolved.

1. 2026年6月5日 UTC 19:11identified

   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日 UTC 20:57identified

   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日 UTC 23:22monitoring

   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日 UTC 14:04resolved

   This incident has been resolved.

1. 2026年5月13日 UTC 15:21investigating

   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日 UTC 15:55resolved

   This incident has been resolved.

1. 2026年4月24日 UTC 16:21identified

   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日 UTC 18:56monitoring

   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日 UTC 13:49resolved

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

1. 2026年4月9日 UTC 16:26investigating

   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日 UTC 16:32investigating

   We are continuing to investigate this issue.

3. 2026年4月9日 UTC 18:27investigating

   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日 UTC 20:06investigating

   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日 UTC 20:07resolved

   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日 UTC 16:54investigating

   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日 UTC 18:22identified

   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日 UTC 21:36monitoring

   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日 UTC 14:11resolved

   This incident has been resolved.

1. 2026年3月5日 UTC 22:00investigating

   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日 UTC 23:03identified

   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日 UTC 23:34monitoring

   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日 UTC 04:22resolved

   This incident has been resolved.

1. 2026年3月2日 UTC 19:48investigating

   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日 UTC 20:40monitoring

   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日 UTC 22:55resolved

   This incident has been resolved.

1. 2026年2月11日 UTC 15:50investigating

   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日 UTC 17:05resolved

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

1. 2026年1月20日 UTC 18:35investigating

   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日 UTC 20:00monitoring

   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日 UTC 00:59resolved

   This incident has been resolved.

1. 2026年1月20日 UTC 15:13investigating

   We are currently investigating api failures.

2. 2026年1月20日 UTC 16:45monitoring

   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日 UTC 00:59resolved

   This incident has been resolved.

1. 2026年1月14日 UTC 13:38investigating

   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日 UTC 14:21investigating

   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日 UTC 15:11identified

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

4. 2026年1月14日 UTC 15:28identified

   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日 UTC 16:35identified

   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日 UTC 17:05monitoring

   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日 UTC 17:46monitoring

   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日 UTC 18:42monitoring

   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日 UTC 20:28monitoring

   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日 UTC 21:25monitoring

    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日 UTC 22:45monitoring

    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日 UTC 01:18monitoring

    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日 UTC 02:56monitoring

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

14. 2026年1月17日 UTC 00:17resolved

    This incident has been resolved.