Actionstep Status

We are communicating to provide further information on the issues that affected the Actionstep Gmail Add-on platform which started the 1st of June, 2026 and confirm that the issue is now resolved. What happened: The Gmail Add-on was running on the deprecated Google Apps Script Rhino runtime. Google ended support for the Rhino runtime, which caused the add-on to fail before any app logic could execute. What we did: Our team migrated the Apps Script project to the V8 runtime, created a new deployment version, and redeployed the Gmail Add-on. The add-on is now fully operational. What we're doing to prevent this: We have reviewed our runtime dependencies to ensure we are not relying on deprecated infrastructure going forward. We apologise for any disruption this caused and thank you for your patience. Regards, Actionstep Support Team

The root cause of this issue has now been resolved. If you are still experiencing performance degradation and seeing 500 errors, please reach out to support@actionstep.com.

Xero has resolved the issue impacting customers. Xero is now stable and customers should be able to use the platform normally.

We are communicating to provide further information on the outage that affected the Actionstep platform and confirm that the issue is now resolved. This outage started from 9:15am NZT, and prevented user access to the system. Some customers who managed to log in experienced error messages and periods of instability and slowness. It is important to confirm that no data was lost, and the issue related to access to platform only. Our team investigated the issue as the sole priority and released an urgent fix at 9:51am NZT which restored platform access and brought system performance back to normal levels. The Actionstep team appreciate the impact that this outage may have had on your business, and we want to reiterate our commitment to improving the experience of all customers who use the platform. We have identified the root cause of the issue and implemented steps to prevent it from occurring again in future. Regards, Actionstep Support Team

This incident has been resolved. Staging systems are now accessible and back online.

We are pleased to report that Microsoft have resolved the issues that were impacting users who rely on Microsoft Authenticator for multi-factor authentication (MFA) when signing in to Actionstep Practice Management and Legal Accounting. Thank you for your patience during this Microsoft service outage.

**Post-Incident Summary:** United Kingdom – External Connectivity Issue – December 4, 2025 **Incident Overview** On December 4, 2025, some customers in the United Kingdom – primarily those using Sky Broadband – experienced difficulty accessing the Actionstep login page. This login page \(also known as the Launchpad\) is hosted in the ap-southeast-2 region; however, no customer data for UK systems is stored or processed in this region. Once a user selects their system, they are directed to the appropriate UK/region-specific server where their data resides. Our investigation confirmed that this incident was caused entirely by a Sky ISP routing/connectivity issue preventing requests from reaching a wide variety of services hosted in ap-southeast-2. Actionstep also contacted AWS, who confirmed we were one of hundreds of services affected by the Sky outage. There was no issue with the Actionstep platform, AWS infrastructure, or our regional hosting. The issue began at approximately 2:30 pm GMT on December 4, 2025, and normal access was fully restored by December 9, 2025 **Impact** Customers in the UK using Sky Broadband were intermittently or completely unable to reach the Actionstep login page due to Sky’s network routing issue. Customers using other ISPs, or those switching to an alternative connection such as mobile data, were able to access Actionstep normally. At all times, the Actionstep platform itself remained operational. **Resolution** Once Sky resolved their connectivity issue, normal access to the Actionstep login page was restored. Throughout the incident, Actionstep systems continued to perform normally, and users connecting from unaffected networks experienced no disruption. **Next Steps** No Actionstep changes are required, as the root cause was external to our systems and infrastructure. If customers encounter similar symptoms in the future, we recommend testing an alternative connection \(such as a mobile hotspot\) and contacting their ISP to confirm whether a localised network issue is occurring. **Acknowledgement** We recognise that this caused inconvenience for affected customers and appreciate everyone’s patience while Sky resolved their network routing issue. Ensuring reliable access to Actionstep remains our priority.

We are communicating to provide further information on the outage that affected the Actionstep system on 11/11/2025 and confirm that the issue is now resolved. This outage started at 8:30 am EST and prevented user access to the system. Some customers who managed to log in experienced error messages and periods of instability and slowness. It is important to confirm that no data was lost, and the issue is related to platform performance only. Our team investigated the issue as the sole priority and released an urgent fix at 11:20 am EST, which restored platform access and brought system performance back to normal levels. The Actionstep team appreciates the impact that this outage may have had on your business, and we want to reiterate our commitment to improving the experience of all customers who use the platform. We have identified the root cause of the issue and implemented steps to prevent it from occurring again in the future. Regards, Actionstep Support Team

**Post-Incident Summary: US – Actionstep Payments Outage – October 17, 2024** ### Incident Overview On October 17, 2024, Actionstep experienced a service outage affecting the Actionstep Payments platform in the US. A configuration update inadvertently restricted access to a required system resource, which caused payment processing and related services to become temporarily unavailable. ### Impact US-based customers were unable to process payments or access related payment features for approximately one hour. ### Resolution The engineering team identified the configuration issue, restored access to the affected resource, and confirmed that all payment services were operating normally. Service was fully restored once functionality was verified across multiple customer accounts. ### Next Steps We are strengthening our change control and rollout processes to ensure configuration updates are thoroughly tested and deployed safely, with improved monitoring and communication to detect and address issues more quickly. ### Acknowledgement We sincerely apologize for the disruption this caused to our US customers. Maintaining reliable and uninterrupted access to Actionstep Payments remains a priority.

**Post-Incident Summary: EU-West-1 \(UK\) – System Outage – October 17, 2024** ### Incident Overview On October 17, 2024, Actionstep experienced a service outage affecting customers in the UK region \(EU-West-1\). A configuration update inadvertently restricted access to a required system resource, which caused login failures and prevented users from accessing the platform. ### Impact All UK-based customers were unable to log in or use Actionstep for about one hour. Internal testing environments in the same region were also affected. ### Resolution The engineering team identified the configuration issue, restored access to the affected resource, and confirmed that all systems were operating normally. Service was fully restored once access was verified across multiple customer accounts. ### Next Steps We are improving our change control and rollout processes to ensure configuration updates are tested and deployed safely, with enhanced communication and monitoring to detect issues earlier. ### Acknowledgement We sincerely apologize for the disruption this caused to our UK customers. Ensuring consistent access and reliability remains our highest priority.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.

The scheduled maintenance has been completed.