MSP

ConnectWise is investigating recent attempts of unauthorized access associated with the ConnectWise Cloud Backup environment. Upon detecting this threat, we promptly initiated our incident response procedures. Containment measures are in place, and our investigation continues. At this time, there is no indication that partner backup data has been accessed. Our engineering teams are continuing to explore the nature and scope of the issue. Our investigation is ongoing, and we will provide additional information as appropriate. We appreciate your patience while we work through this process. Indicators of Compromise (IOCs) The following indicators have been associated with the reported suspicious authentication activity . Source IP Address 144.172.64.128 Observed User Agents Python-urllib/3.12 python-requests/2.31 These indicators are provided transparency to assist with security monitoring and investigation. Their presence alone does not establish unauthorized activity or confirm compromise.

Some Dependabot alerts continue to be delayed in closing after repository updates address a vulnerability. We're continuing to investigate and work to restore normal processing.

We're aware of recently announced PHP vulnerabilities. We have mitigations in place, and have patched our managed services, including Web Hosting and Managed Hosting for WordPress. If you manage your own server or VPS, you'll need to apply the PHP update yourself. Latest updates and steps can be found at https://www.godaddy.com/resources/news/important-php-security-update-what-website-owners-need-to-do

The root cause has been identified as undersea cable issues affecting Azure infrastructure. The impact is highest for South Africa, which has the longest network path to Australia. Requests from South Africa to Azure DevOps organizations hosted in Australia are seeing an availability impact of around 6%. We expect improvement by October 26 and further recovery by November 4, though both dates are tentative due to technical complexity of the issue itself.

We are providing an update on the disruption affecting the Middle East (UAE) (me-central-1) Region. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in the mec1-az2 Availability Zone. We continue to work on recovering regional resources, as well as zonal resources hosted in the other affected Availability Zones (mec1-az1 and mec1-az3). Since the disruption began in March, most customers have been able to re-establish their operations in other Regions by restoring backups or copying data that remained accessible. AWS Support remains available to help customers who need assistance moving their applications to alternate Regions. We remain committed to supporting our customers in the UAE. We are working on replacing the affected infrastructure and will provide an update on the restoration of our services in the coming months. We have notified the relevant authorities and continue to work with them toward that goal.