<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>CompassMSP Services Status Page Status - Incident history</title>
    <link>https://health.compassmsp.com</link>
    <description>CompassMSP Services Status Page</description>
    <pubDate>Sun, 4 Oct 2026 00:35:00 +0000</pubDate>
    
<item>
  <title>RMM - Vidal (US East) - Platform Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 20 minutes

    Affected Components: RMM / Monitoring System
    Oct 4, 00:35:07 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Oct 4, 00:33:47 GMT+0 - Planned - In order to provide you with continued platform stability, we will be performing maintenance on this platform.

Expected Impact: Partners can expect devices to reconnect during this time, and in some cases devices may briefly go offline. CSM and Agent Browser sessions may close, and there may be a short period of reduced functionality.

Should you have any questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Oct 4, 00:55:07 GMT+0 - Completed - The scheduled maintenance has been completed. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 20 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:35:07&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:33:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Planned&lt;/strong&gt; -
  In order to provide you with continued platform stability, we will be performing maintenance on this platform.

Expected Impact: Partners can expect devices to reconnect during this time, and in some cases devices may briefly go offline. CSM and Agent Browser sessions may close, and there may be a short period of reduced functionality.

Should you have any questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:55:07&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The scheduled maintenance has been completed..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 4 Oct 2026 00:35:00 +0000</pubDate>
  <link>https://health.compassmsp.com/maintenance/cmut38qyc0i6p0krthhggvpes</link>
  <guid>https://health.compassmsp.com/maintenance/cmut38qyc0i6p0krthhggvpes</guid>
</item>

<item>
  <title>DattoRMM - All Platforms - MacOS Agent Connectivity Issues</title>
  <description>
    Type: Incident
    

    Affected Components: RMM / Monitoring System
    Oct 3, 15:08:19 GMT+0 - Identified - Our teams are continuing to work on a resolution.

The behaviors described in our previous update remain unchanged:
• Newly installed macOS agent installations are unable to establish connectivity.
• Existing macOS agents that are currently in production environments should remain online.
• If a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM.

Until a resolution is available, we continue to recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible.

We will post our next update here by 7:00 PM EDT on Saturday, October 3, 2026, or sooner if more information becomes available.

We apologize for the inconvenience and appreciate your patience while we work to resolve this issue.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/ Oct 3, 23:00:44 GMT+0 - Identified - The Kaseya R&amp;D team has developed a fix and will be rolling out the update to the MacOS agents tonight and tomorrow. We will post a maintenance window for each platform prior to the update. 
 
To assist with updating macOS agents and verifying they are updated correctly, we have prepared a step-by-step guide available here: https://rmm.datto.com/help/en/Content/Troubleshooting/Agent/macOS11994.htm
 
Until the update is out on your platform the behaviors described in our previous posts remain unchanged: 
• Newly installed macOS agent installations are unable to establish connectivity. 
• Existing macOS agents that are currently in production environments should remain online. 
• If a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM. 
• We continue to recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible. 
 
We will post our next update here after all deployments are completed, or sooner if more information becomes available. 
 
We apologize for the inconvenience and appreciate your patience while we work to resolve this issue. 
 
Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact 
 
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/ Oct 4, 13:31:49 GMT+0 - Monitoring - A fix has now been deployed across all supported platforms and is available to all customers. Our teams are actively monitoring the environment and platform telemetry to validate the effectiveness of the changes and ensure systems continue to operate as expected.

We encourage all customers to verify that their macOS devices are online and reporting successfully following the deployment of this fix. While many devices should recover normally, some macOS agents may remain offline and will require additional remediation including manual intervention by the end users. To assist with this process, we have prepared a step-by-step guide that will help you confirm agent status, identify devices requiring further assistance, and walk you through the recommended recovery steps: https://rmm.datto.com/help/en/Content/Troubleshooting/Agent/macOS11994.htm

We appreciate your patience, understanding, and partnership while we worked to investigate and resolve these issues.

Should you have any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Oct 2, 18:16:00 GMT+0 - Investigating - We are aware of a problem affecting the connectivity of Datto RMM macOS agents.

At this time, we have identified the following behaviors:

- Newly installed macOS agent installations are unable to establish connectivity.
- Existing macOS agents, that are currently in production environments, should remain online; however, our investigation is ongoing to determine whether additional scenarios may cause agents to go offline.
- Initial testing shows that if a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM.

Our teams are actively investigating the root cause with Apple and working to develop a resolution. We will provide additional updates as more information becomes available.

Until further notice, we recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible.

We apologize for the inconvenience and appreciate your patience while we work to resolve this issue.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/ Oct 2, 21:58:25 GMT+0 - Identified - We have identified the cause of the issue affecting the connectivity of Datto RMM macOS agents. Our teams are now working on a resolution.

The behaviors described in our previous update remain unchanged:
• Newly installed macOS agent installations are unable to establish connectivity.
• Existing macOS agents that are currently in production environments should remain online.
• If a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM.

Until a resolution is available, we continue to recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible.

We will post our next update here by 11:00 AM EDT on Saturday, October 3, 2026, or sooner if more information becomes available.

We apologize for the inconvenience and appreciate your patience while we work to resolve this issue.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/ 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:08:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our teams are continuing to work on a resolution.

The behaviors described in our previous update remain unchanged:
• Newly installed macOS agent installations are unable to establish connectivity.
• Existing macOS agents that are currently in production environments should remain online.
• If a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM.

Until a resolution is available, we continue to recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible.

We will post our next update here by 7:00 PM EDT on Saturday, October 3, 2026, or sooner if more information becomes available.

We apologize for the inconvenience and appreciate your patience while we work to resolve this issue.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:00:44&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The Kaseya R&amp;D team has developed a fix and will be rolling out the update to the MacOS agents tonight and tomorrow. We will post a maintenance window for each platform prior to the update. 
 
To assist with updating macOS agents and verifying they are updated correctly, we have prepared a step-by-step guide available here: https://rmm.datto.com/help/en/Content/Troubleshooting/Agent/macOS11994.htm
 
Until the update is out on your platform the behaviors described in our previous posts remain unchanged: 
• Newly installed macOS agent installations are unable to establish connectivity. 
• Existing macOS agents that are currently in production environments should remain online. 
• If a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM. 
• We continue to recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible. 
 
We will post our next update here after all deployments are completed, or sooner if more information becomes available. 
 
We apologize for the inconvenience and appreciate your patience while we work to resolve this issue. 
 
Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact 
 
Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:31:49&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  A fix has now been deployed across all supported platforms and is available to all customers. Our teams are actively monitoring the environment and platform telemetry to validate the effectiveness of the changes and ensure systems continue to operate as expected.

We encourage all customers to verify that their macOS devices are online and reporting successfully following the deployment of this fix. While many devices should recover normally, some macOS agents may remain offline and will require additional remediation including manual intervention by the end users. To assist with this process, we have prepared a step-by-step guide that will help you confirm agent status, identify devices requiring further assistance, and walk you through the recommended recovery steps: https://rmm.datto.com/help/en/Content/Troubleshooting/Agent/macOS11994.htm

We appreciate your patience, understanding, and partnership while we worked to investigate and resolve these issues.

Should you have any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:16:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of a problem affecting the connectivity of Datto RMM macOS agents.

At this time, we have identified the following behaviors:

- Newly installed macOS agent installations are unable to establish connectivity.
- Existing macOS agents, that are currently in production environments, should remain online; however, our investigation is ongoing to determine whether additional scenarios may cause agents to go offline.
- Initial testing shows that if a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM.

Our teams are actively investigating the root cause with Apple and working to develop a resolution. We will provide additional updates as more information becomes available.

Until further notice, we recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible.

We apologize for the inconvenience and appreciate your patience while we work to resolve this issue.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:58:25&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified the cause of the issue affecting the connectivity of Datto RMM macOS agents. Our teams are now working on a resolution.

The behaviors described in our previous update remain unchanged:
• Newly installed macOS agent installations are unable to establish connectivity.
• Existing macOS agents that are currently in production environments should remain online.
• If a macOS device is restarted, the agent may not restart, causing the device to be offline in Datto RMM.

Until a resolution is available, we continue to recommend avoiding unnecessary reboots of managed macOS devices and postponing new macOS agent deployments where possible.

We will post our next update here by 11:00 AM EDT on Saturday, October 3, 2026, or sooner if more information becomes available.

We apologize for the inconvenience and appreciate your patience while we work to resolve this issue.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 2 Oct 2026 18:15:59 +0000</pubDate>
  <link>https://health.compassmsp.com/incident/cmuraenrw1inq0rpnx70mkgkb</link>
  <guid>https://health.compassmsp.com/incident/cmuraenrw1inq0rpnx70mkgkb</guid>
</item>

<item>
  <title>RMM Agent Not Generating Service Tickets</title>
  <description>
    Type: Incident
    Duration: 2 hours and 3 minutes

    Affected Components: RMM / Monitoring System
    Sep 30, 14:23:22 GMT+0 - Investigating - We are currently investigating an issue with our RMM agent that is preventing service tickets from being generated. In the meantime, please submit tickets through the End User Ticketing Portal at https://compassmsp.myportallogin.com or by emailing help@compassmsp.com. Our team is actively working to resolve this issue and will provide updates as more information becomes available. Sep 30, 16:22:41 GMT+0 - Monitoring - We have restored functionality of the ticket submission feature in the RMM agent and are actively monitoring its performance to ensure stability. We will provide a final update once the issue has been fully resolved. Sep 30, 16:26:35 GMT+0 - Resolved - This issue has been resolved with the workaround. RMM agent ticket creation capabilities have been restored. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 3 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:23:22&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an issue with our RMM agent that is preventing service tickets from being generated. In the meantime, please submit tickets through the End User Ticketing Portal at https://compassmsp.myportallogin.com or by emailing help@compassmsp.com. Our team is actively working to resolve this issue and will provide updates as more information becomes available..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:22:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We have restored functionality of the ticket submission feature in the RMM agent and are actively monitoring its performance to ensure stability. We will provide a final update once the issue has been fully resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:26:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This issue has been resolved with the workaround. RMM agent ticket creation capabilities have been restored..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 30 Sep 2026 14:23:22 +0000</pubDate>
  <link>https://health.compassmsp.com/incident/cmuo73sah00w31ms2nn9s7yxb</link>
  <guid>https://health.compassmsp.com/incident/cmuo73sah00w31ms2nn9s7yxb</guid>
</item>

<item>
  <title>CompassMSP Ticketing System – Scheduled Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 6 days, 13 hours and 40 minutes

    Affected Components: CompassMSP Ticketing System
    Sep 24, 12:37:21 GMT+0 - Identified - We have scheduled routine maintenance for the CompassMSP Ticketing System on Tuesday, September 29, from 10:00 PM to 12:00 AM ET. During this window, the ticketing system may be intermittently unavailable. We appreciate your patience and apologize for any inconvenience. Sep 30, 02:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 30, 02:44:00 GMT+0 - Identified - Scheduled maintenance has been completed. The CompassMSP Ticketing System is fully operational. Thank you for your patience. Sep 29, 22:45:00 GMT+0 - Completed - Maintenance has completed successfully Sep 30, 02:44:07 GMT+0 - Identified - The maintenance window for the CompassMSP Ticketing System has been extended and is now scheduled to conclude at 10:45 PM ET. We appreciate your continued patience. Oct 6, 15:40:21 GMT+0 - Completed - Scheduled maintenance for the CompassMSP Ticketing System has been completed. The system is fully operational. Thank you for your patience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 6 days, 13 hours and 40 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:37:21&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have scheduled routine maintenance for the CompassMSP Ticketing System on Tuesday, September 29, from 10:00 PM to 12:00 AM ET. During this window, the ticketing system may be intermittently unavailable. We appreciate your patience and apologize for any inconvenience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:44:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Scheduled maintenance has been completed. The CompassMSP Ticketing System is fully operational. Thank you for your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:44:07&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The maintenance window for the CompassMSP Ticketing System has been extended and is now scheduled to conclude at 10:45 PM ET. We appreciate your continued patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:40:21&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Scheduled maintenance for the CompassMSP Ticketing System has been completed. The system is fully operational. Thank you for your patience..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 30 Sep 2026 02:00:00 +0000</pubDate>
  <link>https://health.compassmsp.com/maintenance/cmufiobw30a0k1mrgsat84hph</link>
  <guid>https://health.compassmsp.com/maintenance/cmufiobw30a0k1mrgsat84hph</guid>
</item>

<item>
  <title>DattoRMM - Syrah/Vidal - Cagservice.exe is being flagged as malicious (Rapidstop) by Microsoft Defender for Endpoint.</title>
  <description>
    Type: Incident
    Duration: 8 hours and 12 minutes

    Affected Components: RMM / Monitoring System
    Sep 28, 15:11:12 GMT+0 - Investigating - We are aware of a problem where Datto RMM&#039;s 15.1.1 Cagservice.exe is being flagged as malicious (Rapidstop) by Microsoft Defender for Endpoint.

The Kaseya Engineering Team is investigating this issue with Microsoft.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/ Sep 28, 22:10:30 GMT+0 - Monitoring - A fix has been implemented and we are Monitoring the results.

The Kaseya R&amp;D team confirmed with Microsoft counterparts that the issue was caused by misclassification of the 15.1.1 Datto RMM version&#039;s cagservice.exe in a recent security intelligence update for Microsoft Defender Antivirus and other Microsoft antimalware. 
 
This issue was fixed in the security intelligence update version 1.459.450.0, and the issue should no longer occur on device&#039;s with this definition version or later. Microsoft currently does not offer an automated way to revert the quarantining of a file, therefore manual action is required to bring affected devices back online in Datto RMM. 
 
We recommend our partners to ensure that devices are updated with security intelligence version 1.459.450.0 or later to avoid the agent being falsely flagged as malicious by Microsoft antimalware. 
 
Users can use the below commands and instructions to ensure that the latest security intelligence update is installed on the device to prevent the behavior: 
Updating the security intelligence version: 
- PowerShell: Update-MpSignature 
- Command Prompt (CMD): MpCmdRun.exe -SignatureUpdate 
 
After running the update, users can verify the installed version with the following command: 
- Get-MpComputerStatus | Select-Object AntivirusSignatureVersion, AntivirusSignatureLastUpdated Sep 28, 19:40:35 GMT+0 - Investigating - Our team remains actively engaged with Microsoft to investigate reports of false-positive detections occurring after devices were updated to Datto RMM Agent version 15.1.1 and to support remediation efforts where needed. At this time, the issue appears to be related to a security detection classification and not confirmed as malicious activity within the Datto RMM agent. We will continue to share updates as additional information becomes available.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/ Sep 29, 14:55:24 GMT+0 - Resolved - This incident has been resolved after monitoring overnight. As previously stated, this issue was fixed in the security intelligence update version 1.459.450.0, and should no longer occur on device&#039;s with this definition version or later. Please see the earlier communication for further details. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:11:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of a problem where Datto RMM&#039;s 15.1.1 Cagservice.exe is being flagged as malicious (Rapidstop) by Microsoft Defender for Endpoint.

The Kaseya Engineering Team is investigating this issue with Microsoft.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:10:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  A fix has been implemented and we are Monitoring the results.

The Kaseya R&amp;D team confirmed with Microsoft counterparts that the issue was caused by misclassification of the 15.1.1 Datto RMM version&#039;s cagservice.exe in a recent security intelligence update for Microsoft Defender Antivirus and other Microsoft antimalware. 
 
This issue was fixed in the security intelligence update version 1.459.450.0, and the issue should no longer occur on device&#039;s with this definition version or later. Microsoft currently does not offer an automated way to revert the quarantining of a file, therefore manual action is required to bring affected devices back online in Datto RMM. 
 
We recommend our partners to ensure that devices are updated with security intelligence version 1.459.450.0 or later to avoid the agent being falsely flagged as malicious by Microsoft antimalware. 
 
Users can use the below commands and instructions to ensure that the latest security intelligence update is installed on the device to prevent the behavior: 
Updating the security intelligence version: 
- PowerShell: Update-MpSignature 
- Command Prompt (CMD): MpCmdRun.exe -SignatureUpdate 
 
After running the update, users can verify the installed version with the following command: 
- Get-MpComputerStatus | Select-Object AntivirusSignatureVersion, AntivirusSignatureLastUpdated.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:40:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  Our team remains actively engaged with Microsoft to investigate reports of false-positive detections occurring after devices were updated to Datto RMM Agent version 15.1.1 and to support remediation efforts where needed. At this time, the issue appears to be related to a security detection classification and not confirmed as malicious activity within the Datto RMM agent. We will continue to share updates as additional information becomes available.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:55:24&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved after monitoring overnight. As previously stated, this issue was fixed in the security intelligence update version 1.459.450.0, and should no longer occur on device&#039;s with this definition version or later. Please see the earlier communication for further details..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 28 Sep 2026 15:11:12 +0000</pubDate>
  <link>https://health.compassmsp.com/incident/cmule3ketce7g0krvo4692y2k</link>
  <guid>https://health.compassmsp.com/incident/cmule3ketce7g0krvo4692y2k</guid>
</item>

<item>
  <title>RMM - Vidal (US East) - Platform Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: RMM / Monitoring System
    Sep 25, 14:02:58 GMT+0 - Planned - In order to provide you with continued platform stability, we will be performing maintenance on this platform.

Expected Impact: Partners can expect devices to reconnect during this time, and in some cases devices may briefly go offline. CSM and Agent Browser sessions may close, and there may be a short period of reduced functionality.

Should you have any questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Sep 28, 08:00:24 GMT+0 - Planned - Maintenance will begin as scheduled in 60 minutes. Sep 28, 09:00:08 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Sep 28, 10:00:08 GMT+0 - Completed - The scheduled maintenance has been completed. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:02:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Planned&lt;/strong&gt; -
  In order to provide you with continued platform stability, we will be performing maintenance on this platform.

Expected Impact: Partners can expect devices to reconnect during this time, and in some cases devices may briefly go offline. CSM and Agent Browser sessions may close, and there may be a short period of reduced functionality.

Should you have any questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:00:24&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Planned&lt;/strong&gt; -
  Maintenance will begin as scheduled in 60 minutes..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:00:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:00:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The scheduled maintenance has been completed..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 28 Sep 2026 09:00:00 +0000</pubDate>
  <link>https://health.compassmsp.com/maintenance/cmuh1aqcx59540rrv0mqo5jn8</link>
  <guid>https://health.compassmsp.com/maintenance/cmuh1aqcx59540rrv0mqo5jn8</guid>
</item>

<item>
  <title>RMM - Vidal (US East) - Platform Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: RMM / Monitoring System
    Sep 23, 09:00:16 GMT+0 - Completed - The scheduled maintenance has been completed. Sep 22, 15:24:58 GMT+0 - Planned - In order to provide you with continued platform stability, we will be performing maintenance on this platform.

Expected Impact: Partners can expect devices to reconnect during this time, and in some cases devices may briefly go offline. CSM and Agent Browser sessions may close, and there may be a short period of reduced functionality.

Should you have any questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Sep 23, 06:00:18 GMT+0 - Planned - Maintenance will begin as scheduled in 60 minutes. Sep 23, 07:00:21 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:00:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The scheduled maintenance has been completed..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:24:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Planned&lt;/strong&gt; -
  In order to provide you with continued platform stability, we will be performing maintenance on this platform.

Expected Impact: Partners can expect devices to reconnect during this time, and in some cases devices may briefly go offline. CSM and Agent Browser sessions may close, and there may be a short period of reduced functionality.

Should you have any questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:00:18&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Planned&lt;/strong&gt; -
  Maintenance will begin as scheduled in 60 minutes..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:21&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 23 Sep 2026 07:00:00 +0000</pubDate>
  <link>https://health.compassmsp.com/maintenance/cmuctz196jyet0rmhw1gmee1b</link>
  <guid>https://health.compassmsp.com/maintenance/cmuctz196jyet0rmhw1gmee1b</guid>
</item>

<item>
  <title>RMM - Vidal (US East) - Platform Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 30 minutes

    Affected Components: RMM / Monitoring System
    Sep 10, 12:30:45 GMT+0 - Planned - In order to provide you with continued platform stability, we will be performing maintenance on this platform.

Expected Impact: Partners can expect devices to reconnect during this time, and in some cases devices may briefly go offline. CSM and Agent Browser sessions may close, and there may be a short period of reduced functionality. Job-related activities may experience some degradation. 

Should you have any questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Sep 11, 08:00:09 GMT+0 - Planned - Maintenance will begin as scheduled in 60 minutes. Sep 11, 09:00:07 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Sep 11, 09:31:07 GMT+0 - Completed - The scheduled maintenance has been completed. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:30:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Planned&lt;/strong&gt; -
  In order to provide you with continued platform stability, we will be performing maintenance on this platform.

Expected Impact: Partners can expect devices to reconnect during this time, and in some cases devices may briefly go offline. CSM and Agent Browser sessions may close, and there may be a short period of reduced functionality. Job-related activities may experience some degradation. 

Should you have any questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:00:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Planned&lt;/strong&gt; -
  Maintenance will begin as scheduled in 60 minutes..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:00:07&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:31:07&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The scheduled maintenance has been completed..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 11 Sep 2026 09:00:00 +0000</pubDate>
  <link>https://health.compassmsp.com/maintenance/cmtviexaha5m80kqjltc2k391</link>
  <guid>https://health.compassmsp.com/maintenance/cmtviexaha5m80kqjltc2k391</guid>
</item>

<item>
  <title>ConnectWise PSA Scheduled Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: CompassMSP Ticketing System
    Sep 2, 12:57:05 GMT+0 - Identified - ConnectWise Manage (PSA) will be intermittently unavailable during this maintenance window. Reporting and dashboards may continue to be unavailable until the following morning. Sep 9, 02:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 9, 04:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:57:05&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  ConnectWise Manage (PSA) will be intermittently unavailable during this maintenance window. Reporting and dashboards may continue to be unavailable until the following morning..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 9&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 9 Sep 2026 02:00:00 +0000</pubDate>
  <link>https://health.compassmsp.com/maintenance/cmtk3oz1w02141nnwl13c8lvm</link>
  <guid>https://health.compassmsp.com/maintenance/cmtk3oz1w02141nnwl13c8lvm</guid>
</item>

<item>
  <title>KaseyaOne - Release v2.76.0 - Maintenance Notice</title>
  <description>
    Type: Maintenance
    Duration: 3 hours

    
    Sep 2, 17:13:25 GMT+0 - Planned - We are notifying you of a planned maintenance event for KaseyaOne to ensure the platform remains secure, efficient, and reliable.

Maintenance Schedule:
    Version: Release v2.76.0
    Start Time: Thursday, 3rd September 2026 at 1:00 AM (EDT)
    Duration: 3 Hours

What You Need to Know:
    - Service Availability: No service disruption is anticipated during this maintenance. 
    - Affected Components: KaseyaOne platform

Our team will conduct this maintenance to introduce enhancements aimed at optimizing performance, reinforcing security, and providing a smoother experience for all users. 

Should you have any questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/phone

Subscribe to receive up-to-date notifications on this and future maintenance periods by visiting https://status.kaseya.com/

As a note; To ensure business continuity, for Kaseya modules using Require Log In with KaseyaOne, users must authenticate using their KaseyaOne Unified Login credentials.  Users added as exceptions can still log in using local module-specific credentials. Details are available in this Knowledge Base article: https://help.one.kaseya.com/help/Content/1_Configuration/enable-require-login-with-K1.htm 

We recommend adding a small set of users to the override list to maintain access in the event of a future disruption or maintenance, helping ensure continuous business operations. Sep 3, 04:00:09 GMT+0 - Planned - Maintenance will begin as scheduled in 60 minutes. Sep 3, 05:00:07 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Sep 3, 08:01:45 GMT+0 - Completed - The scheduled maintenance has been completed. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:13:25&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Planned&lt;/strong&gt; -
  We are notifying you of a planned maintenance event for KaseyaOne to ensure the platform remains secure, efficient, and reliable.

Maintenance Schedule:
    Version: Release v2.76.0
    Start Time: Thursday, 3rd September 2026 at 1:00 AM (EDT)
    Duration: 3 Hours

What You Need to Know:
    - Service Availability: No service disruption is anticipated during this maintenance. 
    - Affected Components: KaseyaOne platform

Our team will conduct this maintenance to introduce enhancements aimed at optimizing performance, reinforcing security, and providing a smoother experience for all users. 

Should you have any questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/phone

Subscribe to receive up-to-date notifications on this and future maintenance periods by visiting https://status.kaseya.com/

As a note; To ensure business continuity, for Kaseya modules using Require Log In with KaseyaOne, users must authenticate using their KaseyaOne Unified Login credentials.  Users added as exceptions can still log in using local module-specific credentials. Details are available in this Knowledge Base article: https://help.one.kaseya.com/help/Content/1_Configuration/enable-require-login-with-K1.htm 

We recommend adding a small set of users to the override list to maintain access in the event of a future disruption or maintenance, helping ensure continuous business operations..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:00:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Planned&lt;/strong&gt; -
  Maintenance will begin as scheduled in 60 minutes..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:00:07&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:01:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The scheduled maintenance has been completed..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 3 Sep 2026 05:00:00 +0000</pubDate>
  <link>https://health.compassmsp.com/maintenance/cmtkcwxytcwkq0kpw9eb0flrc</link>
  <guid>https://health.compassmsp.com/maintenance/cmtkcwxytcwkq0kpw9eb0flrc</guid>
</item>

<item>
  <title>Intuit Reports QuickBooks Online API Errors</title>
  <description>
    Type: Incident
    Duration: 16 days, 14 hours and 23 minutes

    Affected Components: Kaseya → Connectbooster → Portal
    Sep 1, 21:49:24 GMT+0 - Monitoring - A recent degradation with Intuit&#039;s QuickBooks Online has been reported by Intuit. This is currently affecting API calls which may result in sync failures causing delays in data syncing to and from QBO and ConnectBooster. Our team is currently monitoring the status of this from Intuit&#039;s Status Page which can be found here: https://status.developer.intuit.com/

At this time, a valid workaround is not available, and we recommend that you subscribe to Intuit&#039;s Status Page for immediate updates. Our team will continue to provide status updates as they are received to the status page.

Thank you, Sep 2, 03:00:59 GMT+0 - Monitoring - Intuit has updated their status page stating that this is a Major Outage within the Intuit system. They are still investigating the issue. This is currently affecting API calls resulting in sync failures causing delays in data syncing to and from QBO and ConnectBooster. 

Our team is continuing to monitor the status of this from Intuit&#039;s Status Page which can be found here: https://status.developer.intuit.com/

At this time, a valid workaround is not available, and we recommend that you subscribe to Intuit&#039;s Status Page for immediate updates. Our team will continue to provide status updates as they are received to the status page Sep 2, 12:52:18 GMT+0 - Monitoring - Intuit has reported that API functionality has returned, and calls should be completing as expected. Our internal teams have confirmed that syncs are running now running as expected. 

We advise Partners to compare data between ConnectBooster, and QuickBooks Online to ensure the data is up to date, and if not, to set their sync date back to 9/1/2026 - 1pm which was prior to the outage being reported by Intuit and allow for an accounting package sync to take place.

Thank you, Sep 2, 16:51:47 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 16 days, 14 hours and 23 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:49:24&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  A recent degradation with Intuit&#039;s QuickBooks Online has been reported by Intuit. This is currently affecting API calls which may result in sync failures causing delays in data syncing to and from QBO and ConnectBooster. Our team is currently monitoring the status of this from Intuit&#039;s Status Page which can be found here: https://status.developer.intuit.com/

At this time, a valid workaround is not available, and we recommend that you subscribe to Intuit&#039;s Status Page for immediate updates. Our team will continue to provide status updates as they are received to the status page.

Thank you,.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:00:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Intuit has updated their status page stating that this is a Major Outage within the Intuit system. They are still investigating the issue. This is currently affecting API calls resulting in sync failures causing delays in data syncing to and from QBO and ConnectBooster. 

Our team is continuing to monitor the status of this from Intuit&#039;s Status Page which can be found here: https://status.developer.intuit.com/

At this time, a valid workaround is not available, and we recommend that you subscribe to Intuit&#039;s Status Page for immediate updates. Our team will continue to provide status updates as they are received to the status page.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:52:18&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Intuit has reported that API functionality has returned, and calls should be completing as expected. Our internal teams have confirmed that syncs are running now running as expected. 

We advise Partners to compare data between ConnectBooster, and QuickBooks Online to ensure the data is up to date, and if not, to set their sync date back to 9/1/2026 - 1pm which was prior to the outage being reported by Intuit and allow for an accounting package sync to take place.

Thank you,.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:51:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 1 Sep 2026 21:49:24 +0000</pubDate>
  <link>https://health.compassmsp.com/incident/cmtkbybrp01z714qtfvruq5y5</link>
  <guid>https://health.compassmsp.com/incident/cmtkbybrp01z714qtfvruq5y5</guid>
</item>

<item>
  <title>DattoRMM - Vidal - Users are unable to access the platform.</title>
  <description>
    Type: Incident
    Duration: 10 days, 18 hours and 53 minutes

    Affected Components: RMM / Monitoring System
    Sep 1, 15:56:49 GMT+0 - Resolved - The issue affecting access to the Datto RMM Vidal platform has been resolved. Sep 1, 11:37:56 GMT+0 - Investigating - We are aware of a problem where users are unable to access the Vidal platform

The Kaseya Engineering Team is actively investigating and we will provide updates as more information becomes available.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/ Sep 1, 12:35:31 GMT+0 - Monitoring - The Kaseya Engineering Team has issued a fix. Service has been restored, and we are monitoring the environment to ensure continued stability. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 days, 18 hours and 53 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:56:49&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue affecting access to the Datto RMM Vidal platform has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:37:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of a problem where users are unable to access the Vidal platform

The Kaseya Engineering Team is actively investigating and we will provide updates as more information becomes available.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:35:31&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The Kaseya Engineering Team has issued a fix. Service has been restored, and we are monitoring the environment to ensure continued stability..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 1 Sep 2026 11:37:56 +0000</pubDate>
  <link>https://health.compassmsp.com/incident/cmtkbz1r801zp14qtctllce31</link>
  <guid>https://health.compassmsp.com/incident/cmtkbz1r801zp14qtctllce31</guid>
</item>

<item>
  <title>RMM - Vidal (US East) - Platform Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: RMM / Monitoring System
    Sep 1, 08:00:17 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug 31, 20:01:53 GMT+0 - Planned - In order to provide you with continued platform stability, we will be performing maintenance on this platform.

Expected Impact: Partners can expect devices to reconnect during this time, and in some cases devices may briefly go offline. CSM and Agent Browser sessions may close, and there may be a short period of reduced functionality.

Should you have any questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact Sep 1, 09:00:13 GMT+0 - Completed - The scheduled maintenance has been completed. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:00:17&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Scheduled maintenance is currently in progress. We will provide updates as necessary..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:01:53&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Planned&lt;/strong&gt; -
  In order to provide you with continued platform stability, we will be performing maintenance on this platform.

Expected Impact: Partners can expect devices to reconnect during this time, and in some cases devices may briefly go offline. CSM and Agent Browser sessions may close, and there may be a short period of reduced functionality.

Should you have any questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:00:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The scheduled maintenance has been completed..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 1 Sep 2026 08:00:00 +0000</pubDate>
  <link>https://health.compassmsp.com/maintenance/cmtkbz1ty01zt14qti05n9xn8</link>
  <guid>https://health.compassmsp.com/maintenance/cmtkbz1ty01zt14qti05n9xn8</guid>
</item>

<item>
  <title>Microsoft Exchange Online – Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 6 hours and 11 minutes

    Affected Components: Microsoft Cloud Services
    Aug 31, 17:37:51 GMT+0 - Investigating - We are aware of an ongoing issue affecting Microsoft Exchange Online. Users may experience degraded functionality with Exchange Online services. Microsoft is actively investigating the issue. We will provide updates as more information becomes available. Aug 31, 23:49:11 GMT+0 - Resolved - Microsoft has resolved the issue affecting Exchange Online. All Exchange Online services have been restored to normal functionality. We appreciate your patience and will continue to monitor the situation. Please reach out to us if you experience any further issues. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 11 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:37:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of an ongoing issue affecting Microsoft Exchange Online. Users may experience degraded functionality with Exchange Online services. Microsoft is actively investigating the issue. We will provide updates as more information becomes available..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:49:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Microsoft has resolved the issue affecting Exchange Online. All Exchange Online services have been restored to normal functionality. We appreciate your patience and will continue to monitor the situation. Please reach out to us if you experience any further issues..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 31 Aug 2026 17:37:51 +0000</pubDate>
  <link>https://health.compassmsp.com/incident/cmthiuc770aft1ao1hlgsqtv3</link>
  <guid>https://health.compassmsp.com/incident/cmthiuc770aft1ao1hlgsqtv3</guid>
</item>

<item>
  <title>Datto RMM / Datto EDR / Datto AV – Integration – Datto RMM Reporting Datto EDR and Datto AV Products as Not Detected</title>
  <description>
    Type: Incident
    Duration: 6 days, 21 hours and 59 minutes

    Affected Components: RMM / Monitoring System
    Aug 28, 10:30:39 GMT+0 - Investigating - We are investigating an issue affecting status reporting between Datto RMM, Datto EDR, and Datto AV. Some devices may generate alerts in Datto RMM reporting that Datto EDR or Datto AV is not detected.

Datto EDR and Datto AV remain installed and are operating normally on affected endpoints. This issue is limited to how their status is communicated to and displayed within Datto RMM and does not indicate a loss of endpoint protection.

Our Engineering teams are investigating this issue with high priority. We will provide further updates as more information becomes available.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/ Aug 28, 12:59:52 GMT+0 - Identified - We have identified an issue affecting status reporting between Datto EDR, Datto AV, and Datto RMM. As a result, some devices may incorrectly generate alerts in Datto RMM indicating that Datto EDR requires attention or that Datto AV is not installed.

Our investigation has confirmed that Datto EDR and Datto AV remain installed and functioning properly on affected endpoints. Endpoint protection services continue to operate as expected. The issue is limited to the status information being reported and displayed within Datto RMM and does not indicate a loss of protection or a failure of the Datto EDR or Datto AV products.

Engineering teams have identified the underlying cause and are actively working on a resolution. We will continue to provide updates as additional information becomes available.

If you have questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/ Aug 28, 20:33:17 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Aug 31, 13:40:38 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days, 21 hours and 59 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:30:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are investigating an issue affecting status reporting between Datto RMM, Datto EDR, and Datto AV. Some devices may generate alerts in Datto RMM reporting that Datto EDR or Datto AV is not detected.

Datto EDR and Datto AV remain installed and are operating normally on affected endpoints. This issue is limited to how their status is communicated to and displayed within Datto RMM and does not indicate a loss of endpoint protection.

Our Engineering teams are investigating this issue with high priority. We will provide further updates as more information becomes available.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:59:52&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified an issue affecting status reporting between Datto EDR, Datto AV, and Datto RMM. As a result, some devices may incorrectly generate alerts in Datto RMM indicating that Datto EDR requires attention or that Datto AV is not installed.

Our investigation has confirmed that Datto EDR and Datto AV remain installed and functioning properly on affected endpoints. Endpoint protection services continue to operate as expected. The issue is limited to the status information being reported and displayed within Datto RMM and does not indicate a loss of protection or a failure of the Datto EDR or Datto AV products.

Engineering teams have identified the underlying cause and are actively working on a resolution. We will continue to provide updates as additional information becomes available.

If you have questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:33:17&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  A fix has been implemented and we are monitoring the results..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 31&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:40:38&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 28 Aug 2026 10:30:39 +0000</pubDate>
  <link>https://health.compassmsp.com/incident/cmtkbz1sf01zr14qt71tvuli5</link>
  <guid>https://health.compassmsp.com/incident/cmtkbz1sf01zr14qt71tvuli5</guid>
</item>

<item>
  <title>ConnectWise PSA – Scheduled Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 minute

    Affected Components: CompassMSP Ticketing System
    Aug 24, 20:12:46 GMT+0 - Identified - We have scheduled maintenance on our ConnectWise PSA (Ticketing System) tonight from 7:00 PM to 11:00 PM ET. During this window, the ticketing system will be unavailable. Please plan accordingly and contact us via phone if you require immediate assistance. We appreciate your patience. Aug 24, 20:13:45 GMT+0 - Identified - We are extending our maintenance window by one hour due to an unexpected delay. The ConnectWise PSA (Ticketing System) is expected to be restored by 12:00 AM ET. We apologize for the inconvenience and appreciate your continued patience. Aug 24, 20:15:06 GMT+0 - Completed - Scheduled maintenance on the ConnectWise PSA (Ticketing System) has been completed. All systems are returning to normal operation. Thank you for your patience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:12:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have scheduled maintenance on our ConnectWise PSA (Ticketing System) tonight from 7:00 PM to 11:00 PM ET. During this window, the ticketing system will be unavailable. Please plan accordingly and contact us via phone if you require immediate assistance. We appreciate your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:13:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are extending our maintenance window by one hour due to an unexpected delay. The ConnectWise PSA (Ticketing System) is expected to be restored by 12:00 AM ET. We apologize for the inconvenience and appreciate your continued patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:15:06&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Scheduled maintenance on the ConnectWise PSA (Ticketing System) has been completed. All systems are returning to normal operation. Thank you for your patience..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 24 Aug 2026 23:00:00 +0000</pubDate>
  <link>https://health.compassmsp.com/maintenance/cmt7oalg200320krr0gsu0brl</link>
  <guid>https://health.compassmsp.com/maintenance/cmt7oalg200320krr0gsu0brl</guid>
</item>

<item>
  <title>DattoRMM - Vidal - Activity Log pages are slow to load</title>
  <description>
    Type: Incident
    Duration: 27 days, 13 hours and 57 minutes

    Affected Components: RMM / Monitoring System
    Aug 21, 17:17:03 GMT+0 - Monitoring - We are aware of a problem where the Activity Logs on our Vidal Platform are slow to load after our 15.1 release. 

The Kaseya Engineering Team has applied a fix and is currently monitoring this closely.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/ Aug 28, 18:43:01 GMT+0 - Resolved - The issue affecting Activity Log performance on the Vidal Platform following the 15.1 release has been resolved.

The Kaseya Engineering Team implemented a fix and has confirmed that Activity Logs are loading as expected after monitoring the platform to ensure ongoing stability and performance.

Should you have any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/ 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 27 days, 13 hours and 57 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:17:03&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We are aware of a problem where the Activity Logs on our Vidal Platform are slow to load after our 15.1 release. 

The Kaseya Engineering Team has applied a fix and is currently monitoring this closely.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:43:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The issue affecting Activity Log performance on the Vidal Platform following the 15.1 release has been resolved.

The Kaseya Engineering Team implemented a fix and has confirmed that Activity Logs are loading as expected after monitoring the platform to ensure ongoing stability and performance.

Should you have any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 21 Aug 2026 17:17:03 +0000</pubDate>
  <link>https://health.compassmsp.com/incident/cmtkbz1ql01zo14qtm5etv8vg</link>
  <guid>https://health.compassmsp.com/incident/cmtkbz1ql01zo14qtm5etv8vg</guid>
</item>

<item>
  <title>Datto RMM - Vidal - Post 15.1.0 Release - Activity Log Issues</title>
  <description>
    Type: Incident
    Duration: 25 days, 23 hours and 34 minutes

    Affected Components: RMM / Monitoring System
    Aug 18, 14:58:48 GMT+0 - Monitoring - A fix has been implemented for Activity Logs and they should be loading as expected.

A fix has also been implemented for Jobs not running, but delays are still expected as the platform works through all queued jobs. We will continue to monitor this queue and resolve this status page once it has cleared. Aug 18, 14:15:06 GMT+0 - Investigating - We are aware of a problem on Datto RMM&#039;s Vidal Platform where Jobs are not running and the Activity log can be slow to load.

The Kaseya Engineering Team are investigating the issue.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/ Aug 18, 14:52:33 GMT+0 - Investigating - We are continuing to investigate this issue. Aug 18, 15:48:40 GMT+0 - Monitoring - The Job queue has been cleared and Activity Logs continue to load as expected. We are continuing to monitor for any further issues. Aug 18, 17:13:46 GMT+0 - Identified - We have identified an issue with the Activity Log failing to load. 

The Kaseya R&amp;D team are working on a fix for the issue. Aug 18, 19:48:44 GMT+0 - Identified - We are continuing to work on a fix for this issue. Aug 19, 07:49:16 GMT+0 - Monitoring - A fix has been implemented for the Activity Log on the Vidal platform. The service has recovered and we are monitoring the results. Aug 19, 13:01:47 GMT+0 - Identified - Scheduled and Quick Job functionality is restored, and the Engineering team is continuing to work on resolving the problem causing issues with the Activity Log loading in accounts. Aug 19, 13:53:32 GMT+0 - Monitoring - A fix has been implemented for the Jobs and Activity Log on the Vidal platform and we are monitoring the results. Aug 19, 12:46:15 GMT+0 - Identified - The Engineering team is currently investigating and resolving issues flagged by internal alerting that led to the Activity Log loading and Job execution issues resurfacing.

Thank you for your patience! Aug 19, 21:01:46 GMT+0 - Monitoring - At this time, jobs and activity logs remain stable, and no further issues have been observed however we will continue to monitor the environment overnight. Aug 20, 12:38:40 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 25 days, 23 hours and 34 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:58:48&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  A fix has been implemented for Activity Logs and they should be loading as expected.

A fix has also been implemented for Jobs not running, but delays are still expected as the platform works through all queued jobs. We will continue to monitor this queue and resolve this status page once it has cleared..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:15:06&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of a problem on Datto RMM&#039;s Vidal Platform where Jobs are not running and the Activity log can be slow to load.

The Kaseya Engineering Team are investigating the issue.

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:52:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are continuing to investigate this issue..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:48:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The Job queue has been cleared and Activity Logs continue to load as expected. We are continuing to monitor for any further issues..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:13:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified an issue with the Activity Log failing to load. 

The Kaseya R&amp;D team are working on a fix for the issue..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:48:44&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this issue..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:49:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  A fix has been implemented for the Activity Log on the Vidal platform. The service has recovered and we are monitoring the results..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:01:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Scheduled and Quick Job functionality is restored, and the Engineering team is continuing to work on resolving the problem causing issues with the Activity Log loading in accounts..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:53:32&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  A fix has been implemented for the Jobs and Activity Log on the Vidal platform and we are monitoring the results..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:46:15&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The Engineering team is currently investigating and resolving issues flagged by internal alerting that led to the Activity Log loading and Job execution issues resurfacing.

Thank you for your patience!.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:01:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  At this time, jobs and activity logs remain stable, and no further issues have been observed however we will continue to monitor the environment overnight..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:38:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 18 Aug 2026 14:15:05 +0000</pubDate>
  <link>https://health.compassmsp.com/incident/cmtkbz1sj01zs14qtbe29456u</link>
  <guid>https://health.compassmsp.com/incident/cmtkbz1sj01zs14qtbe29456u</guid>
</item>

<item>
  <title>Test Maintenance – Phone System: 8x8 → Americas</title>
  <description>
    Type: Maintenance
    Duration: 5 minutes

    Affected Components: Phone System: 8x8 → Americas
    Aug 13, 16:15:00 GMT+0 - Identified - Maintenance is now in progress Aug 13, 16:18:10 GMT+0 - Identified - We are performing scheduled test maintenance on the 8x8 Phone System (Americas). During this window, phone services may be temporarily unavailable. We expect this maintenance to be completed within 1 hour. We apologize for any inconvenience. Aug 13, 16:19:04 GMT+0 - Identified - This maintenance window has been extended by one hour. The new expected completion time is 6:15 PM UTC. We appreciate your patience. Aug 13, 16:19:34 GMT+0 - Completed - This maintenance has been completed ahead of schedule. The 8x8 Phone System (Americas) is fully operational. Thank you for your patience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:15:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:18:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are performing scheduled test maintenance on the 8x8 Phone System (Americas). During this window, phone services may be temporarily unavailable. We expect this maintenance to be completed within 1 hour. We apologize for any inconvenience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:19:04&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  This maintenance window has been extended by one hour. The new expected completion time is 6:15 PM UTC. We appreciate your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:19:34&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  This maintenance has been completed ahead of schedule. The 8x8 Phone System (Americas) is fully operational. Thank you for your patience..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 13 Aug 2026 16:15:00 +0000</pubDate>
  <link>https://health.compassmsp.com/maintenance/cmsrq2jch00w60kpm1r5lhk2z</link>
  <guid>https://health.compassmsp.com/maintenance/cmsrq2jch00w60kpm1r5lhk2z</guid>
</item>

<item>
  <title>RMM / Monitoring System Scheduled Maintenance (test)</title>
  <description>
    Type: Maintenance
    Duration: 17 minutes

    
    Aug 13, 15:45:00 GMT+0 - Identified - Maintenance is now in progress Aug 13, 15:58:36 GMT+0 - Identified - We will be performing scheduled maintenance on our RMM / Monitoring System beginning at 15:45 UTC on August 13, 2026. The maintenance window is expected to last approximately 1 hour. During this time, monitoring and alerting functionality may be temporarily unavailable. We will update this page upon completion. Aug 13, 15:59:48 GMT+0 - Identified - The maintenance window for the RMM / Monitoring System has been extended. We now expect work to be completed by 19:00 UTC (2:00 PM CDT). We apologize for the extended downtime and will update this page upon completion. Aug 13, 16:00:29 GMT+0 - Identified - The maintenance window for the RMM / Monitoring System has been updated. We now expect work to be completed by 18:00 UTC (1:00 PM CDT). Aug 13, 16:02:01 GMT+0 - Completed - Scheduled maintenance on the RMM / Monitoring System has been completed. All systems are operational. Thank you for your patience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 17 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:58:36&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We will be performing scheduled maintenance on our RMM / Monitoring System beginning at 15:45 UTC on August 13, 2026. The maintenance window is expected to last approximately 1 hour. During this time, monitoring and alerting functionality may be temporarily unavailable. We will update this page upon completion..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:59:48&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The maintenance window for the RMM / Monitoring System has been extended. We now expect work to be completed by 19:00 UTC (2:00 PM CDT). We apologize for the extended downtime and will update this page upon completion..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:00:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The maintenance window for the RMM / Monitoring System has been updated. We now expect work to be completed by 18:00 UTC (1:00 PM CDT)..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:02:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Scheduled maintenance on the RMM / Monitoring System has been completed. All systems are operational. Thank you for your patience..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 13 Aug 2026 15:45:00 +0000</pubDate>
  <link>https://health.compassmsp.com/maintenance/cmsrpdczh00kg0rpmvlujdy2f</link>
  <guid>https://health.compassmsp.com/maintenance/cmsrpdczh00kg0rpmvlujdy2f</guid>
</item>

<item>
  <title>RMM / Monitoring System Scheduled Maintenance (test)</title>
  <description>
    Type: Maintenance
    Duration: 25 minutes

    
    Aug 13, 15:30:01 GMT+0 - Identified - Maintenance is now in progress Aug 13, 15:39:51 GMT+0 - Identified - We will be performing scheduled maintenance on our RMM / Monitoring System beginning at 15:30 UTC on August 13, 2026. The maintenance window is expected to last approximately 3 hours. During this time, monitoring and alerting functionality may be temporarily unavailable. We will update this page upon completion. Aug 13, 15:54:39 GMT+0 - Completed - Scheduled maintenance on the RMM / Monitoring System has been completed ahead of schedule. All systems are operational. Thank you for your patience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 25 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:30:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:39:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We will be performing scheduled maintenance on our RMM / Monitoring System beginning at 15:30 UTC on August 13, 2026. The maintenance window is expected to last approximately 3 hours. During this time, monitoring and alerting functionality may be temporarily unavailable. We will update this page upon completion..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:54:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Scheduled maintenance on the RMM / Monitoring System has been completed ahead of schedule. All systems are operational. Thank you for your patience..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 13 Aug 2026 15:30:00 +0000</pubDate>
  <link>https://health.compassmsp.com/maintenance/cmsrop94o00je0kpmovidfixm</link>
  <guid>https://health.compassmsp.com/maintenance/cmsrop94o00je0kpmovidfixm</guid>
</item>

<item>
  <title>Ticketing System – Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 1 minute

    Affected Components: CompassMSP Ticketing System
    Aug 13, 14:47:51 GMT+0 - Investigating - We are currently investigating slow response times affecting our ticketing system. Ticket submissions and responses may be delayed. We apologize for the inconvenience and will provide updates as our investigation continues. Aug 13, 14:48:52 GMT+0 - Resolved - We are pleased to confirm that the ticketing system has been restored to full performance. Ticket submissions and responses are operating normally. We apologize for any inconvenience this may have caused. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:47:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating slow response times affecting our ticketing system. Ticket submissions and responses may be delayed. We apologize for the inconvenience and will provide updates as our investigation continues..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:48:52&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We are pleased to confirm that the ticketing system has been restored to full performance. Ticket submissions and responses are operating normally. We apologize for any inconvenience this may have caused..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 13 Aug 2026 14:47:51 +0000</pubDate>
  <link>https://health.compassmsp.com/incident/cmsrmudw90cdh0zo9v0p42mry</link>
  <guid>https://health.compassmsp.com/incident/cmsrmudw90cdh0zo9v0p42mry</guid>
</item>

<item>
  <title>RMM / Monitoring System – Scheduled Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 3 hours and 45 minutes

    
    Aug 13, 14:45:00 GMT+0 - Identified - Maintenance is now in progress Aug 13, 14:52:47 GMT+0 - Identified - We are currently performing scheduled maintenance on our RMM / Monitoring System. During this window, remote monitoring and management functions may be temporarily unavailable or intermittent. We expect work to be completed by 16:45 UTC. We appreciate your patience. Aug 13, 11:00:00 GMT+0 - Completed - Maintenance has completed successfully Aug 13, 15:38:25 GMT+0 - Identified - Scheduled maintenance on the RMM / Monitoring System has been completed. All systems are operational. Thank you for your patience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours and 45 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:52:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are currently performing scheduled maintenance on our RMM / Monitoring System. During this window, remote monitoring and management functions may be temporarily unavailable or intermittent. We expect work to be completed by 16:45 UTC. We appreciate your patience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:38:25&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Scheduled maintenance on the RMM / Monitoring System has been completed. All systems are operational. Thank you for your patience..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 13 Aug 2026 14:45:00 +0000</pubDate>
  <link>https://health.compassmsp.com/maintenance/cmsrn0qii05ra0kk1xvh52zpp</link>
  <guid>https://health.compassmsp.com/maintenance/cmsrn0qii05ra0kk1xvh52zpp</guid>
</item>

<item>
  <title>DattoRMM - Vidal - ConnectWise Integration is inaccessible</title>
  <description>
    Type: Incident
    Duration: 5 days, 21 hours and 31 minutes

    Affected Components: RMM / Monitoring System
    Aug 11, 17:35:45 GMT+0 - Investigating - We are aware of a problem where the ConnectWise integration is returning an error on our Vidal platform. Users may see errors while viewing the integration page and ticketing can be affected.

The Kaseya Engineering Team is currently Investigating this issue

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/ Aug 11, 18:30:20 GMT+0 - Monitoring - We are no longer seeing errors related to the ConnectWise Integration. We are continuing to monitor the services at this time. Aug 12, 19:33:16 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 21 hours and 31 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:35:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of a problem where the ConnectWise integration is returning an error on our Vidal platform. Users may see errors while viewing the integration page and ticketing can be affected.

The Kaseya Engineering Team is currently Investigating this issue

Should you need any additional questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/contact

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 11&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:30:20&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We are no longer seeing errors related to the ConnectWise Integration. We are continuing to monitor the services at this time..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:33:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 11 Aug 2026 17:35:45 +0000</pubDate>
  <link>https://health.compassmsp.com/incident/cmtkbz1sb01zq14qtz61atnbc</link>
  <guid>https://health.compassmsp.com/incident/cmtkbz1sb01zq14qtz61atnbc</guid>
</item>

<item>
  <title>ConnectBooster  - Unable to log in via Kaseya One</title>
  <description>
    Type: Incident
    Duration: 18 days, 1 hour and 9 minutes

    Affected Components: Kaseya → Connectbooster → Portal
    Aug 6, 16:01:02 GMT+0 - Identified - The issue has been identified and a fix is being implemented. Aug 6, 17:19:25 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Aug 6, 17:19:35 GMT+0 - Monitoring - We are continuing to monitor for any further issues. Aug 6, 21:28:20 GMT+0 - Resolved - This incident has been resolved. Aug 6, 14:15:11 GMT+0 - Investigating - We are aware of a problem where Partners have reported the inability to log into the portal via Kaseya One 

The Kaseya R&amp;D Team is investigating the issue.

In the meantime, a workaround of logging directly into the ConnectBooster portal via the primary URL can allow you to log in without Kaseya One. please create a ticket with our Support team or contact them at 833-863-2237 if you need assistance with this process.

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/ Sep 3, 14:24:31 GMT+0 - Resolved - # 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 18 days, 1 hour and 9 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:01:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The issue has been identified and a fix is being implemented..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:19:25&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  A fix has been implemented and we are monitoring the results..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:19:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We are continuing to monitor for any further issues..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:28:20&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:15:11&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of a problem where Partners have reported the inability to log into the portal via Kaseya One 

The Kaseya R&amp;D Team is investigating the issue.

In the meantime, a workaround of logging directly into the ConnectBooster portal via the primary URL can allow you to log in without Kaseya One. please create a ticket with our Support team or contact them at 833-863-2237 if you need assistance with this process.

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:24:31&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  # 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..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 6 Aug 2026 14:15:11 +0000</pubDate>
  <link>https://health.compassmsp.com/incident/cmtkbybrt01z814qtktuauqsf</link>
  <guid>https://health.compassmsp.com/incident/cmtkbybrt01z814qtktuauqsf</guid>
</item>

<item>
  <title>KaseyaOne &amp; Kaseya Store - Issues with payment provider</title>
  <description>
    Type: Incident
    Duration: 8 days, 2 hours and 50 minutes

    
    Aug 6, 13:41:57 GMT+0 - Identified - Our payment provider for KaseyaOne and Kaseya Store has identified intermittent connectivity issues with our fraud prevention provider that might cause increased authentication declines.

During this time, users may experience intermittent issues related to payment processing in KaseyaOne and Kaseya Store.

Core platform functionality outside of payment services will remain unaffected.

We recommend avoiding payment-related actions during this maintenance window where possible. We will monitor the situation and provide updates if necessary. Aug 6, 16:56:47 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 days, 2 hours and 50 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:41:57&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our payment provider for KaseyaOne and Kaseya Store has identified intermittent connectivity issues with our fraud prevention provider that might cause increased authentication declines.

During this time, users may experience intermittent issues related to payment processing in KaseyaOne and Kaseya Store.

Core platform functionality outside of payment services will remain unaffected.

We recommend avoiding payment-related actions during this maintenance window where possible. We will monitor the situation and provide updates if necessary..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:56:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 6 Aug 2026 13:41:57 +0000</pubDate>
  <link>https://health.compassmsp.com/incident/cmtkc3vqm044l1nnwbysfowte</link>
  <guid>https://health.compassmsp.com/incident/cmtkc3vqm044l1nnwbysfowte</guid>
</item>

<item>
  <title>Microsoft Azure Outage in US West Impacting Multiple Kaseya Products</title>
  <description>
    Type: Incident
    Duration: 15 days, 4 hours and 21 minutes

    
    Jul 23, 15:15:08 GMT+0 - Investigating - We are aware of a problem where the KaseyaOne Portal is not accessible.

The Kaseya R&amp;D Team is investigating the issue.

Should you have any questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/phone

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

As a note; To ensure business continuity, for Kaseya modules using Require Log In with KaseyaOne, users must authenticate using their KaseyaOne Unified Login credentials.  Users added as exceptions can still log in using local module-specific credentials. Details are available in this Knowledge Base article: https://help.one.kaseya.com/help/Content/1_Configuration/enable-require-login-with-K1.htm 

We recommend adding a small set of users to the override list to maintain access in the event of a future disruption or maintenance, helping ensure continuous business operations Jul 23, 15:49:37 GMT+0 - Identified - We have verified that the KaseyaOne Portal is being impacted by the Microsoft Azure Outage.  
 
Please follow their Status Post as well for updates: https://azure.status.microsoft/en-us/status Jul 23, 17:06:16 GMT+0 - Identified - Kaseya R&amp;D are continuing to work closely with Microsoft Azure to resolve this issue affecting the KaseyaOne Portal. Jul 23, 18:26:09 GMT+0 - Identified - We have identified additional Kaseya Products that rely on Microsoft Azure Infrastructure that are affected by this issue.

Partners using Datto / Unitrends Backup for Microsoft Azure and Datto / Unitrends Endpoint Backup with Disaster Recovery in the US West region will experience issues with Device Check-In, Device Registration, and Back Up.

The Kaseya R&amp;D team are continuing to work with the Microsoft Azure team to resolve this issue and we hope to have updates on a resolution as soon as possible. Jul 23, 18:40:37 GMT+0 - Monitoring - A fix has been implemented by Microsoft Azure and we are monitoring the results.

Please refer to the Microsoft Status page here: https://azure.status.microsoft/en-us/status for more details Jul 23, 21:19:29 GMT+0 - Resolved - This incident has been resolved. Aug 10, 15:29:21 GMT+0 - Resolved - # Summary: 

Between 2026-07-23 14:44 UTC and 2026-07-23 19:41 UTC, KaseyaOne customers were unable to access the KaseyaOne Portal, and authentication into integrated applications that relied on KaseyaOne SSO was also impacted. 

# Root Cause: 

A network connectivity issue affecting the Microsoft Azure West US region caused service disruption for infrastructure supporting KaseyaOne. This resulted in loss of portal accessibility and SSO functionality until Microsoft restored regional connectivity. 

## Incident Timeline: 

* Identified: 2026-07-23 14:45 UTC 
* Public Notification: 2026-07-23 15:15 UTC 
* Resolved: 2026-07-23 19:41 UTC 

# Preventative Measures: 

To reduce the likelihood and impact of similar incidents in the future, we are making Enhancements to Infrastructure Resiliency. Specifically: 

* Implementing a multi-region deployment architecture with designated primary and disaster recovery regions. This enhancement will reduce reliance on a single Azure region and improve service availability during regional infrastructure failures. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 days, 4 hours and 21 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:15:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of a problem where the KaseyaOne Portal is not accessible.

The Kaseya R&amp;D Team is investigating the issue.

Should you have any questions or require assistance, please contact our support team at https://helpdesk.kaseya.com/hc/en-gb#/phone

Subscribe to the Kaseya Status Page for up-to-date information at https://status.kaseya.com/

As a note; To ensure business continuity, for Kaseya modules using Require Log In with KaseyaOne, users must authenticate using their KaseyaOne Unified Login credentials.  Users added as exceptions can still log in using local module-specific credentials. Details are available in this Knowledge Base article: https://help.one.kaseya.com/help/Content/1_Configuration/enable-require-login-with-K1.htm 

We recommend adding a small set of users to the override list to maintain access in the event of a future disruption or maintenance, helping ensure continuous business operations.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:49:37&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have verified that the KaseyaOne Portal is being impacted by the Microsoft Azure Outage.  
 
Please follow their Status Post as well for updates: https://azure.status.microsoft/en-us/status.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:06:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Kaseya R&amp;D are continuing to work closely with Microsoft Azure to resolve this issue affecting the KaseyaOne Portal..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:26:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified additional Kaseya Products that rely on Microsoft Azure Infrastructure that are affected by this issue.

Partners using Datto / Unitrends Backup for Microsoft Azure and Datto / Unitrends Endpoint Backup with Disaster Recovery in the US West region will experience issues with Device Check-In, Device Registration, and Back Up.

The Kaseya R&amp;D team are continuing to work with the Microsoft Azure team to resolve this issue and we hope to have updates on a resolution as soon as possible..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:40:37&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  A fix has been implemented by Microsoft Azure and we are monitoring the results.

Please refer to the Microsoft Status page here: https://azure.status.microsoft/en-us/status for more details.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:19:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:29:21&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  # Summary: 

Between 2026-07-23 14:44 UTC and 2026-07-23 19:41 UTC, KaseyaOne customers were unable to access the KaseyaOne Portal, and authentication into integrated applications that relied on KaseyaOne SSO was also impacted. 

# Root Cause: 

A network connectivity issue affecting the Microsoft Azure West US region caused service disruption for infrastructure supporting KaseyaOne. This resulted in loss of portal accessibility and SSO functionality until Microsoft restored regional connectivity. 

## Incident Timeline: 

* Identified: 2026-07-23 14:45 UTC 
* Public Notification: 2026-07-23 15:15 UTC 
* Resolved: 2026-07-23 19:41 UTC 

# Preventative Measures: 

To reduce the likelihood and impact of similar incidents in the future, we are making Enhancements to Infrastructure Resiliency. Specifically: 

* Implementing a multi-region deployment architecture with designated primary and disaster recovery regions. This enhancement will reduce reliance on a single Azure region and improve service availability during regional infrastructure failures..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 23 Jul 2026 15:15:08 +0000</pubDate>
  <link>https://health.compassmsp.com/incident/cmtkc3vsb044m1nnwp6qsffps</link>
  <guid>https://health.compassmsp.com/incident/cmtkc3vsb044m1nnwp6qsffps</guid>
</item>

<item>
  <title>Email Gateway Defense attachment file scanning partially impacted in the Australia region</title>
  <description>
    Type: Incident
    Duration: 14 days, 4 hours and 46 minutes

    Affected Components: Barracuda → Email Gateway Defense → Mail Delivery
    Jul 2, 03:25:14 GMT+0 - Investigating - We are currently investigating this issue. Jul 2, 03:27:49 GMT+0 - Monitoring - We are monitoring the results. Jul 2, 09:06:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 days, 4 hours and 46 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:25:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this issue..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:27:49&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We are monitoring the results..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:06:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 2 Jul 2026 03:25:14 +0000</pubDate>
  <link>https://health.compassmsp.com/incident/cmt7f19ki06xd0rnhbif5hsfs</link>
  <guid>https://health.compassmsp.com/incident/cmt7f19ki06xd0rnhbif5hsfs</guid>
</item>

<item>
  <title>Connectwse PSA Maintenance NOtificatoin</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: CompassMSP Ticketing System
    May 8, 14:00:00 GMT+0 - Identified - We are currently undergoing maintenance to our ticketing system. Replies may be delayed during this time. May 8, 14:00:01 GMT+0 - Identified - Maintenance is now in progress May 8, 15:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are currently undergoing maintenance to our ticketing system. Replies may be delayed during this time..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 8 May 2026 14:00:00 +0000</pubDate>
  <link>https://health.compassmsp.com/maintenance/cmovpkc6505pzcessvsu8kzug</link>
  <guid>https://health.compassmsp.com/maintenance/cmovpkc6505pzcessvsu8kzug</guid>
</item>

  </channel>
  </rss>