Resolved after 7 hours 13 minutes, affecting Portal, on August 6, 2026.
# Summary: Between 2026-08-06 05:41 UTC and 2026-08-06 18:03 UTC, ConnectBooster customers were unable to login to ConnectBooster using KaseyaOne Single-Sign-On \(SSO\). # Root Cause: An unexpected failure in a dependency used by the SSO login process caused login attempts to fail. ## Incident Timeline: • Identified: 2026-08-06 13:30 UTC • Public Notification: 2026-08-06 14:15 UTC • Resolved: 2026-08-06 18:03 UTC # Preventative Measures: To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. ## Enhancements to Monitoring and Alerting: * Enhance login workflow logging to provide improved visibility into authentication performance and failures across all login methods. * Implement monitoring and alerting for login workflows using request, error, and performance metrics, enabling the team to quickly identify and respond to authentication issues. ## Enhancements to Infrastructure Resiliency: * Streamline services within the SSO login workflow so that authentication can continue successfully even if related supporting services are unavailable.
Affected components
Update timeline
- investigating Aug 06, 2026, 02:15 PM UTC
We are aware of a problem where Partners have reported the inability to log into the portal via Kaseya One The Kaseya R&D Team is investigating the issue. In the meantime, our Support team has been supplied with a workaround and can assist you with implementing it. If you would like to have the workaround applied, please create a ticket with our Support team or contact them at 833-863-2237. Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/
- identified Aug 06, 2026, 04:01 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Aug 06, 2026, 05:19 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Aug 06, 2026, 05:19 PM UTC
We are continuing to monitor for any further issues.
- resolved Aug 06, 2026, 09:28 PM UTC
This incident has been resolved.
- postmortem Sep 03, 2026, 02:24 PM UTC
# Summary: Between 2026-08-06 05:41 UTC and 2026-08-06 18:03 UTC, ConnectBooster customers were unable to login to ConnectBooster using KaseyaOne Single-Sign-On \(SSO\). # Root Cause: An unexpected failure in a dependency used by the SSO login process caused login attempts to fail. ## Incident Timeline: • Identified: 2026-08-06 13:30 UTC • Public Notification: 2026-08-06 14:15 UTC • Resolved: 2026-08-06 18:03 UTC # Preventative Measures: To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps. ## Enhancements to Monitoring and Alerting: * Enhance login workflow logging to provide improved visibility into authentication performance and failures across all login methods. * Implement monitoring and alerting for login workflows using request, error, and performance metrics, enabling the team to quickly identify and respond to authentication issues. ## Enhancements to Infrastructure Resiliency: * Streamline services within the SSO login workflow so that authentication can continue successfully even if related supporting services are unavailable.
Your product runs on more than Datto
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