Resolved after 7 hours 7 minutes, affecting Automations and Device Scans, on January 20, 2026.
The team is continuing to investigate the root cause and address residual processing delays related to automations and device scans. • Automations scheduled for after ~10:00 AM MST (including any upcoming automations) should now run as expected. • Automations scheduled between 7:30 AM and 10:00 AM MST may not have run. • Automations scheduled between 9:00 AM and 10:00 AM MST that did not run may still execute, but could be delayed by up to one hour. • Automations scheduled before 9:00 AM MST that did not run will not be retried automatically and may need to be run manually as a workaround.
Affected components
Update timeline
- investigating Jan 20, 2026, 02:20 PM UTC
We are currently investigating this issue.
- investigating Jan 20, 2026, 02:54 PM UTC
We are continuing to investigate this issue.
- investigating Jan 20, 2026, 04:37 PM UTC
We are continuing to investigate this issue.
- investigating Jan 20, 2026, 06:24 PM UTC
The team is continuing to investigate the root cause and address residual processing delays related to automations and device scans. • Automations scheduled for after ~10:00 AM MST (including any upcoming automations) should now run as expected. • Automations scheduled between 7:30 AM and 10:00 AM MST may not have run. • Automations scheduled between 9:00 AM and 10:00 AM MST that did not run may still execute, but could be delayed by up to one hour. • Automations scheduled before 9:00 AM MST that did not run will not be retried automatically and may need to be run manually as a workaround.
- resolved Jan 20, 2026, 09:27 PM UTC
This incident has been resolved.
Your product runs on more than PDQ
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services