Action1 Outage History

Action1 is up right now

Action1 had 9 outages in the last 2 years totaling 515h 26m of downtime — averaging 0.4 incidents per month.

There were 9 Action1 outages since March 31, 2026 totaling 515h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.action1.com

Minor June 10, 2026

Issue with Remote Sessions

Detected by Pingoru
Jun 10, 2026, 08:10 PM UTC
Resolved
Jun 10, 2026, 08:46 PM UTC
Duration
36m
Timeline · 2 updates
  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

Detected by Pingoru
Jun 09, 2026, 10:45 AM UTC
Resolved
Jun 09, 2026, 12:10 PM UTC
Duration
1h 25m
Timeline · 2 updates
  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

Detected by Pingoru
May 28, 2026, 06:15 PM UTC
Resolved
May 28, 2026, 09:30 PM UTC
Duration
3h 15m
Timeline · 1 update
  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

Detected by Pingoru
May 12, 2026, 10:00 PM UTC
Resolved
May 12, 2026, 10:15 PM UTC
Duration
15m
Timeline · 2 updates
  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

Detected by Pingoru
May 08, 2026, 09:53 AM UTC
Resolved
May 09, 2026, 10:00 AM UTC
Duration
1d
Timeline · 2 updates
  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

Detected by Pingoru
May 06, 2026, 07:54 AM UTC
Resolved
May 06, 2026, 09:45 AM UTC
Duration
1h 50m
Timeline · 3 updates
  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 April 20, 2026

NAM: Minor Endpoint Interface Latency Increase

Detected by Pingoru
Apr 20, 2026, 06:30 PM UTC
Resolved
Apr 20, 2026, 08:30 PM UTC
Duration
2h
Timeline · 2 updates
  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 →

Minor March 31, 2026

Automation UI Issue

Detected by Pingoru
Mar 31, 2026, 04:25 PM UTC
Resolved
Apr 19, 2026, 11:59 PM UTC
Duration
19d 7h
Timeline · 2 updates
  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 →