Störungsverlauf von Floify

1. 13. Juli 2026 um 17:27 UTCinvestigating

   Wir untersuchen derzeit ein Problem mit Disclosure Delivery für Pakete nach der Veröffentlichung des Encompass-Updates 26.2. Wir werden ein Update bereitstellen, sobald weitere Informationen verfügbar sind.

2. 13. Juli 2026 um 21:19 UTCidentified

   Das Problem wurde identifiziert und unser Team arbeitet daran, so schnell wie möglich eine Lösung dafür zu finden. Ein weiteres Update wird bereitgestellt, wenn der Fix für die Bereitstellung geplant wurde.

3. 14. Juli 2026 um 00:29 UTCmonitoring

   Ein Fix wurde implementiert. Unser Team löst jetzt noch offene Fälle des Problems. Vorwärts, Offenlegungen sollten wie normal durchlaufen werden. Wir werden die Stabilität weiterhin überwachen und morgen ein Update bereitstellen.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 13. Juli 2026 um 16:02 UTCmonitoring

   SMS-Nachrichten, die von Floify gesendet werden, können sich verzögern. Unser SMS-Anbieter Twilio meldet derzeit Netzwerkverzögerungen mit T-Mobile, die sich auf die ausgehende SMS-Kommunikation unseres Systems auswirken können, einschließlich der Multi-Factor Authentication (MFA). Während wir dieses Problem überwachen, können Sie sich bei Schwierigkeiten beim Einloggen aufgrund Ihrer MFA-Methode auf T-Mobile an Ihr Admin-Team oder an unser Support-Team wenden, um beim Zurücksetzen Ihrer Methode zu helfen. Wir empfehlen, zusätzlich zu SMS E-Mails als Methode hinzuzufügen und die Backup-Codes zu verwenden, die bei der Einrichtung der Funktion bereitgestellt werden. Wir werden das Update zur Verfügung stellen, sobald es uns hier zur Verfügung steht.

2. 13. Juli 2026 um 21:05 UTCresolved

   Eine Lösung wurde bereitgestellt und unsere Partner bei Twilio berichten von einer Rückkehr zu der erwarteten Lieferung für T-Mobile. Bitte fühlen Sie sich frei zu erreichen, wenn Sie Hilfe benötigen.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. Juni 2026 um 20:39 UTCresolved

   Es gab ein Problem mit der Funktion zum Upload abgeschlossener Dokumente, die verhinderte, dass abgeschlossene Dokumente korrekt in den Darlehen gespeichert wurden. Wir haben einen Fix veröffentlicht, der das Problem heute Nachmittag löst. Alle Uploads von Dokumenten, die während des Vorfalls versucht wurden, müssen möglicherweise gelöscht und erneut hochgeladen werden, um sicherzustellen, dass sie korrekt gespeichert werden. Wenden Sie sich an support@floify.com, wenn Sie Fragen haben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 1. Juni 2026 um 19:03 UTCidentified

   Wir arbeiten aktiv daran, Latenzprobleme in potenziellen Anwendungen zu lösen. Anwendungen sollten immer noch zugänglich sein, obwohl es zu Verzögerungen beim Laden kommen kann. Benutzer können weiterhin innerhalb der Anwendungen arbeiten, sobald sie geladen haben.

2. 1. Juni 2026 um 20:41 UTCmonitoring

   Ein Fix für dieses Problem wurde implementiert und wir überwachen das System.

3. 1. Juni 2026 um 21:43 UTCresolved

   Dieser Vorfall ist gelöst.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. April 2026 um 17:33 UTCinvestigating

   Wir untersuchen Berichte von Kreditnehmer- und Maklerkonten, die Schwierigkeiten haben, Passwörter zu ändern oder zurückzusetzen.

2. 14. April 2026 um 19:54 UTCresolved

   Wir haben einen Fix implementiert und Benutzer sollten in der Lage sein, ihr Passwort nach Bedarf zu ändern.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 9. März 2026 um 22:52 UTCinvestigating

   Our Byte system tasks are running slower than normal and we are investigating the root cause. Loan creation and other tasks are still processing, and should run without intervention. Our team is looking for resolution to these delays actively.

2. 10. März 2026 um 17:32 UTCinvestigating

   We are seeing some improvement, but are still investigating the root and the persistence of delays. We will post another update later today as more information becomes available.

3. 10. März 2026 um 17:34 UTCinvestigating

   We are continuing to investigate this issue.

4. 11. März 2026 um 15:18 UTCresolved

   We have seen the system operating correctly after implementing a fix. This has been resolved.

1. 2. März 2026 um 23:10 UTCinvestigating

   We are investigating an issue with delivery of Recent Borrower Upload Notifications not being sent correctly.

2. 3. März 2026 um 00:32 UTCresolved

   We have implemented a fix, and email should begin sending again. We are seeing this working now, and we will monitor the fix to ensure stability with this feature.

1. 25. Februar 2026 um 20:03 UTCinvestigating

   We are receiving reports that emails are having delay and delivery issue when coming out from our servers. We are reviewing for a cause and solution actively.

2. 25. Februar 2026 um 20:36 UTCidentified

   The issue has been identified as a delivery issue to Microsoft domains. This appears to be a broad spread issue with Microsoft's servers, although we are working with our mail delivery vendor to identify any options for recourse that we can take. While we await resolution from Microsoft, we recommend monitoring communications with users.

3. 26. Februar 2026 um 00:00 UTCidentified

   We are continuing to monitor this situation and will provide an update tomorrow or as one becomes available. If you need any support or information, please reach out to us at support@floify.com.

4. 26. Februar 2026 um 18:05 UTCmonitoring

   We are seeing delivery to Microsoft email addresses return to normal. We will continue to monitor.

5. 27. Februar 2026 um 16:25 UTCresolved

   We have seen this remain stable after a fix appears to have been made by Microsoft yesterday.

1. 22. Januar 2026 um 22:01 UTCmonitoring

   We have received reports of outages across the Microsoft platform. While our system remains stable, systems connected through Microsoft may experience issue, including email delivery of notifications and MFA codes. If you have any issue accessing the system, reach out to us at support@floify.com. We will provide an update as we find more information about the Microsoft outage.

2. 22. Januar 2026 um 22:59 UTCmonitoring

   We are continuing to monitor this. The impact has remained minimal to our system, but will continue monitoring until we see the all clear from Microsoft.

3. 23. Januar 2026 um 15:58 UTCresolved

   Microsoft has reported that their systems have returned to normal function. Email delivery and other functionality should now work as expected. Please reach out if you need any support.

1. 20. Januar 2026 um 18:07 UTCmonitoring

   Encompass/ICE has reported system latency. This may have an impact on connected systems, including disclosures delivery and processes. We are monitoring the situation with them. If impacted, you can follow along on their status page as well: https://emstatuscenter.elliemae.com/ After the issue is resolved, our team can help restarting any failed tasks.

2. 20. Januar 2026 um 19:38 UTCmonitoring

   Encompass has reported a restoration of functionality. We will restart any failed tasks and monitor for full resolution.

3. 20. Januar 2026 um 22:28 UTCresolved

   This issue has been resolved. Please reach out to support@floify.com if you need any assistance.

1. 9. Januar 2026 um 17:30 UTCinvestigating

   We are currently investigating an app outage preventing users from accessing our systems. We will update this page with more information as it becomes available.

2. 9. Januar 2026 um 17:52 UTCmonitoring

   We have identified the root of the issue and implemented a fix. The system should be accessible soon as it the implemented fix finalizes. We will post a final update once we have seen it fully cleared.

3. 9. Januar 2026 um 18:02 UTCresolved

   We are seeing that this issue is fully resolved. If you are still experiencing issue, clearing your browser's cache and browsing data will resolve any issue. At that, after performing that step, please let us know if you have any further issues by reaching out to us at support@floify.com.

1. 18. Dezember 2025 um 20:57 UTCinvestigating

   We are reviewing reports of duplicate notifications being sent out for milestones checked off from the LOS. We will post an update as we identify the root of the issue.

2. 18. Dezember 2025 um 21:16 UTCidentified

   We have identified the issue is restricted to milestone updates that are also sending out a text message update. We will be rolling out a hotfix shortly to resolve this issue.

3. 18. Dezember 2025 um 23:08 UTCresolved

   We have rolled out a fix for this issue and are seeing milestone communications send out as expected.

1. 11. Dezember 2025 um 16:45 UTCinvestigating

   We are currently investigating reports of issues connecting to Encompass with the integration between our system and theirs. Document uploads, file creation, and disclosures delivery may be impacted. As we have more information, we will provide an update here.

2. 11. Dezember 2025 um 17:28 UTCmonitoring

   A fix has been implemented and we are seeing system tasks catch back up with the sync. We will continue to monitor the integration to ensure there are no outstanding issues.

3. 11. Dezember 2025 um 18:00 UTCresolved

   This incident is resolved. We have seen all tasks catch back up and functionality has been restored.

1. 1. Dezember 2025 um 17:53 UTCidentified

   Our SMS provider, Twilio, has reported delays for SMS messaging, which may impact outbound messaging from our system, including Multi-Factor Authentication (MFA). We are working with our partners to monitor the resolution of the issue and will post updates. In the meantime, if you need help accessing your account, please follow the standard MFA process. We recommend setting your MFA method to have both email and SMS options to ensure access.

2. 1. Dezember 2025 um 21:59 UTCmonitoring

   We are seeing improvement to delivery from most networks. There are still some reports of delay, but have received notice from Twilio of improvements to performance. If you are trying to receive the MFA text message, please give the network a few minutes if you have not received it.

3. 2. Dezember 2025 um 15:58 UTCresolved

   This issue has been resolved and we have seen service restored in full.

1. 20. Oktober 2025 um 14:40 UTCinvestigating

   We are currently experiencing intermittent service interruptions affecting some users, which are due to an ongoing AWS outage impacting multiple services. You can learn more about the outage here: https://health.aws.amazon.com/health/status Our Engineering and Operations teams are actively monitoring the situation and will continue to assess impact to Floify systems. We will provide updates here as we learn more from AWS and our internal assessments. Thank you for your patience.

2. 20. Oktober 2025 um 21:36 UTCmonitoring

   Update - Our systems are now fully operational, and any prior service interruptions due to the AWS outage have been resolved on our end. AWS has confirmed they are in the final stages of restoring full global functionality, which is expected within the next two hours. We are actively monitoring our infrastructure and will continue to post updates if anything changes. Thank you for your patience and understanding.

3. 20. Oktober 2025 um 23:05 UTCresolved

   Amazon is reporting that the issue has now been resolved: https://health.aws.amazon.com/health/status The Floify app is working as expected.

1. 29. September 2025 um 16:26 UTCmonitoring

   We are currently experiencing a partial outage with our SMS provider, Twilio, which is impacting text message delivery across certain mobile networks, including T-Mobile. Some text messages (including notifications and access codes) may fail to send or be delayed. Our team is actively monitoring Twilio’s status and will provide updates as more information becomes available. If you are having issues receiving the code for Multi-Factor Authentication (MFA), you may need to wait longer than normal. If the code does not deliver, request an MFA reset through your standard channel. Thank you for your patience while we work with Twilio to resolve this issue.

2. 29. September 2025 um 18:13 UTCmonitoring

   We received report that this is potentially resolved, but that Twilio is monitoring for recurrence of issue.

3. 29. September 2025 um 21:06 UTCresolved

   This issue is resolved

1. 1. Juli 2025 um 23:31 UTCidentified

   We have identified an issue of degraded performance with some Encompass Adaptors and are working to get them back up and running

2. 1. Juli 2025 um 23:58 UTCresolved

   We have implemented a fix and the encompass integration has resumed full working order. Disclosures documents are resuming their workflows and stalled tasks are picking up automatically. This issue has been resolved.

1. 24. Juni 2025 um 14:31 UTCinvestigating

   We are investigating reports of connectivity issues with the Encompass LOS integration.

2. 24. Juni 2025 um 14:44 UTCidentified

   We will be taking the application offline temporarily to resolve this issue.

3. 24. Juni 2025 um 15:04 UTCmonitoring

   A fix has been implemented and tasks are automatically being restarted, and the Encompass integration is now restored. We have a backlog of tasks that are rerunning, and the any loan files, document pushes, and other Encompass-related tasks are running currently to push over to the LOS. We are monitoring the system and the backlogged tasks in the queue.

4. 24. Juni 2025 um 16:48 UTCresolved

   This issue has been resolved.

1. 12. Juni 2025 um 19:37 UTCinvestigating

   We are receiving reports that various systems, including GCP and AWS, are experiencing outages, resulting in some services within Floify being impacted. We are reviewing these reports actively to identify resolution steps to restore full functionality. Encompass has also reported service issues, which could impact integrations to that system directly. For more information, you can review the ICE status center at the following link: https://emstatuscenter.elliemae.com/

2. 12. Juni 2025 um 20:01 UTCmonitoring

   Google has reported that they have applied fixes to some systems, but that there is no current ETA for full resolution. We are actively monitoring our systems for restoration of service for impacted components, integrations, and tools. As more information becomes available, we will provide update on the situation. Once the issue is externally resolved, we will work to re-push and resolve any outstanding tasks and processes that failed due to this outage.

3. 12. Juni 2025 um 23:02 UTCmonitoring

   We are still seeing certain external services issues persisting, including some functionality with the integration of the Encompass LOS. Once those external services have functionality restored, the system should return to normal operation. We will provide further update of resolution in the morning if no updated become available before then. Once the issue is externally resolved, we will work to re-push and resolve any outstanding tasks and processes that failed due to this outage. For more information specific to Encompass, you can review the ICE status center at the following link: https://emstatuscenter.elliemae.com/

4. 13. Juni 2025 um 15:48 UTCmonitoring

   We are seeing some services restored as our external partners experiencing issue restore functionality. We are currently reviewing our LOS integration connections to ensure they are up and running and are working on repushing tasks to create and connect to loans as we validate services are restored.

5. 13. Juni 2025 um 22:03 UTCresolved

   This issue has been resolved. The outages from GCP and Encompass have been resolved, and we have performed fixes to impacted loans and applications. If you submitted a ticket, we will follow up shortly on that as well.

1. 8. Mai 2025 um 14:58 UTCidentified

   We have found an issue causing encompass disclosures and other eSign packages to appear as blank in the system. We are in the process of rolling back a system update made overnight to resolve this issue.

2. 8. Mai 2025 um 15:17 UTCmonitoring

   We have implemented the fix to this issue and are seeing eSign functionality return to normal. We are monitoring the system to ensure everything is working as expected.

3. 8. Mai 2025 um 15:55 UTCresolved

   This incident has been resolved.