Skip to content

SecurityNot yet confirmed elsewhere1 publisher2 min readPublished

Second DDoS this year disrupts Canonical's ubuntu.com and Ubuntu security advisory API

Canonical confirmed an October 8 DDoS attack on its websites, including ubuntu.com and the Ubuntu security advisory pages and API. OMG! Ubuntu put the downtime at a little over four hours in the second DDoS to hit Canonical this year.

The Watch · Security desk

How we use AISend a correction

Illustration accompanying Second DDoS this year disrupts Canonical's ubuntu.com and Ubuntu security advisory API
Generated illustration
Advisory API hit; Launchpad appeared unaffected The story has too few figures to chart, so this maps which Canonical services were disrupted, which were not, and what remains unshared.

OMG! Ubuntu says ubuntu.com, canonical.com, the blog, developer site and security advisory pages and API were disrupted. Launchpad and the Snap Store did not appear affected; a late-April attack took them down. Canonical has not shared the attack's size or origin.

Advisory API hit; Launchpad appeared unaffected
WhoHowKindClaim
ubuntu.com and canonical.comAmong the primary web properties OMG! Ubuntu says were disrupted, with the Ubuntu blog and developer siteexposure4
Ubuntu security advisory APIOMG! Ubuntu lists the security advisory pages and API among the disrupted web propertiesexposure4
Launchpad and the Snap StoreDeveloper-facing services that did not appear to be affected, SecurityWeek reportedcapability5
Launchpad, Snap Store in AprilTaken down in a more disruptive late-April attack that left some users unable to install Ubuntu updatesprecedent9
CanonicalHas not publicly shared the size or origin of the attack; no one appears to have taken creditdecision8

What happened

  • Launchpad and the Snap Store, Canonical's developer-facing services, did not appear to be affected.
  • On October 9 Canonical said its team was still bringing affected services back, though most were accessible again.
  • Canonical has not publicly shared the size or origin of the attack, and no one appears to have taken credit for it.
  • The late-April attack was more disruptive: it took down Launchpad and the Snap Store and left some users unable to install Ubuntu updates.

Why it matters

  • exposure Scanners, patch dashboards and compliance jobs that call Ubuntu's advisory API live depend on endpoints that were on the disrupted list.
  • decision Teams that poll that API have to choose between holding a local copy of the advisory data and accepting gaps in fix-status lookups the next time it is unreachable.
  • precedent Two attacks about five months apart give operators a rate to plan around, though no source links the two incidents.

Canonical's own statement was short. In a post on the Ubuntu Discourse forum, the company said, "Canonical's websites are under a sustained distributed denial of service attack," and added that some services might not be reachable at times [2][3].

The list of what was hit comes from OMG! Ubuntu, as relayed by SecurityWeek: ubuntu.com, canonical.com, the Ubuntu blog and developer site, and the security advisory pages and API [4]. The four-hour downtime figure is also OMG! Ubuntu's [7]. Both are single-sourced to that outlet.

April is the comparison. Canonical described that incident as a "sustained, cross-border attack" [9]. A hacktivist group calling itself The Islamic Cyber Resistance in Iraq - 313 Team claimed it [10]. SecurityWeek says it is unclear whether the two incidents are connected [12]. Nothing in the reporting ties the October attack to that claim.

For operators the exposure is narrow. A person reading an advisory page can retry later. A scanner, patch dashboard or compliance report that calls the advisory API live has nothing to work from while the endpoint is down, unless a copy exists locally. The advisory API was on the disrupted list [4].

The two attacks fall about five months apart [13]. In our view that is enough reason for any team that polls the advisory API to keep its own copy of the data.

What to watch

  • Whether Canonical publishes the size, origin or a post-incident account of the October 8 attack.
  • Whether any group claims the October attack, and whether that claim connects it to the 313 Team's April claim.
  • Any further outage of the security advisory pages or API, which would make three disruptions in a year.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence45
Adoption
Insufficient
Hype gap0
Incentives
Insufficient
Confidence55
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Canonical confirmed the DDoS attack on October 8 in a post on the Ubuntu Discourse forum.

    ReportedSupportedSource: Canonical, via Ubuntu Discourse post, as reported by SecurityWeekView cited source
  2. [2]

    "Canonical's websites are under a sustained distributed denial of service attack," the company said.

    ReportedSupportedSource: Canonical, Ubuntu Discourse post, as quoted by SecurityWeekView cited source
  3. [3]

    Canonical said some services might not be reachable at times.

    ReportedSupportedSource: Canonical, Ubuntu Discourse post, as reported by SecurityWeekView cited source

Sources

1 independent publisher whose own reporting we read for this story.

  1. securityweek.com

    1 article · October 12, 2026

    Canonical Websites Disrupted in Second DDoS Attack This Year

Share your take

Let Clarity write the post for you.

Signed-in readers get a short post drafted on this story in the register they choose — narrative, analytical, or a direct position — editable to the last word before it goes anywhere. The share buttons at the top of this story work without an account.

Topics and entities

Follow any of these and your For You feed starts watching them — no settings page required.

Topics

Entities

Loading related stories