Pulseway Outage History

Started Oct 07, 2026, 06:10 AM UTC· resolved Oct 07, 2026, 07:59 AM UTC

1. investigating Oct 07, 2026, 06:10 AM UTC

   We are aware of a problem where users are unable to login to Pulseway PSA and are getting a "Something went wrong, please try again." error. The Pulseway Engineering team is investigating the issue. Subscribe to the Pulseway status page for up-to-date information at https://status.pulseway.com/

2. monitoring Oct 07, 2026, 06:36 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Oct 07, 2026, 07:59 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 24, 2026, 02:21 PM UTC· resolved Jul 24, 2026, 09:23 PM UTC

1. identified Jul 24, 2026, 02:21 PM UTC

   We are aware of a problem where customers hosted on EMEA app servers may see intermediate service disruption, getting 500 - internal server error. The Pulseway Engineering Team has identified the issue and working towards a fix. Should you need any additional questions or require assistance, please contact our support team at [email protected] Subscribe to the Pulseway Status Page for up-to-date information at https://status.pulseway.com/

2. identified Jul 24, 2026, 04:29 PM UTC

   The Pulseway Engineering Team has developed a fix that will address this issue. The fix will be deployed after hours to our App Servers on the following schedule: 20:00 UTC (EMEA) Those that are online during this change will need to login again as they will be kicked out the system. Should you have any additional questions or require assistance, please contact our support team at [email protected] Subscribe to the Pulseway Status Page for up-to-date information at https://status.pulseway.com/

3. monitoring Jul 24, 2026, 08:26 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Jul 24, 2026, 09:23 PM UTC

   This incident has been resolved.

5. postmortem Aug 12, 2026, 08:01 PM UTC

   **Root Cause Analysis – Pulseway Intermittent Service Degradation Following 10.28 Release** **Summary** Between **2026-07-24 02:00 UTC** and **2026-07-24 20:25 UTC**, some customers using Pulseway experienced intermittent service degradation, including temporary agent connectivity issues, delayed agent check-ins, and HTTP 503 errors. During periods of elevated automation activity, affected agents could appear to repeatedly transition between online and offline states before reconnecting automatically. The issue was fully resolved on July 24, 2026. **Root Cause** A software change introduced in the 10.28 release altered how certain automation-related database operations were processed. Under high levels of concurrent automation activity, this change resulted in resource contention within the application environment, leading to intermittent service interruptions and delayed responses for agent communications. A hotfix was developed, tested, and deployed the same day to restore the previous transaction handling behavior and eliminate the contention condition. **Incident Timeline** * **Identified:** 2026-07-24 02:00 UTC * **Public Notification:** 2026-07-24 13:27 UTC * **Resolved:** 2026-07-24 20:25 UTC **Preventative Measures** To reduce the likelihood and impact of similar incidents in the future, we are implementing the following improvements: **Enhancements to Monitoring and Alerting** * Introduce additional monitoring and alerting for database contention and long-running transactions to further accelerate detection of similar conditions. * Expand service health dashboards to further improve visibility into application response performance. **Enhancements to Release Management Practices** * Implement expanded canary deployment procedures for higher-risk platform changes, allowing updates to be validated on a limited subset of infrastructure before broader rollout, further reducing the risk for these deployments. * Add additional review requirements for changes affecting high-volume agent communication paths, further reducing risk for these deployments. **Enhancements to Validation and Testing** * Strengthen load and concurrency testing for components that support large-scale automation activity, further increasing scalability at the time of deployment. * Increase validation coverage for scenarios that simulate production-scale agent workloads to catch scalability issues prior to deployment, further reducing risk. **Enhancements to Platform Resiliency** * Continue development of automation workload distribution improvements designed to reduce concentrated processing spikes during large-scale task execution, further increasing scalability at the time of deployment. * Review additional service isolation and capacity improvements to further reduce the impact of localized workload surges. **Completed Corrective Action** * The software change responsible for the contention condition was reverted through a hotfix deployed on July 24, 2026. Following deployment, monitoring confirmed that error rates returned to normal levels and no recurrence of the issue was observed.

Read the full incident report →

Started Jun 05, 2026, 10:57 AM UTC· resolved Jun 05, 2026, 02:25 PM UTC

1. investigating Jun 05, 2026, 10:57 AM UTC

   The Pulseway R&D Teams are currently investing the issue that causes custom agent installers to fail to generate when a user attempts to download them. Please subscribe to this incident to receive updates as they become available.

2. monitoring Jun 05, 2026, 01:08 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Jun 05, 2026, 02:25 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 03, 2026, 06:53 AM UTC· resolved May 03, 2026, 08:21 AM UTC

1. investigating May 03, 2026, 06:53 AM UTC

   We are experiencing service disruption on a subset of Pulseway - US servers, which may impact administrators' ability to manage endpoints. We are aware of the issue, and our team is actively working to resolve the issue. We apologize for any inconvenience caused. - Cloud Operations Team

2. investigating May 03, 2026, 06:54 AM UTC

   We are continuing to investigate this issue.

3. monitoring May 03, 2026, 07:53 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved May 03, 2026, 08:21 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 22, 2026, 02:55 PM UTC· resolved Mar 22, 2026, 05:30 PM UTC

1. investigating Mar 22, 2026, 02:55 PM UTC

   We are currently experiencing a partial service disruption affecting Pulseway EU customers. Our team is actively investigating the issue and working to restore full functionality as quickly as possible. We apologize for any inconvenience caused. - Cloud Operations Team

2. monitoring Mar 22, 2026, 04:22 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Mar 22, 2026, 05:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 12, 2026, 03:24 PM UTC· resolved Mar 13, 2026, 03:52 PM UTC

1. investigating Mar 12, 2026, 03:24 PM UTC

   The R&D team is currently investigating Monitoring Notifications being received from agents without conditions being met for online/offline status changes and service start/stop status changes in the North America region. We apologize for any inconvenience caused.

2. identified Mar 12, 2026, 04:42 PM UTC

   The issue has been identified and a fix is being implemented in a form of a hotfix. We expect this change to be deployed in the next few hours.

3. monitoring Mar 13, 2026, 09:55 AM UTC

   The fix has been implemented for the EMEA region and is currently being deployed for the US region. We are monitoring the results.

4. monitoring Mar 13, 2026, 10:01 AM UTC

   The hotfix was successfully deployed in the US region, and we continue to monitor the results.

5. resolved Mar 13, 2026, 03:52 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 12, 2026, 10:21 AM UTC· resolved Mar 13, 2026, 03:51 PM UTC

1. investigating Mar 12, 2026, 10:21 AM UTC

   We are experiencing Intermittent service disruption in the Pulseway Web Application, which may impact administrators' ability to manage endpoints. We are aware of the issue, and our team is actively working to resolve the issue. We apologize for any inconvenience caused. - Cloud Operations Team

2. investigating Mar 12, 2026, 03:18 PM UTC

   We are continuing to investigate this issue.

3. identified Mar 12, 2026, 04:42 PM UTC

   The issue has been identified and a fix is being implemented in a form of a hotfix. We expect this change to be deployed in the next few hours.

4. identified Mar 13, 2026, 08:30 AM UTC

   We are continuing to work on a fix for this issue.

5. monitoring Mar 13, 2026, 09:55 AM UTC

   The fix has been implemented for the EMEA region and is currently being deployed for the US region. We are monitoring the results.

6. monitoring Mar 13, 2026, 10:01 AM UTC

   The hotfix was successfully deployed in the US region, and we continue to monitor the results.

7. resolved Mar 13, 2026, 03:51 PM UTC

   This incident has been resolved.

8. postmortem Mar 19, 2026, 04:19 PM UTC

   # Summary Between 2026‑03‑12 at 06:21 AM EDT and 2026‑03‑13 at 11:51 AM EDT, customers experienced a performance degradation in the Web Application, which could manifest as slowness or errors while navigating the product. During this period, managed devices intermittently appeared to switch between online and offline states, triggering status‑change notifications when configured, despite the devices’ actual connection status remaining unchanged. # Root Cause A code change introduced in the 9.25 release caused the service responsible for collecting and storing Patch History information to spawn multiple unexpected instances due to a dependency-logic flaw. This led the service to repeatedly trigger full patch‑history resynchronizations across all agents. The resulting surge in request volume gradually saturated the web services, causing progressive performance degradation and ultimately rendering some web service instances unavailable. The R&D team has deployed an Agent hotfix to resolve the issue and has temporarily disabled the patch error history feature in the Web Application. This feature will be re‑enabled, and all related data will be restored during the next release cycle. # Preventative Measures To reduce the likelihood and impact of similar incidents in the future, we are taking the following steps * **Hardening of Internal Systems and Dependencies:** The R&D Team will conduct a comprehensive audit of all dependency logic across the product and verify that injected dependencies consistently perform as expected under load and across various operational scenarios. * **Enhanced Release Management and Control:** The R&D Team will implement additional mandatory quality‑assurance measures to ensure that all shared components and injected dependencies are properly validated and scoped to their intended use‑case scenarios. These measures will help prevent unintended states by confirming that dependencies behave consistently, remain isolated to their defined contexts, and do not introduce side effects across the system. * **Enhanced Monitoring, Alerting, and Response:** The R&D Team will implement enhanced monitoring to identify unexpected database growth in real time across both QA and production environments. These metrics will be integrated with existing anomaly‑detection systems to enable faster detection and response to potentially undesirable states that could impact system stability or degrade user experience. * **Enhanced Incident Management and Response:** The teams will continue to maintain and enhance scenario‑specific playbooks to ensure that validated mitigation and resolution procedures are executed quickly and accurately. These improvements are intended to further reduce the time required to detect, diagnose, and resolve issues when they occur.

Read the full incident report →

Started Mar 10, 2026, 01:10 PM UTC· resolved Mar 10, 2026, 05:42 PM UTC

1. investigating Mar 10, 2026, 01:10 PM UTC

   We are experiencing service disruption on a subset of Pulseway - EU servers, which may impact administrators' ability to manage endpoints. We are aware of the issue, and our team is actively working to resolve the issue. We apologize for any inconvenience caused. - Cloud Operations Team

2. monitoring Mar 10, 2026, 02:33 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Mar 10, 2026, 05:42 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 19, 2026, 12:27 PM UTC· resolved Mar 12, 2026, 03:15 PM UTC

1. identified Jan 19, 2026, 12:27 PM UTC

   The Pulseway R&D teams are working on resolving an issue impacting the publishing of third party application packages. Recent updates published by vendors to managed third party applications do not currently appear as available and get installed in Pulseway 3rd Party Patching. Subscribe to the Pulseway Status Page for up-to-date information at https://status.pulseway.com/

2. resolved Mar 12, 2026, 03:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 24, 2025, 01:38 AM UTC· resolved Nov 24, 2025, 05:39 PM UTC

1. investigating Nov 24, 2025, 01:38 AM UTC

   We are experiencing degraded performance on Pulseway - EU servers, which may impact administrators ability to manage endpoints. We are aware of the issue and our team is actively working to resolve the issue. We apologize for any inconvenience caused. - Cloud Operations Team

2. monitoring Nov 24, 2025, 12:55 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Nov 24, 2025, 05:39 PM UTC

   This incident has been resolved.

4. postmortem Dec 01, 2025, 06:29 PM UTC

   **Summary:** After scheduled system maintenance on 21st November 2025 for Pulseway in the EMEA region, managed devices running Windows Server versions prior to 2016 were unable to connect to the Pulseway service and appeared offline in the Web Application. **Root Cause:** The maintenance, completed at 11:00 PM \(UTC\) on 21st November 2025, involved updating the regional load balancer network to enforce FIPs-compliant connection security and encryption standards. Post-upgrade, affected Operating Systems failed the TLS handshake with the server due to lack of support for the required cipher suites, resulting in connection failures. **Resolution:** The update was rolled back on 24th November 2025 at 10:30 AM \(UTC\) to restore compatibility, allowing impacted managed devices to reconnect successfully. **Preventative Measures:** To mitigate risk and prevent recurrence, the following initiatives are being implemented: * **Progressive Rollout Strategies:** The Kaseya R&D Team will evaluate staged deployment strategies to detect and resolve unforeseen issues before they affect a wider user base. * **Enhanced Customer Experience Monitoring:** Options are being considered to implement more robust synthetic and real-user testing to better simulate and monitor customer experience following deployments. * **Minimum System Requirements Review:** The Kaseya R&D and Product Management teams will review and update the documented minimum system requirements to align with the product roadmap and ensure compatibility with supported environments. As part of this process, support for end-of-life operating systems will be assessed against current security and compliance standards and will be phased out in future Pulseway releases. * **Enhanced Incident Management and Response:** Global Kaseya Teams will continue to train on Incident Management playbooks to strengthen internal coordination and response during incident events.

Read the full incident report →

Started Aug 27, 2025, 08:58 AM UTC· resolved Aug 27, 2025, 10:07 AM UTC

1. identified Aug 27, 2025, 08:58 AM UTC

   We are currently experiencing a partial service disruption affecting Pulseway customers. Customers may not be able to use the below features during this time. E-commerce Custom agent installers New tenant provisioning Our team is actively investigating the issue and working to restore full functionality as quickly as possible. We apologize for any inconvenience caused. - Cloud Operations Team

2. monitoring Aug 27, 2025, 09:08 AM UTC

   This issue has been resolved now and we will continue to monitor the status. We apologize for any inconvenience caused. - Cloud Operations Team

3. resolved Aug 27, 2025, 10:07 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 18, 2025, 04:48 AM UTC· resolved Aug 18, 2025, 05:11 PM UTC

1. investigating Aug 18, 2025, 04:48 AM UTC

   We are currently experiencing a partial service disruption affecting Pulseway EU customers. This may impact administrators' ability to manage endpoints and subscriptions. Our team is actively investigating the issue and working to restore full functionality as quickly as possible. We apologize for any inconvenience caused. - Cloud Operations Team

2. investigating Aug 18, 2025, 04:48 AM UTC

   We are continuing to investigate this issue.

3. identified Aug 18, 2025, 09:44 AM UTC

   The issue has been identified, and the team is actively working to resolve it.

4. monitoring Aug 18, 2025, 10:45 AM UTC

   The issue has been resolved.

5. monitoring Aug 18, 2025, 10:46 AM UTC

   We are continuing to monitor for any further issues.

6. resolved Aug 18, 2025, 05:11 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 21, 2025, 02:46 PM UTC· resolved Jul 21, 2025, 03:32 PM UTC

1. monitoring Jul 21, 2025, 02:46 PM UTC

   We recently identified an issue affecting 2FA login functionality, where a few users were unable to access their accounts. The issue was traced to one of our US-based application servers and has now been resolved. The affected server is currently under monitoring to ensure continued stability. We sincerely apologize for the inconvenience. -Cloud Operations Team

2. resolved Jul 21, 2025, 03:32 PM UTC

   This incident has been resolved.

3. postmortem Aug 05, 2025, 10:16 AM UTC

   On July 21st, 2025 at 10:00 AM EDT, Pulseway customers in the North America region experienced a service disruption that affected user logins utilizing two-factor authentication \(2FA\). Impacted users were redirected back to the login page after attempting to authenticate. The root cause was identified as a server time shift issue. Although the server time was corrected promptly, the web services did not update their time as expected. The infrastructure team performed a restart and recycling to force the synchronization with the updated server time. The service was fully restored and returned to a healthy state by 10:40 AM EDT. To prevent similar incidents in the future, we are implementing the following improvements: * **Enhanced Monitoring**: System monitoring is being upgraded to better detect anomalies in the login flow. * **Improved Failover Mechanisms**: Enhancements are underway to strengthen failover capabilities in the event of web service disruptions. * **Process Optimization**: Engineering runbooks are being updated to streamline incident response and improve operational efficiency. We appreciate your patience and understanding as we continue to improve the reliability and resilience of our services.

Read the full incident report →

Started Nov 21, 2024, 01:50 PM UTC· resolved Nov 21, 2024, 04:28 PM UTC

1. investigating Nov 21, 2024, 01:50 PM UTC

   We are experiencing an outage on Pulseway - US servers that may be resulting in agents offline and impacting administrators ability to manage endpoints. Our team is working to restore functionality on the instance at this time. We apologize for any inconvenience. - Cloud Operations Team

2. identified Nov 21, 2024, 03:51 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Nov 21, 2024, 04:07 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Nov 21, 2024, 04:28 PM UTC

   This incident has been resolved.

5. postmortem Nov 26, 2024, 01:28 PM UTC

   On 21st November 2024 around 13:30 UTC, Pulseway customers in the United States region started experiencing a service issue that resulted in users not being able to login to the Web Application and managed agents going offline. The root cause of this incident was identified to be a configuration issue made apparent by an infrastructure update causing requests to the service to fail. The R&D team resolved the issue with a fail-over and worked with our vendor to ensure that redundancies are available, and appropriately configured, to prevent a future occurrence.

Read the full incident report →