[09:20] Hello! I have some virtual image builds that are failing today because of this error: "Could not connect to ppa.launchpad.net:80 (185.125.190.80), connection timed out". Are there any issues at the moment? I got errors like this yesterday too, in the maintenance window. [09:30] For example, I'm unable to fetch http://ppa.launchpad.net/deadsnakes/ppa/ubuntu/pool/main/p/python3.9/libpython3.9-stdlib_3.9.19-1+focal1_amd64.deb [09:53] (I had to reboot the machine - if someone answered me above then please post again) [10:03] Guest30: this is an unplanned outage - IS team is already working on getting things up again - thank you for your understanding [10:11] Thank you for confirming! It's helpful just to be aware of it :) [10:55] Guest30: is it working now? [11:19] Hey! Are you having problems with PPA, please? We are seeing the following. Cannot initiate the connection to ppa.launchpad.net:80 - connect (101: Network is unreachable) Could not connect to ppa.launchpad.net:80 connection timed out [11:30] Hey! Guest36 it should be working now [14:44] hi, I still keep getting 14.46 E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/main/binary-amd64/Packages.gz File has unexpected size (2018947 != 2018948). Mirror sync in progress? [IP: 91.189.91.83 80] even tho ubuntu canonical health says everything's operational?? [14:45] been getting errors since 5 hours ago, but the incident on https://status.canonical.com/ was already closed? is there a separate status page for this?? [14:47] or is this even a launchpad thing.. [14:57] nvm seems to be working now i think [21:47] vincejv: amazing that one byte moved around .. i've seen errors like this come from broken transparent proxies run by ISPs trying to reduce bandwidth on their networks, sometimes they can be very challenging to track down [21:48] vincejv: do you get errors like this often or was this the first?