Blend experienced a minor incident on July 23, 2026 affecting LOS Integrations, lasting 5h 15m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 23, 2026, 04:47 PM UTC
We're aware of an issue that some users of our Encompass Partner Document Delivery (PDD) integration may be experiencing at this time. Our team is actively investigating the root cause and working to resolve the issue as quickly as possible. We appreciate your patience.
- investigating Jul 23, 2026, 05:05 PM UTC
We're aware of an issue that is causing delays with our Encompass Partner Document Delivery (PDD) integration. API performance may be delayed. Our team is actively investigating the root cause and working to resolve the issue as quickly as possible. We appreciate your patience.
- investigating Jul 23, 2026, 06:29 PM UTC
We are continuing to investigate the issue that is causing delays with our Encompass Partner Document Delivery (PDD) integration. During this time API performance may be delayed. We are working to resolve this issue as quickly as possible. We appreciate your patience.
- investigating Jul 23, 2026, 08:11 PM UTC
Our Engineering team continues to actively investigate the issue causing delays with our Encompass Partner Document Delivery (PDD) integration. We are making progress in isolating the root cause and are working to implement a resolution as quickly as possible. We will continue to provide updates as more information becomes available.
- resolved Jul 23, 2026, 10:02 PM UTC
The Blend Engineering Team has identified the cause of the intermittent delays affecting our Encompass Partner Document Delivery (PDD) integration, and service has returned to normal. Our Engineering team has implemented mitigations to restore stability and will continue to monitor the environment closely to ensure the issue does not recur. We are also continuing work on additional improvements to further strengthen the resiliency of the integration. Thank you for your patience while we worked to resolve this issue.