Lone Wolf Outage History

Started Oct 21, 2026, 02:19 PM UTC· resolved Oct 21, 2026, 07:44 PM UTC

1. investigating Oct 21, 2026, 02:19 PM UTC

   Boost, Connect, Leads+ & Spacio are temporarily unavailable due to system maintenance. We’re working to restore service as quickly as possible. We apologize for the inconvenience.

2. identified Oct 21, 2026, 02:43 PM UTC

   We’ve identified new global PHP vulnerabilities that are affecting every company worldwide, and we’re acting right away to protect your business and your data. To do that, several of our applications will be temporarily unavailable while we put the necessary updates and safeguards in place. We know how much you count on these tools, and we’re sorry for the disruption. Our team is working to finish as quickly as we can, without cutting corners on safety. You can see the latest on application availability on our Status Page: https://statuspage.lwolf.com/. We’ll keep it updated as work progresses and services come back online. Thank you for your patience and trust. Keeping your business secure and your tools reliable is our top priority, and we’re right here with you until everything is back up. The Lone Wolf Team

3. identified Oct 21, 2026, 04:54 PM UTC

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

4. identified Oct 21, 2026, 04:55 PM UTC

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

5. resolved Oct 21, 2026, 07:44 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 09, 2026, 11:09 AM UTC· resolved Oct 09, 2026, 11:24 AM UTC

1. identified Oct 09, 2026, 11:09 AM UTC

   The team is actively engaged with SMEs to implement a solution as soon as possible. We will provide the next update within 30 minutes, or sooner if there are significant developments or the issue is mitigated. Incident ticket: ITIL-23528

2. resolved Oct 09, 2026, 11:24 AM UTC

   The System is now fully restored and operational.

Read the full incident report →

Started Aug 11, 2026, 03:36 PM UTC· resolved Aug 12, 2026, 05:43 PM UTC

1. investigating Aug 11, 2026, 03:36 PM UTC

   We are currently investigating an issue affecting TransactionDesk login. Some users may experience significant latency or receive an “Uh oh… Something went wrong” error when attempting to access TransactionDesk. Our team is actively investigating the issue and will provide further updates as more information becomes available.

2. monitoring Aug 11, 2026, 04:33 PM UTC

   The login issues have been mitigated. We are continuing to monitor the service to ensure it remains stable and continues to function as expected.

3. monitoring Aug 12, 2026, 05:42 PM UTC

   Issue is resolved, pending root cause analysis.

4. resolved Aug 12, 2026, 05:43 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 10, 2026, 06:39 PM UTC· resolved Aug 10, 2026, 11:24 PM UTC

1. investigating Aug 10, 2026, 06:39 PM UTC

   We are investigating an issue affecting users when preparing signings. ZipForms is the most affected application. Users may encounter an error that prevents them from continuing with the signing. Workaround: Resume the signing draft from the eSign tab, or select the document from the Documents tab and click eSign. We are actively investigating the issue and will provide updates as more information becomes available.

2. investigating Aug 10, 2026, 07:12 PM UTC

   Our team continues to investigate the issue affecting users when preparing signings. The issue remains ongoing, and no resolution is available at this time. We will provide another update as soon as more information becomes available.

3. investigating Aug 10, 2026, 08:37 PM UTC

   Our team continues to investigate the issue, and we have not yet identified the underlying cause. The issue remains ongoing, and we are actively working toward a resolution. We will provide another update as soon as more information becomes available.

4. identified Aug 10, 2026, 11:03 PM UTC

   The issue has been resolved for most users. Most users should now be able to prepare signings as expected. We have had some reports of transact users still experiencing issues. Our team continues to monitor that situation and will keep users updated.

5. monitoring Aug 10, 2026, 11:22 PM UTC

   The issue has been resolved and all products are now operating as expected for our users. Our teams will continue monitoring the applications to ensure they remain stable and that no further issues occur.

6. resolved Aug 10, 2026, 11:24 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 05, 2026, 05:29 PM UTC· resolved Mar 05, 2026, 06:19 PM UTC

1. investigating Mar 05, 2026, 05:29 PM UTC

   We are aware of an issue where users attempting to log in are receiving an error message. This is preventing users from proceeding with their login. Current Status: Our team is actively investigating the root cause of this issue and working to resolve it as quickly as possible. We apologize for the inconvenience and appreciate your patience. Next Steps: We will provide updates here as soon as we have more information or a resolution.

2. investigating Mar 05, 2026, 05:49 PM UTC

   We are continuing to investigate this issue.

3. monitoring Mar 05, 2026, 06:11 PM UTC

   The issue has been resolved and all users can now log in. We appreciate your patience and support

4. resolved Mar 05, 2026, 06:19 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 04, 2026, 04:03 AM UTC· resolved Feb 04, 2026, 01:40 PM UTC

1. identified Feb 04, 2026, 04:03 AM UTC

   We’re currently experiencing an issue where some forms are not successfully attaching to transactions. Instead of being added, an error message appears. Our team is actively working to identify the cause and resolve the issue as quickly as possible. We’ll share updates as soon as we have more information or a fix in place.

2. identified Feb 04, 2026, 04:04 AM UTC

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

3. identified Feb 04, 2026, 05:03 AM UTC

   IT is still working on restoration of affected objects.

4. identified Feb 04, 2026, 06:04 AM UTC

   Recovery efforts are ongoing. Our technical teams are actively restoring affected system objects to ensure a stable return to service. We are monitoring progress closely and will share a more detailed update once the restoration phase is complete.

5. identified Feb 04, 2026, 06:04 AM UTC

   Recovery efforts are ongoing. Our technical teams are actively restoring affected system objects to ensure a stable return to service. We are monitoring progress closely and will share a more detailed update once the restoration phase is complete.

6. identified Feb 04, 2026, 07:03 AM UTC

   Recovery are still in progress. Our technical teams are restoring affected system components, and we are closely monitoring progress. A detailed update will follow once restoration is complete.

7. identified Feb 04, 2026, 08:10 AM UTC

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

8. identified Feb 04, 2026, 09:16 AM UTC

   Recovery efforts are currently ongoing and we will share updates once restoration is completed.

9. identified Feb 04, 2026, 10:15 AM UTC

   Recovery efforts are actively underway. We will continue to monitor progress and provide updates once services have been fully restored.

10. identified Feb 04, 2026, 11:14 AM UTC

    The team is still working in the recovery process. We will provide an update within the next hour once the system is fully restored.

11. identified Feb 04, 2026, 12:12 PM UTC

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

12. identified Feb 04, 2026, 12:12 PM UTC

    The team will conduct functional testing to ensure the system is fully restored and operating as expected. We will send an update on the next hour.

13. resolved Feb 04, 2026, 01:40 PM UTC

    We have completed the data restoration and synchronization. Team members have confirmed the fix has produced the proper results. Incident resolved.

Read the full incident report →

Started Jan 22, 2026, 10:23 PM UTC· resolved Jan 23, 2026, 06:48 AM UTC

1. investigating Jan 22, 2026, 10:23 PM UTC

   One of our third-party partners is experiencing an issue that may affect the sending of your emails. We’re working closely with them to resolve the problem and will keep you updated. To stay up to date on our progress, you can subscribe to system notifications.

2. monitoring Jan 23, 2026, 05:01 AM UTC

   Our partner has identified the problem within their infrastructure and continue to work through their challenges. We have seen improvement in our mail flow and have worked through thei majority of our backlogged messages as services improve. The situation is not resolved, and the next update from them will be several hours from now. We will update as needs arise or if resolution is reached before that time window. We thank you for your patience while working through this.

3. resolved Jan 23, 2026, 06:48 AM UTC

   Our partner has issued a “Resolved” status on their services. Will continue to monitor for any issues that may arise. We thank you for your patience and understanding during this frustrating issue. There will be no further updates on this issue, unless the provider relapses.

Read the full incident report →

Started Nov 18, 2025, 02:18 PM UTC· resolved Nov 18, 2025, 02:59 PM UTC

1. investigating Nov 18, 2025, 02:18 PM UTC

   Our partner Cloudfare is experiencing an outage that may be impacting your experience with TransactionDesk. We are monitoring the situation closely and will provide updates as they become available. Thank you for your patience. Note: Zipform Edition and Transact are not impacted by this outage and are operational.

2. resolved Nov 18, 2025, 02:59 PM UTC

   Thank you for your patience. Cloudflare has resolved the issue, and TransactionDesk should now be working as expected.

Read the full incident report →

Started Oct 29, 2025, 04:40 PM UTC· resolved Oct 30, 2025, 12:42 AM UTC

1. investigating Oct 29, 2025, 04:40 PM UTC

   We are aware of an issue that may be affecting some users with access Lone Wolf Foundation. Lone Wolf is investigating the issue and working toward a resolution as quickly as possible. We apologize for the inconvenience and thank you for your patience.

2. investigating Oct 29, 2025, 04:55 PM UTC

   We are continuing to investigate this issue.

3. investigating Oct 29, 2025, 06:09 PM UTC

   We are aware of an issue that may be affecting some users with access Lone Wolf Foundation. Lone Wolf is working with its technology providers of the affected solutions as we move toward a resolution as quickly as possible. Some access issues have cleared while we continue to work toward complete restoration. We currently have no ETA of complete resolution at this time. We apologize for the inconvenience and thank you for your patience.

4. investigating Oct 29, 2025, 07:10 PM UTC

   We are continuing to investigate this issue.

5. investigating Oct 29, 2025, 07:11 PM UTC

   Some of our products are currently affected by the ongoing Azure and Microsoft 365 outage. We are monitoring the situation closely and will provide updates as they become available. Thank you for your patience.

6. investigating Oct 29, 2025, 08:25 PM UTC

   We continue to attempt to work around the Microsoft outage in Azure that has affected many of our customers. Microsoft continues its repair of it's services as well to restore service. Our common goal is service restoration in the quickest time possible. We appreciate your patience while we navigate this issue.

7. investigating Oct 29, 2025, 09:34 PM UTC

   We are continuing to investigate this issue.

8. investigating Oct 29, 2025, 09:40 PM UTC

   Service restoration status - Improving. Microsoft has diagnosed and is rolling out repair of the affected environment. This is going to take several more hours to complete (estimated 2 more hours), however we are already seeing significant relief to our impacted services. We are awaiting full completion of restoration by Microsoft. We appreciate your patience and understanding during this difficult time.

9. resolved Oct 30, 2025, 12:42 AM UTC

   Service restoration status - Resolved. Microsoft has completed restoration services. We appreciate your patience and understanding during this difficult time.

Read the full incident report →

Started Sep 26, 2025, 03:32 PM UTC· resolved Sep 26, 2025, 05:45 PM UTC

1. investigating Sep 26, 2025, 03:32 PM UTC

   We are aware of an issue affecting Transactions (TransactionDesk Edition). Lone Wolf is investigating the issue and working toward a resolution as quickly as possible. At any time, you can check the status of this issue at statuspage.lwolf.com. We apologize for the inconvenience and thank you for your patience.

2. monitoring Sep 26, 2025, 04:11 PM UTC

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

3. resolved Sep 26, 2025, 05:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 30, 2025, 12:06 AM UTC· resolved Jul 30, 2025, 12:41 AM UTC

1. investigating Jul 30, 2025, 12:06 AM UTC

   Authentisign is currently experiencing an issue. Our team is aware and working to restore service as quickly as possible.

2. resolved Jul 30, 2025, 12:41 AM UTC

   Service to Authentisign has been fully restored. Thank you for your patience and understanding.

Read the full incident report →

Started Jul 08, 2025, 10:27 PM UTC· resolved Jul 09, 2025, 02:02 AM UTC

1. investigating Jul 08, 2025, 10:27 PM UTC

   We are aware of an intermittent issue of slowness for some clients in LionDesk v1 and v2. We are investigating the issue and working toward a resolution as quickly as possible.

2. monitoring Jul 09, 2025, 01:37 AM UTC

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

3. resolved Jul 09, 2025, 02:02 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 01, 2025, 03:37 PM UTC· resolved Jul 01, 2025, 09:01 PM UTC

1. investigating Jul 01, 2025, 03:37 PM UTC

   Authentisign 2.0, ZipFormPlus, and TransactionDesk performance is currently degraded due to connection issues within Azure and our Data Centers. Our engineers are currently working with Microsoft team to identify the solution. We will keep you posted.

2. investigating Jul 01, 2025, 06:44 PM UTC

   We implemented a workaround to restore service. We are starting to see the integrations working. We are still working with the Microsoft team on a permanent fix. We will keep you posted.

3. resolved Jul 01, 2025, 09:01 PM UTC

   Microsoft made a change on their end that fixed the issue. We have confirmed that the integration between Authentisign 2.0, TransactionDesk, and ZipformPlus is now back to normal performance. We are now waiting for Microsoft to provide the root cause.

Read the full incident report →

Started Jun 19, 2025, 06:37 PM UTC· resolved Jun 19, 2025, 06:47 PM UTC

1. investigating Jun 19, 2025, 06:37 PM UTC

   Our team is actively investigating an issue affecting Front Office (PBGO). We're working to resolve it as quickly as possible and will provide updates here as we learn more. We appreciate your patience and apologize for the disruption.

2. resolved Jun 19, 2025, 06:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 14, 2025, 09:32 PM UTC· resolved Mar 15, 2025, 04:05 AM UTC

1. investigating Mar 14, 2025, 09:32 PM UTC

   We are aware of an issue (PDF server not loading reports) in (Cloud CMA - ). We are investigating the issue and working toward a resolution as quickly as possible.

2. resolved Mar 15, 2025, 04:05 AM UTC

   This incident has been resolved.

Read the full incident report →