Time: March 7, 2024, 7:22 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: March 7, 2024, 7:01 p.m.

Status: Monitoring

Update: A fix has been implemented and we are monitoring the results.

Time: March 7, 2024, 6:15 p.m.

Status: Identified

Update: The problem has been identified, and we are currently working on implementing a solution. The error has been isolated to situations where users click the home button or the logo image. Users should not encounter login issues except in these specific scenarios.The error message some users are receiving is unrelated to the identified issue, and there is no indication of unauthorized account access from another location. We will continue to update this page as we have more information.

Time: March 7, 2024, 5:29 p.m.

Status: Investigating

Update: We are currently investigating this issue.

Time: Feb. 23, 2024, 6:30 p.m.

Status: Postmortem

Update: **Issue Summary** From 3:00am to 12:07pm MT, Floify experienced a partial system outage, leading to users being unable to submit disclosures and encountering user access errors. The root cause was due to a code release which was scheduled in the daily system refresh. **Timeline \(all times in Mountain Time\)** * 3:00 AM - Code was deployed with the daily automatic system refresh. * 8:05 AM - Users reported errors when attempting to submit disclosures and inadvertently were logged out of the system. * 8:10 AM - Floify engineers were notified and began their investigation into the issue. * 11:40 AM - Floify engineers identified the root cause of the issue and began to rollback the code. * 12:07 PM - The rollback was completed and the issue was resolved.  **Root Cause** The root cause was determined to be an issue with the code released at 3:00am. Due to this, user sessions were incorrectly handled and some users who were attempting to e-sign were incorrectly logged out. **Resolution and Recovery** This issue was resolved by following internal protocols by reverting to the application instance prior to the 3:00am refresh. **Corrective and Preventative Measures** The following are actions we are taking to address the underlying causes of the issue and to help prevent recurrence and improve response times: Short term: * Rollback application instance to prevent further issues \(completed\)  Long term: * The quality assurance team will persist in developing automated test cases to conduct thorough testing before the release. ‌ Floify is dedicated to continuously adapting and enhancing our technology and processes to prevent service interruptions. We sincerely appreciate your patience and apologize for the impact of this outage. Your business and ongoing support are greatly valued. Sincerely, The Floify Team

Time: Feb. 22, 2024, 7:11 p.m.

Status: Resolved

Update: This issue has been resolved and a root cause analysis will be posted shortly.

Time: Feb. 22, 2024, 6:06 p.m.

Status: Investigating

Update: We are currently investigating an issue with submission of disclosure documents.

Time: Feb. 15, 2024, 5:02 p.m.

Status: Resolved

Update: This incident has been resolved and all impacted disclosures have been processed.

Time: Feb. 15, 2024, 4:23 p.m.

Status: Identified

Update: We've identified an issue with downloading disclosure files. The root cause has been identified, and we are working to deploy the necessary changes to resolve the issue.

Time: Jan. 23, 2024, 11:28 p.m.

Status: Postmortem

Update: ### Floify Service Interruption January 19, 2024 This incident report details the Floify interruption of service that occurred on January 19, 2024. **Issue Summary** From 11:30 AM MT Jan 19 to 7:30 AM MT Jan 20, Floify experienced a partial interruption of service impacting disclosures. Disclosures were not able to be downloaded and therefore could not be added to the loan pipeline and further, signed and completed. The root cause was due to a code release at 3:00 AM MT on Jan 19 that impacted the disclosure functionality. **Timeline \(all times in Mountain Time\)** * 3:00 AM Jan 19 – Floify code was deployed to Production * 11:30 AM Jan 19 – Errors specific to disclosure downloads were identified  * 11:42 AM Jan 19 – Floify engineers were notified and began their investigation into the issue. * 5:30 PM Jan 19 - Floify engineers addressed the issue in the code, and the QA team initiated testing. * 6:13 AM Jan 20  – A code fix was deployed to Production. This addressed the disclosure download issues.  * 6:34 AM Jan 20 - A database update was used to retry the failed disclosure downloads.  **Root Cause** The root cause of this issue was a code fix that affected the functionality between the Floify App and the Floify eSign Service regarding co-mortgagors specifically when creating disclosure signing documents. **Resolution and Recovery** * The issue was resolved by completing a code release that resolved the issue.  * After the code fix release and testing was completed, a database update was used to retry the failed disclosure downloads.  **Corrective and Preventative Measures** The following are actions we are taking to address the underlying causes of the issue and to help prevent recurrence and improve response times: _Short term:_ * Database updates were used to correct failed disclosure downloads. _Long term:_ * The quality assurance team will persist in developing automated test cases to conduct thorough testing before the release. Floify is committed to continually adapting and improving our technology and process to prevent service interruptions. We appreciate your patience and again apologize for the impact of this interruption of service. We thank you for your business and continued support. Sincerely, The Floify Team

Time: Jan. 20, 2024, 2:13 p.m.

Status: Resolved

Update: This incident has been resolved.

Time: Jan. 20, 2024, 1:18 p.m.

Status: Monitoring

Update: A fix has been implemented and we are monitoring the results.

Time: Jan. 19, 2024, 11:59 p.m.

Status: Identified

Update: We've identified interruptions with disclosure packages being downloaded and our developers are currently testing a fix. We will update this page as we have more information.

Time: Nov. 28, 2023, 1:24 a.m.

Status: Resolved

Update: All impacted failed loans have successfully been converted and this issue is resolved.

Time: Nov. 28, 2023, 12:14 a.m.

Status: Identified

Update: Between 3:00pm to 4:30pm MT, some users were unable to start or convert loans. As of 4:30pm MT, the issue has been resolved and there have been no reports of loan start or converting instances. Our team is working on automatically converting failed loans that were impacted. This page will be updated once all failed loans have been converted.