- Detected by Pingoru
- May 29, 2026, 01:23 AM UTC
- Resolved
- May 29, 2026, 01:23 AM UTC
- Duration
- —
Timeline · 2 updates
-
identified May 29, 2026, 01:12 AM UTC
**Impact:** Automox Documentation site is unavailable, https://docs.automox.com. **Current Status:** Cause is identified as a third-party outage; team is investigating further. **Next Update:** We will provide another update within an hour.
-
resolved May 29, 2026, 01:23 AM UTC
The third-party outage has been resolved and docs.automox.com is now available.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 02:56 PM UTC
- Resolved
- Apr 24, 2026, 02:56 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Apr 24, 2026, 02:56 PM UTC
The issue causing the Automox console not to load has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 05:09 PM UTC
- Resolved
- Apr 09, 2026, 05:09 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Apr 09, 2026, 05:09 PM UTC
The issue impacting Splashtop RMM on MacOS has been resolved. We have removed the temporary workaround that prevented patching, and normal functionality has been restored. Splashtop RMM updates can now be applied as expected.
Read the full incident report →
- Detected by Pingoru
- Mar 13, 2026, 06:15 PM UTC
- Resolved
- Mar 13, 2026, 06:15 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Mar 13, 2026, 06:15 PM UTC
Between March 9, 2026 9:30 PM UTC and March 10, 2026 10:00 AM UTC, some customers may have experienced intermittent errors when viewing policy results. Automox has identified the cause and is working on remediation efforts. **Impact:** Historical Policy Results data from approximately September 20, 2025 through February 2026 may appear incomplete or unavailable while restoration is in progress. **Current Status:** Policy execution and reporting is currently operating normally without service degradation. All data is fully available and the system is processing normally.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 04:59 PM UTC
- Resolved
- Feb 25, 2026, 04:59 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Feb 25, 2026, 04:59 PM UTC
The issue causing the elevated error rates has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 19, 2026, 03:54 PM UTC
- Resolved
- Feb 19, 2026, 03:54 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Feb 19, 2026, 03:54 PM UTC
Automox has implemented a fix to address issues with service deployment that did not go as expected. **Current Status:** Our engineering team is working to fix the root cause.
Read the full incident report →
- Detected by Pingoru
- Feb 05, 2026, 04:10 PM UTC
- Resolved
- Feb 05, 2026, 04:10 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Feb 05, 2026, 04:10 PM UTC
The issue causing Automox console availability issues has been resolved. **Current Status:** Automox Engineering team is working to identify the root cause.
Read the full incident report →
- Detected by Pingoru
- Jan 12, 2026, 05:39 PM UTC
- Resolved
- Jan 12, 2026, 05:39 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Jan 12, 2026, 05:39 PM UTC
The issue affecting policy compliance has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 01, 2025, 04:14 PM UTC
- Resolved
- Dec 01, 2025, 04:14 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Dec 01, 2025, 04:14 PM UTC
The issue causing degraded performance in the Automox console has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 27, 2025, 03:06 PM UTC
- Resolved
- Nov 27, 2025, 03:06 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Nov 27, 2025, 03:06 PM UTC
The issue causing errors affecting the Automox console. Has been resolved. **Current Status:** Our engineering team is working to identify the root cause.
Read the full incident report →
- Detected by Pingoru
- Nov 26, 2025, 03:44 AM UTC
- Resolved
- Nov 26, 2025, 03:44 AM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Nov 26, 2025, 03:44 AM UTC
Automox has identified the cause of connection issues with the Automox API and implemented a fix. The incident is resolved. **Impact:** Users may experience out-of-date data in the console and degraded policy performance as the Automox platform catches up over the next few hours. **Current Status:** Our engineering team is working to identify the root cause.
Read the full incident report →
- Detected by Pingoru
- Nov 21, 2025, 10:30 AM UTC
- Resolved
- Nov 21, 2025, 10:30 AM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Nov 21, 2025, 10:30 AM UTC
The issue causing problems with agents and users connecting to the Automox API. Has been resolved. **Impact:** Users may have experienced missed or delayed policy executions. **Current Status:** Our engineering team is working to identify the root cause."
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 07:26 PM UTC
- Resolved
- Nov 18, 2025, 07:26 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Nov 18, 2025, 07:26 PM UTC
The cause of the console outage has been identified and resolved. Cloudflare has restored the service, and the modifications implemented in the Automox platform to address the outage effects have been reversed.
Read the full incident report →
- Detected by Pingoru
- Nov 14, 2025, 10:41 PM UTC
- Resolved
- Nov 14, 2025, 10:41 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Nov 14, 2025, 10:41 PM UTC
The issue causing degraded patching execution times. Has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 27, 2025, 07:11 PM UTC
- Resolved
- Oct 27, 2025, 07:11 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Oct 27, 2025, 07:11 PM UTC
The issue causing delayed policy executions has been resolved, and policy runs are now completing as expected.
Read the full incident report →
- Detected by Pingoru
- Oct 08, 2025, 06:21 PM UTC
- Resolved
- Oct 08, 2025, 06:21 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Oct 08, 2025, 06:21 PM UTC
The issue causing Run Now commands to take longer than expected to return is resolved. **Current Status:** Our engineering team is working to identify the root cause.
Read the full incident report →
- Detected by Pingoru
- Sep 11, 2025, 03:54 PM UTC
- Resolved
- Sep 11, 2025, 03:54 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Sep 11, 2025, 03:54 PM UTC
The issue causing an outage affecting Otto AI. Has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 11, 2025, 02:14 PM UTC
- Resolved
- Sep 11, 2025, 02:14 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Sep 11, 2025, 02:14 PM UTC
The issue causing blocked policy creation and updates via the web console. Has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 03, 2025, 04:30 PM UTC
- Resolved
- Sep 03, 2025, 04:30 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Sep 03, 2025, 04:30 PM UTC
Automox identified an issue this morning that may have affected policy scheduling. This was shortly resolved due to efforts by our Engineering team. **Impact:** Users may experience missed or delayed policy execution and compliance. **Current Status:** Our Engineering team has resolved any ongoing issues and will keep monitoring.
Read the full incident report →
- Detected by Pingoru
- Aug 21, 2025, 07:10 AM UTC
- Resolved
- Aug 21, 2025, 07:10 AM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Aug 21, 2025, 07:10 AM UTC
Automox has implemented a fix to address the issues affecting policy reporting. The issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2025, 04:02 PM UTC
- Resolved
- Aug 19, 2025, 04:02 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Aug 19, 2025, 04:02 PM UTC
Automox has implemented a fix to address the issues affecting policy reporting. The issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 31, 2025, 04:35 AM UTC
- Resolved
- Jul 31, 2025, 04:35 AM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Jul 31, 2025, 04:35 AM UTC
The issue causing the remote control outage has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 31, 2025, 01:07 AM UTC
- Resolved
- Jul 31, 2025, 01:07 AM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Jul 31, 2025, 01:07 AM UTC
The issue causing degraded patching has been resolved. Customers that had missed patched windows enabled will have their patches automatically applied during the next checkin.
Read the full incident report →
- Detected by Pingoru
- Jul 25, 2025, 12:45 AM UTC
- Resolved
- Jul 25, 2025, 12:45 AM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Jul 25, 2025, 12:45 AM UTC
The issue affecting worklet signing has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2025, 04:36 PM UTC
- Resolved
- Jul 24, 2025, 04:36 PM UTC
- Duration
- —
Affected: Automox service
Timeline · 1 update
-
resolved Jul 24, 2025, 04:36 PM UTC
The issue that was causing degraded system performance affecting policy processing has been mitigated. **Impact:** No continuing customer impact is expected **Current Status:** The Automox engineering team is investigating the root cause of the incident and identifying all necessary actions to prevent the issue from recurring.
Read the full incident report →