563/69 Wednesday, October 14, 2026
Canonical, the parent company of Ubuntu, disclosed that its websites were continuously targeted by a Distributed Denial-of-Service (DDoS) attack on October 8, 2026, marking the second DDoS incident affecting the company’s infrastructure this year. Canonical stated through Ubuntu Discourse that its team was working to mitigate the incident and that some services might be intermittently unavailable. At this time, no cybercriminal or hacktivist group has claimed responsibility for the attack.
The attack affected several of Canonical’s main public-facing websites, including ubuntu.com, canonical.com, the Ubuntu Blog, the Developer Portal, as well as security advisory pages and related APIs. As a result, some users were temporarily unable to access security announcements or website content. Other related domains and services, including assets.ubuntu.com, academy.canonical.com, and enterprise technology websites such as jaas.ai and maas.io, were also reported to have been affected. Overall, the disruption lasted for more than four hours.
However, Canonical stated that its distributed infrastructure helped limit the impact of the incident, allowing several critical services to remain operational. Launchpad and the Snap Store continued functioning throughout the attack, while software repositories, mirror servers, disk image servers, and Ubuntu Single Sign-On also remained available. This meant that users could still download and install packages or software updates despite partial disruption to Canonical’s public websites. The incident differed from the April 2026 attack, which had a more significant impact and caused Launchpad and the Snap Store to become unavailable. That earlier attack was claimed by a hacktivist group known as Islamic Cyber Resistance in Iraq, or 313 Team. It remains unclear whether the latest attack is connected to the previous incident or was carried out by a different actor.
Source: https://securityaffairs.com/200832/security/canonical-hit-by-second-ddos-attack-in-2026.html