I’m experiencing slow response and timeouts from us.archive ?
sudo apt update ; sudo apt upgrade
Warning: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/stonking/InRelease Unable to connect to us.archive.ubuntu.com :http: [IP: 185.125.190.83 80]
Warning: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/stonking-updates/InRelease Unable to connect to us.archive.ubuntu.com :http: [IP: 185.125.190.83 80]
Warning: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/stonking-backports/InRelease Unable to connect to us.archive.ubuntu.com :http: [IP: 185.125.190.83 80]
Warning: Some index files failed to download. They have been ignored, or old ones used instead.
Are there any known issues with the load balancing of the Ubuntu update servers in the US ?
Do you use a proxy or similar for internet access? Are there any firewalls in the mix here?
Stonking is still in development, moved to Project Discussion > Pre-Release Discussion
Sometimes, waiting a few hours and trying again resolves the issue.
No proxies and no additional firewalls other than existing hardware firewall which has not changed.
Anyway I switched to http://mirrors.mit.edu/ubuntu and updates work fine so I have a work around to use a different mirror.
Anyone know the proper channels to contact us.archive mirror owners ?
First step for most outages is indeed to double-check that your networking is working properly. Well done!
Second step should be status.canonical.com
Let’s see what they have to say about archive.ubuntu.com …
So you’re right, there was some downtime earlier. And Canonical IS is (was) aware of it.
The tracker is not instant. There’s a lag, so patience is appreciated. If the outage confounding your workflow lasts more than a few hours, and still hasn’t appeared on the tracker, it’s appropriate to raise the issue here on Discourse.
2 Likes
Thanks for the quick reply!
system
Closed
August 5, 2026, 6:12pm
7
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.