Blend の障害履歴

1. 2026年8月13日 14:05 UTCinvestigating

   ブレンドは、EPCとPDDを介してEncompassからBlendに流れるクロージングの問題を経験しています。 課題を積極的に調査し、状況が進んでおり、引き続き更新していきます。 KMプラグインを使用したクライアントは不備です.

2. 2026年8月13日 15:05 UTCinvestigating

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

3. 2026年8月13日 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. 2026年8月13日 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. 2026年8月13日 19:55 UTCresolved

   This incident has been resolved.

公式のインシデント更新を自動翻訳しています。

1. 2026年8月10日 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. 2026年8月10日 20:43 UTCidentified

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

3. 2026年8月10日 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. 2026年8月11日 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. 2026年7月31日 14:19 UTCidentified

   ステータス更新に影響を及ぼす問題や、BlのハイブリッドとRON閉鎖のパッケージを完成させる機能を確認しました。 Docusignは、ステータスページでこれらの障害を報告しました。https://status.docusign.com/. 状況を密接に監視し、情報が増えるにつれて更新を行います.

2. 2026年7月31日 16:12 UTCidentified

   現在、Bl の Hybrid と RON のクローズパッケージを完了する機能に影響を及ぼしている Docusign の停電を監視しています。 Docusignは調査を続けており、このインシデントのステータスやステータスページ、https://status.docusign.com/を確認することができます。 状況を密接に監視し、情報が増えるにつれて更新を行います。 その間に、予防策として、今日に影響を与える可能性のある閉鎖を紙やすことをお勧めします.

3. 2026年7月31日 17:38 UTCidentified

   さらなる調査の後、閉鎖に影響を与える2つの別々の問題を特定しました。 Blend Signing room: DocuSignのRONクロージングは、現在、署名を完了するノタリの能力に影響を与えるサービス劣化を報告しています。 19:53 UTCで7月30日に始まり、DocuSignステータスページ(https://status.docusign.com/)で監視できます。 ハイブリッドクローズ、ディスクロージャー、eSign機能の使用フォローアップ: アウトエイジは、eSignatures が文書に適用されないように、文書サービスで大きなキューを引き起こしています。 これは、ハイブリッドクローズワークフローだけでなく、ディスクロージャーサービスに影響を与え、eSign機能に依存するフローをフォローアップします。 借主は文書を完成させることができるかもしれませんが、署名アプリケーションとタスクステータスの更新は、この時点では正しく処理されません。 一方、本件が解決するまでは、紙の閉塞や開示に取り組むことをお勧めします.

4. 2026年7月31日 18:33 UTCidentified

   弊社のチームは引き続き、Blender環境でのDocuSign e-sign可用性の問題の根本的な原因を調査していますが、7月30日(木)の夕方に、DocuSignが受けたイベントの大量に影響が関連していると考えています。 当社のチームは、現在、DocuSignによる生産電子署名の可用性を再開するための回復戦略を実施するための最良の次のステップを決定しています。 現在の借り手に直面している経験はDocuSign内の文書の電子署名を可能にしていますが、署名とパッケージ補完イベントはDocuSignとBl間で正常に処理されず、その結果、文書の電子署名タスクは正常に完了するために設定されません。 弊社チームがより多くの情報を持っているとすぐに更新情報を共有します.

5. 2026年7月31日 19:45 UTCresolved

   DocuSignとBlenderの署名とパッケージ補完イベントのバックログを通して作業するために、最後に処理能力をスケールアップしました。 このバックログは完全に処理され、文書の電子署名タスクは完了ステータスを正常に反映しています。 RON、ハイブリッドクローズ、ディスクロージャー、フォローアップフローは、eSign機能を利用しています。 この問題で働いたときに、忍耐をありがとう.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月29日 3:09 UTCinvestigating

   Blendプラットフォームは現在利用できません。 当社の製品およびエンジニアリングチームは積極的に調査を行い、頻繁なステータス更新を短時間で提供します.

2. 2026年7月29日 3:34 UTCinvestigating

   最新のリリースを振り返る過程で、生産アクセスのブロックを解除します。 今後10分で完成する見込みです.

3. 2026年7月29日 4:02 UTCmonitoring

   リリースロールバックは、生産の在庫状況を把握しました。 このアウトエイジは、Blender Builder Platform のローンに対するローンの生産アクセスにのみ影響を及ぼし、Lending Platform が完全に運用されていることを確認しました。 Blend Builderプラットフォームのトラフィックのパフォーマンスを監視していますが、これは8:40pm PTで完全に動作するように期待しています.

4. 2026年7月29日 4:12 UTCmonitoring

   Blend Builderプラットフォーム上のトラフィックのためのすべてのBlモニターは、フル生産の可用性とパフォーマンスの回復を示しており、現在完全に運用されています

5. 2026年7月29日 19:00 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月23日 16:47 UTCinvestigating

   エンコムパス・パートナー・ドキュメント・デリバリー(PDD)のインテグレーションの一部ユーザーがこの時点で経験する可能性があることを認識しています。 私たちのチームは、根本的な原因を積極的に調査し、可能な限り迅速に問題を解決するために取り組んでいます。 お問い合わせ.

2. 2026年7月23日 17:05 UTCinvestigating

   Encompass Partner Document Delivery (PDD) の統合で遅延を引き起こしている問題を認識しています。 API のパフォーマンスが遅延する場合があります。 私たちのチームは、根本的な原因を積極的に調査し、可能な限り迅速に問題を解決するために取り組んでいます。 お問い合わせ.

3. 2026年7月23日 18:29 UTCinvestigating

   エンコパス・パートナー・ドキュメント・デリバリー(PDD)の統合に伴う遅延を引き起こしている問題の調査を継続しています。 今回はAPIのパフォーマンスが遅れる場合があります。 可能な限り迅速にこの問題を解決します。 お問い合わせ.

4. 2026年7月23日 20:11 UTCinvestigating

   当社のエンジニアリングチームは、Encompass Partner Document Delivery (PDD) の統合で遅延を引き起こした問題を積極的に調査し続けています。 根本原因を隔離し、可能な限り迅速に解決を実践する取り組みを進めています。 今後も、より一層の最新情報をお届けしてまいります.

5. 2026年7月23日 22:02 UTCresolved

   Blend Engineeringチームは、Encompass Partner Document Delivery(PDD)の統合に影響を及ぼす断続的な遅延の原因を特定し、サービスが正常に戻りました。 当社のエンジニアリングチームは、安定性を回復するために緩和を実施し、問題が再発しないように環境を密接に監視します。 また、統合のレジリエンスをさらに強化するために、さらなる改善に取り組んでいます。 この問題の解決に取り組んでいる間、あなたの忍耐をありがとう.

公式のインシデント更新を自動翻訳しています。

1. 2026年7月22日 16:38 UTCinvestigating

   現在、ユーザーが閉じるパッケージをBlに送信できない問題について調査しています。 私たちのチームは、根本原因を特定し、可能な限り迅速に正常な機能を復元するために積極的に取り組んでいます。 今後も状況を監視し、さらなるアップデートを継続的に提供してまいります.

2. 2026年7月22日 17:52 UTCmonitoring

   パッケージを閉じる能力に影響を与える問題を特定しました。 修正が展開され、機能の送信が完全に復元されていることを確認するためにシステムを積極的に監視しています。 問題が完全に解決されると別の更新を提供します

3. 2026年7月22日 21:09 UTCresolved

   この問題の修正が導入され、問題が完全に解決されていると確信しています.

公式のインシデント更新を自動翻訳しています。

1. 2026年6月22日 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. 2026年6月22日 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. 2026年6月22日 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. 2026年6月22日 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. 2026年6月22日 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. 2026年6月10日 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. 2026年6月10日 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. 2026年6月10日 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. 2026年6月10日 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. 2026年6月10日 22:02 UTCresolved

   This incident has been resolved.

1. 2026年6月5日 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. 2026年6月5日 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. 2026年6月5日 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. 2026年6月8日 14:04 UTCresolved

   This incident has been resolved.

1. 2026年5月13日 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. 2026年5月13日 15:55 UTCresolved

   This incident has been resolved.

1. 2026年4月24日 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. 2026年4月24日 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. 2026年4月25日 13:49 UTCresolved

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

1. 2026年4月9日 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. 2026年4月9日 16:32 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026年4月9日 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. 2026年4月9日 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. 2026年4月9日 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. 2026年4月8日 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. 2026年4月8日 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. 2026年4月8日 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. 2026年4月9日 14:11 UTCresolved

   This incident has been resolved.

1. 2026年3月5日 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. 2026年3月5日 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. 2026年3月5日 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. 2026年3月6日 4:22 UTCresolved

   This incident has been resolved.

1. 2026年3月2日 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. 2026年3月2日 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. 2026年3月2日 22:55 UTCresolved

   This incident has been resolved.

1. 2026年2月11日 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. 2026年2月11日 17:05 UTCresolved

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

1. 2026年1月20日 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. 2026年1月20日 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. 2026年1月21日 0:59 UTCresolved

   This incident has been resolved.

1. 2026年1月20日 15:13 UTCinvestigating

   We are currently investigating api failures.

2. 2026年1月20日 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. 2026年1月21日 0:59 UTCresolved

   This incident has been resolved.

1. 2026年1月14日 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. 2026年1月14日 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. 2026年1月14日 15:11 UTCidentified

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

4. 2026年1月14日 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. 2026年1月14日 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. 2026年1月14日 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. 2026年1月14日 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. 2026年1月14日 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. 2026年1月14日 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. 2026年1月14日 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. 2026年1月14日 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. 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日 0:17 UTCresolved

    This incident has been resolved.