Historique des pannes de Blend

1. 13 août 2026 à 14: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. 13 août 2026 à 15:05 UTCinvestigating

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

3. 13 août 2026 à 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 août 2026 à 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 août 2026 à 19:55 UTCresolved

   This incident has been resolved.

1. 10 août 2026 à 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 août 2026 à 20:43 UTCidentified

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

3. 10 août 2026 à 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 août 2026 à 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 juillet 2026 à 14:19 UTCidentified

   Nous avons confirmé un problème qui affecte la mise à jour de l'état et la capacité de compléter les paquets de fermeture pour les fermetures hybride et RON dans Blend. Docusign a également signalé ces échecs sur sa page de statut, https://status.docusign.com/. Nous suivons la situation de près et fournirons une mise à jour au fur et à mesure que de plus amples renseignements seront disponibles.

2. 31 juillet 2026 à 16:12 UTCidentified

   Nous continuons à surveiller la panne de Docusign qui affecte actuellement la capacité de compléter les paquets de fermeture pour les fermetures hybride et RON dans Blend. Docusign poursuit son enquête et vous pouvez vérifier l'état de cet incident aussi bien sur leur page de statut, https://status.docusign.com/. Nous suivons la situation de près et fournirons une mise à jour au fur et à mesure que de plus amples renseignements seront disponibles. Entre-temps, par précaution, nous recommandons d'effacer toutes les fermetures qui pourraient être touchées aujourd'hui.

3. 31 juillet 2026 à 17:38 UTCidentified

   Après une enquête plus approfondie, nous avons relevé deux questions distinctes touchant les clôtures : Fermetures du RON dans la salle de signature du mélange : DocuSign signale actuellement une dégradation du service qui affecte la capacité des notaires à effectuer une signature. Cela a commencé le 30 juillet à 19h53 UTC et peut être surveillé sur la page d'état de DocuSign (https://status.docusign.com/). Fermetures, divulgations et suivi hybrides utilisant la fonctionnalité de signe électronique : La panne provoque une grande file d'attente dans notre service de documents, ce qui empêche les signatures électroniques d'être appliquées aux documents. Cela a une incidence sur les flux de travail de fermeture hybrides ainsi que sur les services de divulgation et les flux de suivi qui dépendent de la fonctionnalité eSign. Les emprunteurs peuvent encore être en mesure de remplir des documents, mais les mises à jour de l'application de signature et de l'état des tâches ne sont pas encore traitées correctement. Entre-temps, nous recommandons de procéder à la clôture et à la divulgation sur papier jusqu'à ce que cette question soit réglée.

4. 31 juillet 2026 à 18:33 UTCidentified

   Notre équipe enquête encore sur la cause fondamentale du problème de disponibilité de DocuSign e-sign dans les environnements Blend, mais nous croyons que l'impact est lié à un volume élevé d'événements reçus par DocuSign dans le cadre d'une atténuation de récupération de leur panne le jeudi soir, 30 juillet. Notre équipe détermine actuellement les meilleures étapes à suivre pour mettre en œuvre un programme de rétablissement afin de reprendre la production en ligne via DocuSign. L'expérience actuelle de l'emprunteur permet la signature électronique des documents dans DocuSign, mais les événements de signature et d'achèvement des paquets ne sont pas traités avec succès entre DocuSign et Blend, et par conséquent, les tâches de signature électronique des documents ne sont pas réglées avec succès. Nous partagerons plus de mises à jour dès que nos équipes auront plus d'informations.

5. 31 juillet 2026 à 19:45 UTCresolved

   Nous avons augmenté la capacité de traitement à notre fin pour travailler à travers l'arriéré des événements de signature et d'achèvement des paquets entre DocuSign et Blend. Cet arriéré a maintenant été entièrement traité, et les tâches de signature électronique documentent avec succès l'état d'achèvement. RON, les fermetures hybrides, les divulgations et les flux de suivi utilisant la fonctionnalité eSign fonctionnent normalement. Merci de votre patience pendant que nous avons travaillé sur cette question.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 29 juillet 2026 à 03:09 UTCinvestigating

   La plateforme Blend est actuellement indisponible. Nos équipes de produits et d'ingénierie enquêtent activement et nous fournirons sous peu des mises à jour fréquentes.

2. 29 juillet 2026 à 03:34 UTCinvestigating

   Nous sommes en train de faire reculer la dernière version qui, selon nous, débloquera l'accès à la production. Nous prévoyons que cela sera terminé dans les 10 prochaines minutes.

3. 29 juillet 2026 à 04:02 UTCmonitoring

   Nous avons confirmé que le retour à la production avait trait à la disponibilité de la production. Nous avons confirmé que cette panne n'influe que sur l'accès à la production pour les prêts sur la plateforme Blend Builder et que la plate-forme de prêt est pleinement opérationnelle. Nous surveillons les performances du trafic sur la plate-forme Blend Builder, mais nous nous attendons à ce que cela soit pleinement opérationnel comme sur 20h40 PT.

4. 29 juillet 2026 à 04:12 UTCmonitoring

   Tous les moniteurs Blend pour le trafic sur la plate-forme Blend Builder montrent la pleine disponibilité de production et la récupération des performances et sont pleinement opérationnels maintenant

5. 29 juillet 2026 à 19:00 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 23 juillet 2026 à 16:47 UTCinvestigating

   Nous sommes conscients d'un problème que certains utilisateurs de notre intégration encompass Partner Document Delivery (PDD) peuvent rencontrer en ce moment. Notre équipe étudie activement la cause fondamentale et s'emploie à résoudre le problème le plus rapidement possible. Nous apprécions votre patience.

2. 23 juillet 2026 à 17:05 UTCinvestigating

   Nous sommes au courant d'un problème qui cause des retards avec notre intégration encompass partenaire de livraison de documents (PDD). La performance de l'API peut être retardée. Notre équipe étudie activement la cause fondamentale et s'emploie à résoudre le problème le plus rapidement possible. Nous apprécions votre patience.

3. 23 juillet 2026 à 18:29 UTCinvestigating

   Nous continuons d'enquêter sur la question qui cause des retards avec l'intégration de notre partenaire encompass de livraison de documents (PDD). Pendant cette période, les performances de l'API peuvent être retardées. Nous nous efforçons de résoudre ce problème le plus rapidement possible. Nous apprécions votre patience.

4. 23 juillet 2026 à 20:11 UTCinvestigating

   Notre équipe d'Ingénierie continue d'enquêter activement sur la question qui cause des retards avec notre intégration encompass Partner Document Delivery (PDD). Nous progressons dans l'isolement de la cause fondamentale et nous nous efforçons de mettre en œuvre une résolution le plus rapidement possible. Nous continuerons de fournir des mises à jour à mesure que de plus amples renseignements seront disponibles.

5. 23 juillet 2026 à 22:02 UTCresolved

   L'équipe d'ingénierie mixte a identifié la cause des retards intermittents affectant l'intégration de notre service de livraison de documents (PDD) aux partenaires d'Encompass, et le service est revenu à la normale. Notre équipe d'ingénierie a mis en place des mesures d'atténuation pour rétablir la stabilité et continuera de surveiller étroitement l'environnement afin de s'assurer que le problème ne se reproduise pas. Nous poursuivons également nos travaux sur des améliorations supplémentaires afin de renforcer encore la résilience de l'intégration. Merci de votre patience pendant que nous avons travaillé à résoudre ce problème.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 22 juillet 2026 à 16:38 UTCinvestigating

   Nous enquêtons actuellement sur un problème où les utilisateurs pourraient ne pas être en mesure d'envoyer des paquets de fermeture à Blend. Notre équipe s'emploie activement à identifier la cause fondamentale et à restaurer la fonctionnalité normale le plus rapidement possible. Nous continuerons de suivre de près la situation et de fournir d'autres mises à jour à mesure que de plus amples renseignements seront disponibles.

2. 22 juillet 2026 à 17:52 UTCmonitoring

   Nous avons identifié un problème ayant une incidence sur la capacité d'envoyer des paquets de fermeture. Une correction a été déployée, et nous surveillons activement le système pour confirmer que la fonctionnalité d'envoi a été entièrement rétablie. Nous fournirons une autre mise à jour une fois que le problème sera complètement résolu

3. 22 juillet 2026 à 21:09 UTCresolved

   La solution pour cette question a maintenant été déployée, et nous pensons que la question est entièrement résolue.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 22 juin 2026 à 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 juin 2026 à 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 juin 2026 à 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 juin 2026 à 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 juin 2026 à 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 juin 2026 à 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 juin 2026 à 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 juin 2026 à 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 juin 2026 à 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 juin 2026 à 22:02 UTCresolved

   This incident has been resolved.

1. 5 juin 2026 à 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 juin 2026 à 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 juin 2026 à 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 juin 2026 à 14:04 UTCresolved

   This incident has been resolved.

1. 13 mai 2026 à 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 mai 2026 à 15:55 UTCresolved

   This incident has been resolved.

1. 24 avril 2026 à 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 avril 2026 à 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 avril 2026 à 13:49 UTCresolved

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

1. 9 avril 2026 à 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 avril 2026 à 16:32 UTCinvestigating

   We are continuing to investigate this issue.

3. 9 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 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 avril 2026 à 14:11 UTCresolved

   This incident has been resolved.

1. 5 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 04:22 UTCresolved

   This incident has been resolved.

1. 2 mars 2026 à 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 mars 2026 à 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 mars 2026 à 22:55 UTCresolved

   This incident has been resolved.

1. 11 février 2026 à 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 février 2026 à 17:05 UTCresolved

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

1. 20 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 00:59 UTCresolved

   This incident has been resolved.

1. 20 janvier 2026 à 15:13 UTCinvestigating

   We are currently investigating api failures.

2. 20 janvier 2026 à 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 janvier 2026 à 00:59 UTCresolved

   This incident has been resolved.

1. 14 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 15:11 UTCidentified

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

4. 14 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 02:56 UTCmonitoring

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

14. 17 janvier 2026 à 00:17 UTCresolved

    This incident has been resolved.