launchpad is still down (across all tested systems and global IPs I have access to) even though it is reported as up all day on https://status.canonical.com/
yes I am aware of Update concerning DDOS attack on Canonical and Ubuntu , however, this needs to be tracked publicly. If launchpad is known down, I don’t want to increase server loads by doing an apt update constantly to check if I can upgrade my packages, I would rather the status site actually report accurate information.
Launchpad is now up, i just installed some updates on my Stonking.
Working for me. Using my phone
You just have to be patient. Canonical has been having a DDOS attack for several days already.
It’s failing for me wrt aarch64. I guess x86_64 has (more) mirrors.
Seems partially restored however severely ratelimited. Downloads only occurring at ~100kB/s
Repeatedly getting
W: Failed to fetch https://ppa.launchpadcontent.net/dotnet/backports/ubuntu/dists/noble/InRelease Could not connect to ppa.launchpadcontent.net:443 (185.125.190.80). - connect (111: Connection refused)
Is that the DDOS problem, or something else?
Hello,
I think I face the same “problem”.
(Sorry for the links, I can’t post more than two as a new user)
status_canonical_com says that all server are in the green.
And
dnschecker says it can reach ppa_launchpadcontent_net in my country (France).
But when I do an apt update, I have this error :
Erreur fatale: E: https://ppa.launchpadcontent.net/phoerious/keepassxc/ubuntu questing InRelease is not (yet) available (Impossible de se connecter à ppa.launchpadcontent.net:http
s
And I can’t reach ppa_launchpad_net, nor ppa_launchpadcontent_net via Firefox neither.
That’s not critical because there is no keepassxc update for now, but I have to remove this ppa from apt sources list or I can’t update my Ubuntu at all.
I don’t think Ubuntu is blacklisting some countries or IPs because I tested from my work, and from my home, with two totally different providers, and same problem.
Thank you for any advice you can provide.
@nagle-animats and @gmifsud — Yes, it’s the DDOS. We have to be patient. For some bizarre reason, a group claiming to represent Iran is running DDOS against Canonical, attempting to extort it for money. I have no clue why, seeing as Canonical isn’t even in the US.
I would prefer to wait it out than have Canonical give in and pay.
Yes, I am finding the status page to be extremely confusing and contradictory. I am quite happy to wait until the “all clear” before running another sudo apt update but when one sees messages implying the issue was resolved I will run just in case it is right. It never is.
This is what happens when an external third party with bad intentions surprisingly points a bot army at you. It’s entirely possible that the Canonical engineering team mitigated the flood of bad packets, at which point status can be said to be “good”.
However, all it takes is for the bad actor to turn things up a notch, or point all their resources at one place, and things go down again. The status page is a guideline, and is also dependent on humans and other automated processes which may or may not be attacked at the time.
It’s not super productive for us to go back and forth suggesting it’s working, not working, working, not working, when the majority of the volunteers here do not have access to anymore information than the rest of the world.
So, I’ll leave the link here, for anyone following and close this thread. The following page is the best source of truth.
