{
"vendor": "Actionstep",
"slug": "actionstep",
"platform": "statuspage",
"status_url": "https://status.actionstep.com",
"last_checked": "2026-09-16T12:28:20Z",
"last_state": "ok",
"history_backfilled": true,
"first_watched": "2026-09-04T07:06:16Z",
"incidents": [
{
"body": "This issue has now been fixed, and our Engineering team has confirmed that the Actionstep Practice Management platform is now stable and fully operational again.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-28T16:18:51.487+12:00",
"resolved_inferred": false,
"started_at": "2026-08-28T12:17:47.187+12:00",
"state": "resolved",
"title": "Practice Management Outage AP-Southeast 2",
"updated_at": "2026-08-28T16:18:51.511+12:00",
"url": "https://stspg.io/ynrrm4zpch64"
},
{
"body": "The issues affecting the Actionstep Practice Management platform have now been resolved. Engineering team confirmed that the services are now fully functional.\n\nWe apologise for any inconvenience this may have caused.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-28T11:45:25.920+12:00",
"resolved_inferred": false,
"started_at": "2026-08-28T11:30:28.050+12:00",
"state": "resolved",
"title": "Practice Management Outage - Ap Southeast 2",
"updated_at": "2026-08-28T11:45:25.940+12:00",
"url": "https://stspg.io/jdbxw4p9cr61"
},
{
"body": "The issues affecting the Actionstep Practice Management platform have now been resolved, and our technical teams have confirmed that all services are now fully functional.\n\nWe would like to apologise for any inconvenience this may have caused.\n\nRegards,\nThe Actionstep Team",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-27T15:13:13.772+12:00",
"resolved_inferred": false,
"started_at": "2026-08-27T14:50:48.000+12:00",
"state": "resolved",
"title": "Server Outage - (AP-Southeast-2) - Users Unable to Login - August 27, 2026",
"updated_at": "2026-08-27T15:13:13.785+12:00",
"url": "https://stspg.io/yz9npn9wzmqs"
},
{
"body": "**Resolved** - Between 00:15\u201301:00 NZST, some Actionstep users were unable to log in to the website. The issue affected users on UK servers, particularly eu-west-1.actionstep.com.\n\nImpact: Login access only. No customer data was affected.\n\nCause: Currently investigating\n\nWorking Solution: Clearing cookies and cache or restarting your machine has shown to resolve the issue.\n\nFor further help, log a ticket at [https://support.actionstep.com](https://support.actionstep.com/)",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-11T01:11:30.000+12:00",
"resolved_inferred": false,
"started_at": "2026-08-11T00:00:41.000+12:00",
"state": "postmortem",
"title": "Issue Identified \u2013 eu-west-1.actionstep.com",
"updated_at": "2026-08-11T01:23:19.719+12:00",
"url": "https://stspg.io/byjxqccdb5rt"
},
{
"body": "Between 19:39\u201322:00 NZST, some Actionstep users were unable to log in to the website. The issue affected users on certain ISPs, particularly Virgin Media.\n\nImpact: Login access only. No customer data was affected or moved.\n\nCause: Likely network or routing changes on the affected ISPs impacting access to the Actionstep login page. Affected customers should contact their ISP to check for recent changes.\n\nData location clarification: No customer data is stored in AP Southeast 2. That region only serves the login page. Once you select your system tile, you're redirected to the data centre where your system actually resides (UK region for UK customers). Your data has not moved and remains stored in your designated region.\n\nWorkaround: If you're still affected, use a mobile hotspot to reach the login page and sign in, then switch back to your normal Wi-Fi once logged in.\n\nFor further help, log a ticket at https://support.actionstep.com",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-31T06:00:00.000+12:00",
"resolved_inferred": false,
"started_at": "2026-07-31T02:23:52.367+12:00",
"state": "resolved",
"title": "Login Disruption (eu-west-1) \u2013 ISP Related Connectivity Issues Jul 30 2026",
"updated_at": "2026-07-31T02:23:52.421+12:00",
"url": "https://stspg.io/xlxx3tp6mwv3"
},
{
"body": "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.\n\nWhat happened:\nThe 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.\n\nWhat we did:\nOur 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.\n\nWhat we're doing to prevent this:\nWe have reviewed our runtime dependencies to ensure we are not relying on deprecated infrastructure going forward.\n\nWe apologise for any disruption this caused and thank you for your patience.\n\nRegards,\nActionstep Support Team",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-04T12:31:20.408+12:00",
"resolved_inferred": false,
"started_at": "2026-06-03T13:38:49.308+12:00",
"state": "resolved",
"title": "Actionstep Gmail Add-on & Logging in to the Actionstep Mobile App using Gmail.",
"updated_at": "2026-06-04T12:31:20.423+12:00",
"url": "https://stspg.io/jlv3bgwst75b"
},
{
"body": "The root cause of this issue has now been resolved. \n\nIf you are still experiencing performance degradation and seeing 500 errors, please reach out to support@actionstep.com.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-22T18:22:44.539+12:00",
"resolved_inferred": false,
"started_at": "2026-05-22T13:25:41.017+12:00",
"state": "resolved",
"title": "Performance degradation and 500 errors",
"updated_at": "2026-05-22T18:22:44.554+12:00",
"url": "https://stspg.io/zzkj7fx4vjpm"
},
{
"body": "Xero has resolved the issue impacting customers. Xero is now stable and customers should be able to use the platform normally.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-11T12:50:04.094+12:00",
"resolved_inferred": false,
"started_at": "2026-05-11T11:53:46.504+12:00",
"state": "resolved",
"title": "Third-Party Service Disruption \u2013 Xero",
"updated_at": "2026-05-11T12:50:04.117+12:00",
"url": "https://stspg.io/2cfxt83h0hw2"
},
{
"body": "We are communicating to provide further information on the outage that affected the Actionstep platform and confirm that the issue is now resolved.\n\nThis 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.\n\nIt is important to confirm that no data was lost, and the issue related to access to platform only.\n\nOur 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.\n\nThe 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.\n\nWe have identified the root cause of the issue and implemented steps to prevent it from occurring again in future.\n\nRegards,\nActionstep Support Team",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-17T10:00:26.541+13:00",
"resolved_inferred": false,
"started_at": "2026-03-17T09:42:40.000+13:00",
"state": "resolved",
"title": "502 bad gateway errors and 504 unexpected API errors",
"updated_at": "2026-03-17T10:00:32.652+13:00",
"url": "https://stspg.io/6xgjfbwlnmk6"
},
{
"body": "This incident has been resolved. Staging systems are now accessible and back online.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-11T21:04:01.000+13:00",
"resolved_inferred": false,
"started_at": "2026-03-11T18:07:52.558+13:00",
"state": "resolved",
"title": "Actionstep Staging System Outage - 11/03/2026",
"updated_at": "2026-03-11T21:04:28.486+13:00",
"url": "https://stspg.io/pnyp3ynyzf5r"
},
{
"body": "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.\n\nThank you for your patience during this Microsoft service outage.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-01-23T19:41:30.875+13:00",
"resolved_inferred": false,
"started_at": "2026-01-23T09:26:14.000+13:00",
"state": "resolved",
"title": "Third-Party Service Outage \u2013 Microsoft 365 / Microsoft Authenticator - 22 January 2026",
"updated_at": "2026-01-23T19:41:30.890+13:00",
"url": "https://stspg.io/c9slg1p461pb"
},
{
"body": "**Post-Incident Summary:** United Kingdom \u2013 External Connectivity Issue \u2013 December 4, 2025\n\n**Incident Overview**    \nOn December 4, 2025, some customers in the United Kingdom \u2013 primarily those using Sky Broadband \u2013 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.\n\nOur 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.\n\nThe issue began at approximately 2:30 pm GMT on December 4, 2025, and normal access was fully restored by December 9, 2025\n\n**Impact**    \nCustomers in the UK using Sky Broadband were intermittently or completely unable to reach the Actionstep login page due to Sky\u2019s network routing issue.\n\nCustomers using other ISPs, or those switching to an alternative connection such as mobile data, were able to access Actionstep normally.\n\nAt all times, the Actionstep platform itself remained operational.\n\n**Resolution**    \nOnce Sky resolved their connectivity issue, normal access to the Actionstep login page was restored.\n\nThroughout the incident, Actionstep systems continued to perform normally, and users connecting from unaffected networks experienced no disruption.\n\n**Next Steps**    \nNo Actionstep changes are required, as the root cause was external to our systems and infrastructure.\n\nIf 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.\n\n**Acknowledgement**    \nWe recognise that this caused inconvenience for affected customers and appreciate everyone\u2019s patience while Sky resolved their network routing issue. Ensuring reliable access to Actionstep remains our priority.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-06T04:43:53.000+13:00",
"resolved_inferred": false,
"started_at": "2025-12-05T03:30:01.000+13:00",
"state": "postmortem",
"title": "Login Disruption (eu-west-1) \u2013 ISP Related Connectivity Issues",
"updated_at": "2025-12-10T04:31:43.942+13:00",
"url": "https://stspg.io/h7y8ccp3b7m5"
},
{
"body": "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.\n\nThis 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.\n\nIt is important to confirm that no data was lost, and the issue is related to platform performance only.\n\nOur 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.\n\nThe 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.\n\nWe have identified the root cause of the issue and implemented steps to prevent it from occurring again in the future.\n\nRegards,\nActionstep Support Team",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-12T05:30:49.414+13:00",
"resolved_inferred": false,
"started_at": "2025-11-12T05:20:18.064+13:00",
"state": "resolved",
"title": "Partial Outage - (US-West-2) - Bad Gateway Error Encountered in Actionstep Navigation \u2013 November 11, 2025",
"updated_at": "2025-11-12T05:30:49.432+13:00",
"url": "https://stspg.io/2s7m0svkw25k"
},
{
"body": "**Post-Incident Summary: US \u2013 Actionstep Payments Outage \u2013 October 17, 2024**\n\n### Incident Overview\n\nOn 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.\n\n### Impact\n\nUS-based customers were unable to process payments or access related payment features for approximately one hour.\n\n### Resolution\n\nThe 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.\n\n### Next Steps\n\nWe 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.\n\n### Acknowledgement\n\nWe sincerely apologize for the disruption this caused to our US customers. Maintaining reliable and uninterrupted access to Actionstep Payments remains a priority.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-07T05:22:39.661+13:00",
"resolved_inferred": false,
"started_at": "2025-11-07T04:58:03.012+13:00",
"state": "postmortem",
"title": "Feature Degridation - us-east-1, us-west-1 - Actionstep Payments Unavailable - Nov 06 2025",
"updated_at": "2025-11-07T10:36:33.236+13:00",
"url": "https://stspg.io/zqgvk4fy42y8"
},
{
"body": "**Post-Incident Summary: EU-West-1 \\(UK\\) \u2013 System Outage \u2013 October 17, 2024**\n\n### Incident Overview\n\nOn 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.\n\n### Impact\n\nAll 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.\n\n### Resolution\n\nThe 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.\n\n### Next Steps\n\nWe 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.\n\n### Acknowledgement\n\nWe sincerely apologize for the disruption this caused to our UK customers. Ensuring consistent access and reliability remains our highest priority.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-06T22:26:52.620+13:00",
"resolved_inferred": false,
"started_at": "2025-11-06T21:45:55.000+13:00",
"state": "postmortem",
"title": "Server Outage - (eu-west-1) - Users Unable to Login - Nov 06 2025",
"updated_at": "2025-11-07T10:35:11.613+13:00",
"url": "https://stspg.io/dkfmzshwb660"
},
{
"body": "**Post-Incident Summary:** Microsoft Dependency Disruption \u2013 Global \u2013 October 29, 2025  \n\n**Incident Overview**    \nOn October 29, 2025, a widespread outage affecting Microsoft\u2019s Azure Front Door service caused latency, timeouts, and service errors across Microsoft 365 and Azure platforms. This impacted Actionstep features that rely on Microsoft services.  \n\n**Impact**    \nDuring the incident, some users experienced difficulty accessing Microsoft-related functionality, including the Outlook Add-in, OneDrive integrations, and Office 365 email services. Service availability improved as Microsoft began recovery efforts, though intermittent issues persisted for some users.  \n\n**Resolution**    \nMicrosoft reloaded configurations and rebalanced traffic across its network to restore full operational capacity. As of 23:20\u202fUTC, Microsoft reported significant progress, and Actionstep services dependent on Microsoft systems have largely returned to normal operation.  \n\n**Next Steps**    \nActionstep will continue monitoring Microsoft\u2019s recovery and ensure all integrations remain stable. We are also reviewing dependency monitoring to improve early detection of third-party disruptions.  \n\n**Acknowledgement**    \nWe appreciate your patience during this incident and apologize for the inconvenience. Ensuring reliable access to all integrated services remains a top priority for Actionstep.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-30T11:55:00.221+13:00",
"resolved_inferred": false,
"started_at": "2025-10-30T05:50:29.191+13:00",
"state": "postmortem",
"title": "Microsoft Outage Impacting All Actionstep Servers \u2014 Oct 29 2025",
"updated_at": "2025-11-07T08:48:21.803+13:00",
"url": "https://stspg.io/b5jwbdxwsk53"
},
{
"body": "On November 6, 2025, Actionstep\u2019s main website \\([actionstep.com](http://actionstep.com)\\) became temporarily unavailable during a scheduled maintenance activity. The maintenance affected only the public website and did not impact access to the Actionstep application.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-22T12:40:39.116+13:00",
"resolved_inferred": false,
"started_at": "2025-10-22T12:05:55.203+13:00",
"state": "postmortem",
"title": "Website Maintenance \u2013 actionstep.com",
"updated_at": "2025-11-07T08:45:22.969+13:00",
"url": "https://stspg.io/yr8v04y6zqdt"
},
{
"body": "**Post-Incident Summary: North America \\(US-East-1\\) \u2013 AWS Outage Impact \u2013 October 20, 2025**\n\n**Incident Overview**    \nOn October 20, 2025, Actionstep services in the US-East-1 region were affected by a widespread outage within Amazon Web Services \\(AWS\\). This incident originated from AWS infrastructure and impacted many cloud-based platforms globally, not just Actionstep. As a result, customers experienced degraded performance and intermittent downtime across the Practice Management and Legal Accounting platforms.\n\n**Impact**    \nThe outage occurred between approximately **9:39 a.m. and 2:19 p.m. MDT**. During this period, some customers in North America experienced slow performance, timeouts, and temporary unavailability of certain features. The issue was entirely due to an AWS infrastructure failure and was not caused by Actionstep systems or changes.\n\n**Resolution**    \nAWS restored functionality in the affected region, after which Actionstep systems automatically recovered. Our engineering team closely monitored the recovery process and validated all environments to confirm full stability and normal operation.  \n  \nFor more information about this outage, please see the AWS website: [Service health - Oct 20, 2025 | AWS Health Dashboard | Global](https://health.aws.amazon.com/health/status)\n\n**Next Steps**    \nWe are reviewing our communication and monitoring processes to ensure faster updates and improved transparency during third-party service disruptions. We are also exploring additional resilience measures to minimize the impact of future upstream provider outages.\n\n**Acknowledgement**    \nWe understand the disruption this caused and apologize for the impact on your firm\u2019s operations. While this incident originated outside of Actionstep\u2019s control, we remain committed to maintaining system reliability and ensuring clear, timely communication during any service interruption.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-21T09:19:47.950+13:00",
"resolved_inferred": false,
"started_at": "2025-10-21T04:39:35.092+13:00",
"state": "postmortem",
"title": "AWS Outage Impacting Us-East-1 - 20 October 2025",
"updated_at": "2025-11-07T06:08:14.961+13:00",
"url": "https://stspg.io/nq41qpkd4fgj"
},
{
"body": "**Post-Incident Summary: Global \u2013 Third-Party Communication Outage \u2013 October 20, 2025**\n\n**Incident Overview**    \nOn October 20, 2025, a widespread AWS outage in the US-East-1 region affected several third-party platforms, including Freshdesk and Intercom. As a result, Actionstep\u2019s Support and Accounting teams were unable to send or receive tickets, live chats, or email communications during the disruption.\n\n**Impact**    \nThe issue occurred between approximately **9:38 a.m. and 10:04 a.m. MDT**. During this time, customers were unable to contact Actionstep Support or Accounting through normal channels. The outage originated from AWS infrastructure supporting Freshdesk and Intercom and did not involve any Actionstep systems.\n\n**Resolution**    \nFreshdesk restored services once AWS resolved the underlying issue. Actionstep teams verified full functionality and resumed normal support operations immediately after recovery.\n\n**Next Steps**    \nWe are reviewing backup communication options and evaluating redundancy for critical customer communication tools to ensure we can continue providing updates and assistance during future third-party outages.\n\n**Acknowledgement**    \nWe understand the inconvenience this caused and apologize for the disruption to your ability to reach our teams. Maintaining reliable communication and support availability is a top priority, and we are taking steps to strengthen our resilience against external service interruptions.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-21T05:04:30.222+13:00",
"resolved_inferred": false,
"started_at": "2025-10-21T04:38:40.000+13:00",
"state": "postmortem",
"title": "Service Interruption \u2013 AWS Outage Impacting Support Systems - 20 October 2025",
"updated_at": "2025-11-07T06:08:15.028+13:00",
"url": "https://stspg.io/j2k1616d650j"
},
{
"body": "### **Post-Incident Summary: Staging Environment Outage \u2013 October 13, 2025**\n\n**Incident Overview**  \nOn October 13, 2025, Actionstep\u2019s Staging environment experienced a temporary service interruption following a system update that affected how application services processed requests.\n\n**Impact**  \nBetween 11:29 \u2013 12:20 UTC and again 22:16 \u2013 22:33 UTC, users accessing the Staging environment encountered errors and were unable to complete normal testing or pre-release activities.\n\n**Resolution**  \nThe engineering team identified the update as the cause and restored service by rolling back to a stable configuration. Functionality was verified and all systems in Staging returned to normal operation.\n\n**Next Steps**  \nWe are refining our deployment and testing procedures to ensure updates to non-production environments are validated without impacting users. Additional automated checks and pre-deployment reviews will be implemented.\n\n**Acknowledgement**  \nWe apologize for the disruption this caused. Maintaining reliable and predictable environments for testing and validation remains a key priority.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-14T11:50:28.279+13:00",
"resolved_inferred": false,
"started_at": "2025-10-14T11:40:07.452+13:00",
"state": "postmortem",
"title": "Staging Environment Outage \u2013 October 13, 2025",
"updated_at": "2025-11-07T06:08:15.093+13:00",
"url": "https://stspg.io/1lpn9xh7h3kv"
},
{
"body": "### **Post-Incident Summary: Production Environment Outage \u2013 October 13, 2025**\n\n**Incident Overview**  \nOn October 13, 2025, Actionstep experienced two brief service interruptions in the Production environment caused by a system update that affected how application services processed requests.\n\n**Impact**  \nCustomers across all regions experienced temporary unavailability between 11:29 \u2013 12:20 UTC and 22:16 \u2013 22:33 UTC. During these times, users were unable to access or perform actions within the platform.\n\n**Resolution**  \nThe engineering team identified the cause and restored service by rolling back the recent update to a stable version. The corrected configuration was rebuilt, tested, and redeployed to confirm full restoration of normal operations.\n\n**Next Steps**  \nWe are enhancing our testing and deployment processes to prevent similar issues. This includes improved validation of system updates, additional automated testing before release, and refined monitoring to detect issues earlier.\n\n**Acknowledgement**  \nWe sincerely apologize for the disruption and appreciate your patience. Maintaining a stable and reliable platform remains our highest priority.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-14T01:27:32.210+13:00",
"resolved_inferred": false,
"started_at": "2025-10-14T00:33:09.000+13:00",
"state": "postmortem",
"title": "System Interruption \u2013 All Regions \u2013 October 13, 2025",
"updated_at": "2025-11-07T06:08:15.154+13:00",
"url": "https://stspg.io/0plf29j0n3y1"
},
{
"body": "We are communicating to provide further information on the issue affecting Reports, document generation, email assignment, and invoice finalization on the eu-west-1 platform on October 3, 2025, and confirm that the issue is now resolved.\n\nThis issue impacted the ability to run reports, finalize invoices, and assign emails via Gmail/Outlook add-ins from 09:00 BST to 10:15 BST, and resulted in tasks being stuck in processing without completion.\n\nIt is important to confirm that no data was lost, and the issue is related to platform performance only.\nOur team investigated the issue as the sole priority during the day and released an urgent fix at 10:15 BST, which restored all functionality to normal operations.\n\nThe Actionstep team appreciates the impact that this issue may have had on your business, and we want to reiterate our commitment to improving the experience of all customers who use the platform.\n\nWe have identified the root cause of the issue and implemented steps to prevent it from occurring again in the future.\n\nRegards,\nActionstep Support Team",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-03T22:22:24.069+13:00",
"resolved_inferred": false,
"started_at": "2025-10-03T21:26:18.672+13:00",
"state": "resolved",
"title": "Issue Identified > Reports, document generation, and the Gmail/Outlook add-ins, which are currently unable to assign emails or finalize invoices.",
"updated_at": "2025-11-07T06:08:15.221+13:00",
"url": "https://stspg.io/144fl186hhjm"
},
{
"body": "**Post-Incident Summary: North America Feature Outage \u2013 September 19, 2025**\n\n**Incident Overview**  \nOn September 19, 2025, Actionstep experienced an outage affecting several features in North America, including document, contact, and custom data management, as well as integrations such as Outlook, Word, and Zapier. Customers encountered 403 error messages during this time.\n\n**Impact**  \nThe issue occurred between 11:45 a.m. MDT and 1:00 p.m. MDT. During this period, customers in North America were unable to reliably use the affected features.\n\n**Resolution**  \nOur engineering team identified the root cause and worked with our partners to remediate the issue. Full functionality was restored by 1:00 p.m. MDT.\n\n**Next Steps**  \nWe are implementing additional safeguards in our change management and quality assurance processes to ensure this type of disruption does not occur again.\n\n**Acknowledgement**  \nWe understand the disruption this caused and apologize for the impact on your firm\u2019s operations. Maintaining system stability and reliability is our top priority, and we are taking steps to strengthen our controls and prevent recurrence.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-20T07:24:42.549+12:00",
"resolved_inferred": false,
"started_at": "2025-09-20T05:45:51.000+12:00",
"state": "postmortem",
"title": "Multiple Feature Outages North America - 19 September 2025",
"updated_at": "2025-11-07T06:08:15.288+13:00",
"url": "https://stspg.io/cltmf76nyvfp"
},
{
"body": "We are providing additional information about the issue affecting Actionstep Practice Management on August 15, 2025, and confirming that the problem has now been resolved.\n\nThe issues began at 11:51AM MDT and were resolved by 12:10PM MDT.\n\nIt is important to confirm that no data was lost and that the issue was related solely to platform performance.\n\nOur team prioritized investigating the problem and restored functionality to normal operations.\n\nThe Actionstep team understands the impact this issue may have had on your business, and we want to reaffirm our commitment to enhancing the experience for all customers using the platform.\n\nRegards,\nActionstep Support Team",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-08-16T06:16:12.650+12:00",
"resolved_inferred": false,
"started_at": "2025-08-16T06:03:01.926+12:00",
"state": "resolved",
"title": "Partial Server Outage - US-East-1 - August 15th 2025",
"updated_at": "2025-11-07T06:08:15.350+13:00",
"url": "https://stspg.io/5n2vvg5d9pq4"
}
]
}