Action1 Outage History

Action1 is up right now

Pingoru has recorded 75 incidents for Action1: 47 in the last 12 months and 18 in the last 90 days.

Source: status.action1.com

75incidents recorded
47last 12 months
18last 90 days
36 hourstypical duration
Incidents per month
0510AprMayJunJulAugSepOctNov2
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov2%
Pingoru began tracking Action1 in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20262330 of 720 (46%)
May 2026531 of 744 (4%)
June 202633 of 720 (0%)
July 20265202 of 744 (27%)
August 20267147 of 744 (20%)
September 202622 of 720 (0%)
October 2026919 of 744 (3%)
November 202623 of 166 (2%)

Incidents, newest first

Major June 24, 2026 NAM: Login Issue 1h 3m Action1 Application [NAM]

Started Jun 24, 2026, 09:41 AM UTC· resolved Jun 24, 2026, 10:45 AM UTC

  1. investigating Jun 24, 2026, 09:41 AM UTC

    We're investigating NAM login issue

  2. identified Jun 24, 2026, 10:16 AM UTC

    We have identified and resolved the login issue affecting some users. Login functionality has been restored and is operating normally. We are continuing to investigate additional product errors that may be impacting certain features. Our team is actively monitoring the platform and working to identify and address any remaining issues. We will provide further updates as more information becomes available. Thank you for your patience.

  3. resolved Jun 24, 2026, 11:00 AM UTC

    All affected services are operating normally, and the incident has been fully resolved. Our investigation determined that the issue was caused by an unannounced SDK update from a third-party provider. The timing of this external change coincided with a planned internal release, which led to unexpected behavior across parts of the platform. The login issue was resolved first, and additional product errors have since been fully mitigated. We have completed validation across affected systems and are no longer observing any related issues. We are implementing additional safeguards around dependency validation and release monitoring to reduce the likelihood of similar incidents in the future. We apologize for the disruption and appreciate your patience while we worked through this issue.

Read the full incident report →

Minor June 10, 2026 Issue with Remote Sessions 36m Action1 Remote Session North America [NAM]

Started Jun 10, 2026, 08:10 PM UTC· resolved Jun 10, 2026, 08:46 PM UTC

  1. identified Jun 10, 2026, 08:10 PM UTC

    We have received reports that customers are experiencing issues with the remote desktop feature. We have identified the issue and are working towards fixing the root cause.

  2. resolved Jun 10, 2026, 08:46 PM UTC

    We have corrected the issue and remote connections should now be stable.

Read the full incident report →

Minor June 9, 2026 EU: Degraded Platform Performance 1h 25m Action1 Application [EU]

Started Jun 09, 2026, 10:45 AM UTC· resolved Jun 09, 2026, 12:10 PM UTC

  1. investigating Jun 09, 2026, 10:45 AM UTC

    We are currently observing degraded platform performance in the Europe region. Our engineering team is actively investigating and working to restore normal performance as quickly as possible. We will provide updates as more information becomes available.

  2. resolved Jun 09, 2026, 12:52 PM UTC

    The issue has been resolved, and platform performance in the Europe region has returned to normal. The degradation was caused by a temporary service disruption affecting Amazon ElastiCache at our hosting provider. The underlying issue has been resolved, and all systems are now operating normally with no observed performance impact. We will continue to monitor the platform closely to ensure stability.

Read the full incident report →

Minor May 28, 2026 NAM: Remote Session North America Connectivity Issues 3h 15m Action1 Remote Session North America [NAM]

Started May 28, 2026, 06:15 PM UTC· resolved May 28, 2026, 09:30 PM UTC

  1. resolved May 28, 2026, 06:15 PM UTC

    On May 28, 2026, a subset of customers experienced intermittent failures when establishing remote sessions. The issue was caused by an infrastructure component operating in an unhealthy state, which prevented some connection requests from being processed successfully. The affected component was identified and restored, returning service to normal operation. We have also reviewed our monitoring and recovery procedures to reduce the likelihood and duration of similar incidents in the future. We apologize for the disruption and appreciate your patience.

Read the full incident report →

Major May 12, 2026 Action1 Remote Session Outage 15m Action1 Remote Session [AU]

Started May 12, 2026, 10:00 PM UTC· resolved May 12, 2026, 10:15 PM UTC

  1. identified May 12, 2026, 10:09 PM UTC

    An issue with establishing remote connections to endpoints has been identified.

  2. resolved May 12, 2026, 11:10 PM UTC

    The issue has been resolved and remote sessions are working as expected.

Read the full incident report →

Minor May 8, 2026 Endpoint Disconnected Status for Windows Agent 6.0.660.1 1d Action1 Endpoint Interface [NAM], Action1 Endpoint Interface [EU], Action1 Endpoint Interface [AU]

Started May 08, 2026, 09:53 AM UTC· resolved May 09, 2026, 10:00 AM UTC

  1. investigating May 08, 2026, 09:53 AM UTC

    Action1 Windows Agent version 6.0.660.1 may incorrectly report some endpoints as disconnected. We are actively investigating and working on a resolution.

  2. resolved May 11, 2026, 12:50 PM UTC

    The issue affecting Action1 Windows Agent version 6.0.660.1, where some endpoints could be incorrectly reported as disconnected, has been resolved. If you continue to notice any unexpected behavior or endpoint connectivity issues, please contact Action1 Technical Support. Our team will assist you as quickly as possible.

Read the full incident report →

Minor May 6, 2026 NAM: Endpoint Interface Partially Unavailable 1h 50m Action1 Endpoint Interface [NAM]

Started May 06, 2026, 07:54 AM UTC· resolved May 06, 2026, 09:45 AM UTC

  1. investigating May 06, 2026, 07:54 AM UTC

  2. monitoring May 06, 2026, 09:02 AM UTC

  3. resolved May 06, 2026, 10:53 AM UTC

    The database performance degradation that caused automation hangs and overall platform performance degradation earlier today has been mitigated.

Read the full incident report →

Minor May 6, 2026 NAM: Endpoint Interface Partially Unavailable 1h 2m Action1 Endpoint Interface [NAM]

Started May 06, 2026, 02:08 AM UTC· resolved May 06, 2026, 03:11 AM UTC

  1. investigating May 06, 2026, 02:08 AM UTC

  2. resolved May 06, 2026, 03:11 AM UTC

    Several servers responsible for handling Endpoint Interface traffic experienced memory-related anomalies following a minor disruption in the provider’s data center. The affected instances were replaced and migrated to different subnets. Action1 Endpoint Interface operations in the NAM region have been fully restored.

Read the full incident report →

Minor April 20, 2026 NAM: Minor Endpoint Interface Latency Increase 2h Action1 Endpoint Interface [NAM]

Started Apr 20, 2026, 06:30 PM UTC· resolved Apr 20, 2026, 08:30 PM UTC

  1. monitoring Apr 20, 2026, 06:30 PM UTC

    We are currently experiencing minor performance degradation impacting the Action1 Endpoint Interface in the NAM region due to elevated request volume within the NAM data center. The system is actively processing the backlog of requests, and we are closely monitoring recovery to ensure performance returns to expected levels without further impact.

  2. resolved Apr 20, 2026, 09:12 PM UTC

    The previously observed performance degradation impacting the Action1 Endpoint Interface in the NAM region has been resolved. The elevated request queue has been cleared, and performance has returned to normal levels. We will continue monitoring to ensure sustained stability.

Read the full incident report →

Major April 8, 2026 AU Endpoint Interface 28m Action1 Endpoint Interface [AU]

Started Apr 08, 2026, 11:06 PM UTC· resolved Apr 08, 2026, 11:35 PM UTC

  1. investigating Apr 08, 2026, 11:06 PM UTC

    Endpoints may struggle to connect to server.au.action1.com. The problem has been identified and a fix will be deployed shortly.

  2. resolved Apr 08, 2026, 11:50 PM UTC

    The incident preventing endpoints from connecting to Action1 servers has been resolved. We appreciate your prompt response and cooperation.

Read the full incident report →

Minor March 31, 2026 Automation UI Issue 19d 7h Action1 Application [NAM]

Started Mar 31, 2026, 04:25 PM UTC· resolved Apr 19, 2026, 11:59 PM UTC

  1. identified Mar 31, 2026, 04:25 PM UTC

    We are currently experiencing a UI issue where automations may incorrectly display a ‘Running’ status. This is a visual discrepancy only - automations are executing as expected and on schedule. Our team is working to resolve the issue.

  2. resolved Apr 20, 2026, 01:05 PM UTC

    The previously identified UI discrepancy affecting automation status display has been resolved. The issue was limited to incorrect status representation; automation execution remained unaffected and continued to operate as designed. All impacted automation queues have been processed and are now in a healthy state. We appreciate the collaboration from customers who provided reports, which helped expedite the resolution.

Read the full incident report →

Minor March 18, 2026 NAM: Endpoint Interface Partially Unavailable 7h 30m Action1 Endpoint Interface [NAM]

Started Mar 18, 2026, 03:00 PM UTC· resolved Mar 18, 2026, 10:30 PM UTC

  1. investigating Mar 18, 2026, 02:57 PM UTC

    We're investigating the ongoing incident. The issue affects only the Action1 Console. All existing scheduled automations are unaffected and will execute as scheduled.

  2. identified Mar 18, 2026, 05:54 PM UTC

    We have identified the root cause of the issue affecting the Action1 Endpoint Interface in the NAM region. A fix is currently being implemented. During this time, some customers may continue to experience intermittent issues when interacting with the console. Scheduled automations remain unaffected and continue to execute as expected. Our team is actively working to restore full functionality and will provide further updates as progress continues.

  3. monitoring Mar 18, 2026, 10:47 PM UTC

    The issue has been resolved, and full functionality of the Action1 Console has been restored. We are currently monitoring the system to ensure continued stability and performance. All scheduled automations were not impacted and have been executing as expected throughout the incident. If you continue to experience any issues, please contact our support team.

  4. resolved Mar 19, 2026, 12:29 AM UTC

    The issue has been fully resolved, and all systems are operating normally. We sincerely thank our customers for their patience and for the exceptionally precise feedback, which helped us identify and address the problem. We will continue to monitor the system to ensure ongoing stability and performance.

Read the full incident report →

Minor March 17, 2026 NAM: Longer-Than-Expected Execution Times for Automations or Intermittent Issues Selecting Endpoints for Patching 3d 13h Action1 Endpoint Interface [NAM]

Started Mar 17, 2026, 12:30 AM UTC· resolved Mar 20, 2026, 01:53 PM UTC

  1. identified Mar 17, 2026, 12:30 AM UTC

    Some customers may experience longer-than-expected execution times for automations or intermittent issues selecting endpoints for patching. The automation performance fix is expected to be rolled out in the United States March 18th 2026. We are continuing work on the endpoint selection issue affecting patching workflows and expect this to be resolved across all regions March 18th 2026. Our team is actively monitoring the platform and will provide updates as progress continues.

  2. monitoring Mar 18, 2026, 02:24 PM UTC

    We have deployed improvements to address the previously reported automation performance issue in the United States and are actively monitoring the results. We will continue to monitor the platform and provide further updates as needed.

  3. resolved Mar 20, 2026, 01:54 PM UTC

    The issue affecting automation execution times and endpoint selection for patching has been fully resolved. All impacted services have returned to normal performance levels. We will continue to monitor the platform to ensure stability.

Read the full incident report →

Minor March 16, 2026 EU & AU: Intermittent Issues Selecting Endpoints for Patching 3d 18h Action1 Endpoint Interface [EU], Action1 Endpoint Interface [AU]

Started Mar 16, 2026, 09:30 PM UTC· resolved Mar 20, 2026, 03:40 PM UTC

  1. identified Mar 16, 2026, 09:30 PM UTC

    Some customers may experience intermittent issues selecting endpoints for patching. The issue affects only the Action1 Console. All existing scheduled automations are unaffected and will execute as scheduled. We are continuing work on the endpoint selection issue affecting patching workflows and expect this to be resolved across all regions March 19th, 2026. Our team is actively monitoring the platform and will provide updates as progress continues.

  2. resolved Mar 20, 2026, 03:40 PM UTC

    The issue affecting endpoint selection for patching in the EU and AU regions has been resolved. All systems are operating normally. Scheduled automations were not impacted during this incident. We will continue to monitor the platform to ensure ongoing stability.

Read the full incident report →

Minor February 19, 2026 Degraded Performance and Elevated Latency 20m Action1 Application [NAM], Action1 Endpoint Interface [NAM]

Started Feb 19, 2026, 08:35 PM UTC· resolved Feb 19, 2026, 08:55 PM UTC

  1. investigating Feb 19, 2026, 08:25 PM UTC

    We are currently investigating reports of degraded performance impacting the Action1 console. Our team is actively working to identify the root cause and restore normal service as quickly as possible. We will provide updates as more information becomes available.

  2. identified Feb 19, 2026, 08:48 PM UTC

    We have identified an underlying issue with the application. We are rebalancing the cache layer and scaling to restore normal performance. We are also implementing additional safeguards to prevent similar traffic patterns from impacting service. You may experience slower navigation and longer completion times while mitigation efforts are in progress.

  3. resolved Feb 19, 2026, 09:19 PM UTC

    Service has been restored and the Action1 console is operating normally. We do not expect continued performance degradation, and automations executed during the incident are not expected to be impacted or to fail.

Read the full incident report →

Minor February 16, 2026 Degraded Endpoint Performance 30m Action1 Application [AU], Action1 Endpoint Interface [AU]

Started Feb 16, 2026, 07:45 PM UTC· resolved Feb 16, 2026, 08:15 PM UTC

  1. investigating Feb 16, 2026, 07:45 PM UTC

    Degraded performance when performing actions related to configuring and displaying settings and endpoints have been detected in Australia / APAC. Additionally, users may experience issues when logging in to the Action1 console.

  2. resolved Feb 16, 2026, 08:19 PM UTC

    All actions in the console and their underlying backend systems are considered healthy and functional. Thank you for your patience while we resolved the incident.

Read the full incident report →

Minor January 29, 2026 Action1 Endpoint Interface in Europe 45m Action1 Endpoint Interface [EU]

Started Jan 29, 2026, 01:45 PM UTC· resolved Jan 29, 2026, 02:30 PM UTC

  1. resolved Jan 29, 2026, 01:45 PM UTC

    During the identified period, some endpoints experienced intermittent inability to reach Action1 servers. We appreciate the reports submitted to our support team — the detailed information you provided helped us quickly identify and eliminate the service degradation. All services are now operating normally.

Read the full incident report →

Minor December 10, 2025 Partial Outage - Endpoint Interface & Remote Session Service 9h 29m Action1 Endpoint Interface [NAM], Action1 Remote Session North America [NAM]

Started Dec 10, 2025, 10:30 PM UTC· resolved Dec 11, 2025, 08:00 AM UTC

  1. investigating Dec 10, 2025, 10:30 PM UTC

    Customer reports of issues managing endpoints and dropped remote sessions. We are working to remedy this and appreciate your patience.

  2. investigating Dec 11, 2025, 01:06 AM UTC

    We are continuing to experience issues with caching related to the Endpoint Interface component in NAM. We are rolling out fixes currently and expect a return to normal operations as updates are applied.

  3. resolved Dec 11, 2025, 09:07 AM UTC

    The issue affecting the Endpoint Interface component and Remote Session Service in the NAM region has been fully resolved. Caching-related problems have been corrected, and all systems have returned to normal operation. We have verified stability across the impacted services, and no further disruptions are expected. Thank you for your patience while we worked to restore optimal performance.

Read the full incident report →

Major December 5, 2025 Action1 Endpoint Interface - Europe 49m Action1 Endpoint Interface [EU]

Started Dec 05, 2025, 08:13 AM UTC· resolved Dec 05, 2025, 09:02 AM UTC

  1. investigating Dec 05, 2025, 08:13 AM UTC

  2. resolved Dec 05, 2025, 09:02 AM UTC

Read the full incident report →

Major December 4, 2025 Action1 Application Europe 2h 26m Action1 Application [EU], Action1 Endpoint Interface [EU]

Started Dec 04, 2025, 09:18 AM UTC· resolved Dec 04, 2025, 11:45 AM UTC

  1. investigating Dec 04, 2025, 09:18 AM UTC

    We're investigating the ongoing incident

  2. resolved Dec 04, 2025, 12:08 PM UTC

    We have fully resolved the effects of the incident, and all teams are now focused on identifying its root cause. Thank you for your feedback and patience.

Read the full incident report →

Minor December 3, 2025 Action1 Endpoint Interface in Australia 1h Action1 Endpoint Interface [AU]

Started Dec 03, 2025, 09:00 AM UTC· resolved Dec 03, 2025, 10:00 AM UTC

  1. resolved Dec 03, 2025, 09:00 AM UTC

    Earlier today, some customers in the Australia region experienced issues where Action1 agents were unable to establish connectivity with the service. We identified the cause as insufficient backend capacity and scaled the required resources. All systems are now fully operational. Thank you for your patience and feedback.

Read the full incident report →

Major November 18, 2025 Action1 Website - Cloudflare-related outage 1h Action1 Website

Started Nov 18, 2025, 12:00 PM UTC· resolved Nov 18, 2025, 01:00 PM UTC

  1. resolved Nov 18, 2025, 12:00 PM UTC

    Action1 was unavailable due to the Cloudflare global outage from 12:00 PM to 1:00 PM time. At this time all systems are operational.

Read the full incident report →

Minor November 6, 2025 Action1 Application Degraded Performance 15m Action1 Application [NAM]

Started Nov 06, 2025, 09:30 PM UTC· resolved Nov 06, 2025, 09:45 PM UTC

  1. investigating Nov 06, 2025, 09:35 PM UTC

    We are handling degraded performance of the Action1 application due to elevated usage. Logging in may result in errors or delayed loading. Thank you for your patience.

Read the full incident report →

Major October 31, 2025 Action1 Endpoint Interface 3h 45m Action1 Application [NAM], Action1 Endpoint Interface [NAM]

Started Oct 31, 2025, 05:54 PM UTC· resolved Oct 31, 2025, 09:39 PM UTC

  1. investigating Oct 31, 2025, 05:54 PM UTC

    We've identified an issue with our endpoints interface. A solution is being deployed now and we expect normal behavior to return shortly.

  2. investigating Oct 31, 2025, 08:01 PM UTC

    The steps taken earlier have not resolved the core issue. Our team is working towards a solution and will continue to provide updates.

  3. resolved Oct 31, 2025, 09:40 PM UTC

    The issue has been fully resolved. Earlier today, an unintended spike in traffic caused temporary service degradation resembling a DoS event. Our team identified and mitigated the source, restoring system stability. Please note that cache recovery and agent-to-server reconnections took longer than expected, as we performed the restoration gradually to maintain overall platform stability. All systems are now operating normally. Thank you for your patience and understanding.

Read the full incident report →

Minor October 20, 2025 Major Service Outage – Widespread Cloud Provider Failure 13h 57m Action1 Application [NAM], Action1 Endpoint Interface [NAM], Action1 REST API [NAM]

Started Oct 20, 2025, 01:17 PM UTC· resolved Oct 21, 2025, 03:15 AM UTC

  1. identified Oct 20, 2025, 07:27 AM UTC

    We are currently experiencing a major outage affecting Action1 platform services. This incident began as a result of an ongoing infrastructure issue impacting Amazon Web Services (AWS). We are monitoring the situation and are on standby for a swift recovery once the infrastructure issue is resolved.

  2. monitoring Oct 20, 2025, 08:37 AM UTC

    Services have started to recover after the major outage affecting AWS’s US-EAST-1 region. At this time, [https://app.action1.com](https://app.action1.com) and related platform services are accessible, and systems appear to be stabilizing. We are continuing to closely monitor platform health and underlying AWS services for any further disruptions. While this initial restoration is promising, there may still be intermittent issues as AWS fully resolves the incident on their end and our systems stabilize.

  3. monitoring Oct 20, 2025, 01:21 PM UTC

    What we’re doing: We’ve mitigated broadly and are routing workloads to healthy capacity. Queued jobs are processing automatically as capacity returns. Upstream note: AWS has made progress, but EC2 in us-east-1 is not yet fully recovered, so we’re keeping this incident open. Customer action: None required. Retries happen automatically; your existing schedules and tasks will catch up.

  4. monitoring Oct 20, 2025, 05:30 PM UTC

    We are continuing to work towards infrastructure stability and monitoring AWS for updates.

  5. investigating Oct 21, 2025, 02:18 AM UTC

    We are aware of an ongoing issue affecting agents communicating with Action1's backend. We will provide updates as we narrow in on root causes.

  6. monitoring Oct 21, 2025, 03:03 AM UTC

    We have identified the root cause and have deployed a hotfix. We are continuing to monitor our infrastructure and will update the status of this incident as we stabilize.

  7. resolved Oct 21, 2025, 04:10 AM UTC

    While we will continue our monitoring of the situation, the Action 1 application and infrastructure are remaining stable. Thank you for your patience as we recovered from yesterday's regional outages.

Read the full incident report →