- Detected by Pingoru
- May 13, 2026, 03:21 PM UTC
- Resolved
- May 13, 2026, 03:55 PM UTC
- Duration
- 34m
Affected: Lending Platform
Timeline · 2 updates
-
investigating May 13, 2026, 03:21 PM UTC
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.
-
resolved May 13, 2026, 03:55 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 04:21 PM UTC
- Resolved
- Apr 25, 2026, 01:49 PM UTC
- Duration
- 21h 27m
Affected: Lending PlatformLOS IntegrationsDisclosures and Documents
Timeline · 3 updates
-
identified Apr 24, 2026, 04:21 PM UTC
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.
-
monitoring Apr 24, 2026, 06:56 PM UTC
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.
-
resolved Apr 25, 2026, 01:49 PM UTC
Encompass confirmed the issue on their end has been resolved and all services remain in a stable state.
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 04:26 PM UTC
- Resolved
- Apr 09, 2026, 08:07 PM UTC
- Duration
- 3h 40m
Affected: Lending Platform
Timeline · 5 updates
-
investigating Apr 09, 2026, 04:26 PM UTC
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.
-
investigating Apr 09, 2026, 04:32 PM UTC
We are continuing to investigate this issue.
-
investigating Apr 09, 2026, 06:27 PM UTC
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.
-
investigating Apr 09, 2026, 08:06 PM UTC
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.
-
resolved Apr 09, 2026, 08:07 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Apr 08, 2026, 04:54 PM UTC
- Resolved
- Apr 09, 2026, 02:11 PM UTC
- Duration
- 21h 16m
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2026, 10:00 PM UTC
- Resolved
- Mar 06, 2026, 04:22 AM UTC
- Duration
- 6h 21m
Affected: Disclosures and Documents
Timeline · 4 updates
-
investigating Mar 05, 2026, 10:00 PM UTC
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.
-
identified Mar 05, 2026, 11:03 PM UTC
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.
-
monitoring Mar 05, 2026, 11:34 PM UTC
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.
-
resolved Mar 06, 2026, 04:22 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 07:48 PM UTC
- Resolved
- Mar 02, 2026, 10:55 PM UTC
- Duration
- 3h 7m
Affected: Blend Public API
Timeline · 3 updates
-
investigating Mar 02, 2026, 07:48 PM UTC
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.
-
monitoring Mar 02, 2026, 08:40 PM UTC
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.
-
resolved Mar 02, 2026, 10:55 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 03:50 PM UTC
- Resolved
- Feb 11, 2026, 05:05 PM UTC
- Duration
- 1h 14m
Affected: Blend Close
Timeline · 2 updates
-
investigating Feb 11, 2026, 03:50 PM UTC
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.
-
resolved Feb 11, 2026, 05:05 PM UTC
Resolved but still monitoring. Continue to send Hybrid Closing packages.
Read the full incident report →
- Detected by Pingoru
- Jan 20, 2026, 06:35 PM UTC
- Resolved
- Jan 21, 2026, 12:59 AM UTC
- Duration
- 6h 23m
Affected: Lending Platform
Timeline · 3 updates
-
investigating Jan 20, 2026, 06:35 PM UTC
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.
-
monitoring Jan 20, 2026, 08:00 PM UTC
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.
-
resolved Jan 21, 2026, 12:59 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 20, 2026, 03:13 PM UTC
- Resolved
- Jan 21, 2026, 12:59 AM UTC
- Duration
- 9h 46m
Affected: Lending Platform
Timeline · 3 updates
-
investigating Jan 20, 2026, 03:13 PM UTC
We are currently investigating api failures.
-
monitoring Jan 20, 2026, 04:45 PM UTC
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.
-
resolved Jan 21, 2026, 12:59 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 14, 2026, 01:38 PM UTC
- Resolved
- Jan 17, 2026, 12:17 AM UTC
- Duration
- 2d 10h
Affected: Lending Platform
Timeline · 15 updates
Read the full incident report →
Critical January 13, 2026 - Detected by Pingoru
- Jan 13, 2026, 08:23 PM UTC
- Resolved
- Jan 13, 2026, 09:52 PM UTC
- Duration
- 1h 28m
Affected: Lending Platform
Timeline · 5 updates
-
investigating Jan 13, 2026, 08:23 PM UTC
We are aware of an issue currently impacting all logins(emails and SSO), app creation, eClose, disclosures, and are actively investigating the root cause.
-
investigating Jan 13, 2026, 08:45 PM UTC
We are aware of an issue impacting all logins (email and SSO), application creation, eClose, and disclosures. Our team is actively investigating the root cause and will provide updates as more information becomes available.
-
investigating Jan 13, 2026, 09:01 PM UTC
We are seeing signs of improvement across impacted services. Our Engineering team remains actively engaged and continues to investigate the root cause. We will share additional updates as more information becomes available.
-
investigating Jan 13, 2026, 09:22 PM UTC
We are seeing signs of recovery of Blend Platform logins (email and SSO). Our Engineering team remains actively engaged and continues to investigate Blend Signing Room (RONs) and other affected services. We will share additional updates as more information becomes available.
-
resolved Jan 13, 2026, 09:52 PM UTC
All affected services including Blend Signing Room (RONs) and Public API have been recovered.
Read the full incident report →
- Detected by Pingoru
- Nov 26, 2025, 04:14 AM UTC
- Resolved
- Dec 01, 2025, 04:30 PM UTC
- Duration
- 5d 12h
Affected: Data Reporting API
Timeline · 2 updates
-
investigating Nov 26, 2025, 04:14 AM UTC
Issue affecting our internal reporting data pipelines. No impact to customer business operations, and no data is being lost. However, reporting API's will not contain up-to-date data until the issue is resolved. 11/24 is the last day we have data for at the moment.
-
resolved Dec 01, 2025, 04:30 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 25, 2025, 04:40 PM UTC
- Resolved
- Nov 25, 2025, 09:02 PM UTC
- Duration
- 4h 21m
Affected: LOS Integrations
Timeline · 2 updates
-
monitoring Nov 25, 2025, 04:40 PM UTC
Blend has been made aware of an issue that may have impacted application exports where applications may have been left in "in progress" export status as a result of a temporary issue that has since been resolved. Blend is working to identify a list of potentially impacted applications apply the respective corrections. We will continue to monitor for updates and relay them as soon as they become available. In the meantime, please don't hesitate to reach back with any additional question to [email protected]
-
resolved Nov 25, 2025, 09:02 PM UTC
We have identified the impacted applications and re-exported applications stuck "in progress." We have started sending out impact lists individually to any impacted clients.
Read the full incident report →
- Detected by Pingoru
- Nov 19, 2025, 03:44 PM UTC
- Resolved
- Nov 19, 2025, 04:59 PM UTC
- Duration
- 1h 15m
Affected: Product and Pricing
Timeline · 2 updates
-
identified Nov 19, 2025, 03:44 PM UTC
We want to inform you of an active issue currently affecting the Blend platform. Automated Underwriting (AUS) requests—specifically DU and LP—are not successfully running for clients at this time. Our engineering team is actively investigating the root cause and working to restore AUS functionality as quickly as possible. We will share further updates as soon as more information becomes available. Thank you for your patience while we work to resolve this.
-
resolved Nov 19, 2025, 04:59 PM UTC
AUS Functionality Fully Restored We have successfully resolved and confirmed the full restoration of AUS functionality. You can now run AUS as expected. Please note that this incident was strictly confined to AUS; there were no other known or expected impacts to any other Blend features or user data. Thank you for your patience as our team worked to deploy this fix quickly. We appreciate your partnership.
Read the full incident report →
- Detected by Pingoru
- Nov 03, 2025, 04:37 PM UTC
- Resolved
- Nov 03, 2025, 05:54 PM UTC
- Duration
- 1h 17m
Affected: Lending Platform
Timeline · 3 updates
-
investigating Nov 03, 2025, 04:37 PM UTC
We are currently experiencing an outage affecting the Blend Signing Room, making it inoperable. This issue stems from our vendor responsible for generating the Knowledge-Based Authentication (KBA) security questions. We are in close contact with the vendor and will provide an update immediately once the service is restored. In the interim, we recommend that RON signing appointments be changed to Hybrid or Traditional, or rescheduled for another day.
-
monitoring Nov 03, 2025, 05:44 PM UTC
We are currently experiencing an outage affecting the Blend Signing Room, making it inoperable. This issue stems from our vendor responsible for generating the Knowledge-Based Authentication (KBA) security questions. We are in close contact with the vendor and will provide an update immediately once the service is restored. In the interim, we recommend that RON signing appointments be changed to Hybrid or Traditional, or rescheduled for another day.
-
resolved Nov 03, 2025, 05:54 PM UTC
This incident has been resolved.
Read the full incident report →
Critical October 20, 2025 - Detected by Pingoru
- Oct 20, 2025, 09:27 AM UTC
- Resolved
- Oct 20, 2025, 09:37 PM UTC
- Duration
- 12h 10m
Affected: Lending PlatformLOS Integrations
Timeline · 13 updates
Read the full incident report →
- Detected by Pingoru
- Aug 21, 2025, 06:35 PM UTC
- Resolved
- Aug 22, 2025, 02:28 PM UTC
- Duration
- 19h 52m
Timeline · 6 updates
-
investigating Aug 21, 2025, 06:35 PM UTC
A recent outage from the OneSpan envelope service provider may prevent one-span related process from being completed successfully through Blend such as viewing, updating or issuing envelopes. Blend continues to monitor for updates and will update the status page with relevant updates. In the meantime, please feel free to reach out to [email protected] with any additional questions.
-
identified Aug 21, 2025, 06:35 PM UTC
Blend continues to monitor for updates and recovery
-
monitoring Aug 21, 2025, 07:44 PM UTC
Onespan has made some adjustments on their end and response times are noticeably trending down sharply; however, they remain at 10x normal levels as of 12:34pm. Some Docusign workflows including e-close may be experiencing degradation including eclose as a result of the Onespan outage. Blend will continue to monitor and update the status page as soon as new information becomes available.
-
monitoring Aug 21, 2025, 08:02 PM UTC
onespan response times are closer to nominal (~5s compared to normal ~1s) and continuing to trend down but not fully recovered. queue backlog is coming down as well, with our current worker provisioning we are expecting recovery in 2hr. slowness in eclose and other esign related operations should improve as well as the backlog clears
-
monitoring Aug 21, 2025, 11:32 PM UTC
Failure rates from the OneSpan Envelope Service provider are now back to normal. Blend will continue to monitor.
-
resolved Aug 22, 2025, 02:28 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 20, 2025, 05:44 AM UTC
- Resolved
- Jul 20, 2025, 05:44 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 20, 2025, 05:44 AM UTC
We identified an issue affecting the Builder workflow that resulted in some customers experiencing prolonged loading screens. The issue has since been resolved following a successful hotfix that was deployed tonight. We are actively remediating any impacted applications and have shared detailed impact lists with the affected clients.
Read the full incident report →
- Detected by Pingoru
- Jul 18, 2025, 08:07 PM UTC
- Resolved
- Jul 18, 2025, 08:07 PM UTC
- Duration
- —
Affected: Lending Platform
Timeline · 1 update
-
resolved Jul 18, 2025, 08:07 PM UTC
Timeframe: July 18, 2:19 PM – 2:27 PM CT Status: Resolved Between 2:19 PM and 2:27 PM CT, Blend experienced a service disruption due to an outage from our eSign partner, DocuSign. During this window: eSign packages could not be sent from Blend to borrowers. Borrowers may have been unable to complete eSigning within DocuSign envelopes. The Blend Signing Room experience was also impacted. All systems have since recovered, and services are operating normally. We are continuing to monitor to ensure full stability. We appreciate your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jul 02, 2025, 08:04 PM UTC
- Resolved
- Jul 02, 2025, 09:00 PM UTC
- Duration
- 55m
Affected: Lending Platform
Timeline · 2 updates
-
monitoring Jul 02, 2025, 08:04 PM UTC
We are currently experiencing an interruption in service with eOriginal. This outage is preventing successful eNote operations at this time. If you are actively attempting to send an eNote or an eNote is not able to be signed for same day closings, we recommend papering these out. Our team is actively monitoring the situation and is in communication with eOriginal.
-
resolved Jul 02, 2025, 09:00 PM UTC
The recent eOriginal outage has been resolved. You can now send packages with eNotes, and borrowers are able to sign eNotes as expected. If you experience any further issues, please contact us at [email protected]
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2025, 04:01 PM UTC
- Resolved
- Jun 23, 2025, 05:04 PM UTC
- Duration
- 1h 2m
Affected: LOS Integrations
Timeline · 2 updates
-
investigating Jun 23, 2025, 04:01 PM UTC
We suspect an outage on MortgageBot APIs and are actively trying to contact them to confirm the issue.
-
resolved Jun 23, 2025, 05:04 PM UTC
Blend was able to confirm there was a change made on the Mortgage Bot side during a Disaster Recovery test on Sunday which lead to the error's we were alerted too this morning. The change was reverted and we are no longer seeing the errors on our side.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2025, 07:10 PM UTC
- Resolved
- Jun 18, 2025, 08:58 PM UTC
- Duration
- 1h 48m
Affected: Lending Platform
Timeline · 4 updates
-
investigating Jun 18, 2025, 07:10 PM UTC
We're currently experiencing an interruption in service with one of our eNote vendors, eOriginal. This outage is preventing successful eNote operations at this time. Our team is actively monitoring the situation and is in communication with eOriginal. We will post further updates here as soon as we have more information. Thank you for your patience.
-
investigating Jun 18, 2025, 07:23 PM UTC
We are continuing to investigate this issue.
-
monitoring Jun 18, 2025, 08:48 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 18, 2025, 08:58 PM UTC
This incident has been resolved. Users who attempted to generate or sign an eNote but weren't able to, please try again now.
Read the full incident report →
- Detected by Pingoru
- May 23, 2025, 03:48 PM UTC
- Resolved
- May 23, 2025, 04:31 PM UTC
- Duration
- 42m
Affected: LOS Integrations
Timeline · 2 updates
-
investigating May 23, 2025, 03:48 PM UTC
Velocify is reporting the same issue as last night and we are seeing a high number of lead creation errors. Here is a link to their status page for further information: https://emstatuscenter.elliemae.com/
-
resolved May 23, 2025, 04:31 PM UTC
This has now been resolved by ICE and we are seeing leads being created at a normal rate.
Read the full incident report →
- Detected by Pingoru
- May 23, 2025, 01:35 AM UTC
- Resolved
- May 23, 2025, 04:51 AM UTC
- Duration
- 3h 16m
Affected: LOS Integrations
Timeline · 2 updates
-
investigating May 23, 2025, 01:35 AM UTC
All lead creation through Velocify is currently failing. We have escalated to ICE support and have temporarily paused all events going to Velocify until the issue is resolved.
-
resolved May 23, 2025, 04:51 AM UTC
A fix has been implemented by Velocify. We have unpaused the integration and will continue to monitor for any errors.
Read the full incident report →
- Detected by Pingoru
- May 07, 2025, 01:58 PM UTC
- Resolved
- May 07, 2025, 02:33 PM UTC
- Duration
- 34m
Timeline · 2 updates
-
investigating May 07, 2025, 01:58 PM UTC
Some users are encountering “Your Connection is not Private” error when accessing workspace.blend.com (Settlement Agent Workspace and Blend Signing Room). Current Status: Our team is aware of an issue where users are seeing a browser privacy warning when trying to access workspace.blend.com. Please be assured, the site remains secure. Workaround: Most users can bypass the warning by: 1. Clicking “Advanced” 2. Selecting “Proceed to workspace.identity.blend.com (unsafe)” We understand the message can be concerning, but we assure you the site is still safe to use. We are working to resolve this as quickly as possible and will provide updates here as we make progress. Thank you for your patience.
-
resolved May 07, 2025, 02:33 PM UTC
The issue has been fully resolved. All users should now be able to access workspace.blend.com without encountering security warnings. The SSL certificate for http://workspace.identity.blend.com/ was updated to restore full browser trust. We appreciate your patience and understanding while we worked to resolve this issue.
Read the full incident report →