Is there a problem with archive.ubuntu.com?

That just throws an http 500 for me.

1 Like

Usually waiting it out is the best solution.

I am sure the issues will be resolved soon.

Thanks for understanding.

It’s been now down for more than 4 hours, maybe more.

https://status.canonical.com/ has nothing to say about it.

  • At the beginning it was downloading with 18.6 kB/s.
  • Then it was ā€œinternal server errorā€.
  • Now it’s back to 18.6 kB/s.

Not sure if that can be called a progress.

Edit:

I have fresh workstation setup waiting for this to resolve, in the meantime it’s unusable…

The best I can offer is this:

4 Likes

Thanks!
Though that’s some wild time frame.

Edit:

Now I’m down to 12.0 kB/s :smile:
Are we ddos’ing it by any chance?

A fluctuationi between 12 and 16 kBps is not a significant change. There are a LOT of things being processed in the backlog for publishing to the servers which also takes bandwidth. Best we can do is say ā€œbe patientā€.

2 Likes

Thanks for the updates, I’m seeing the same on my end…

Err:1 http://security.ubuntu.com/ubuntu noble-updates/main amd64 linux-firmware amd64 20240318.git3b128b60-0ubuntu2.17
  500  Internal Server Error [IP: 91.189.91.83 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/l/linux-firmware/linux-firmware_20240318.git3b128b60-0ubuntu2.17_amd64.deb  500  Internal Server Error [IP: 91.189.91.83 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
2 Likes

I have the same issues but with another URL where Ubuntu 22.04 installation is failing with HTTP 500 error to unable to download the package.

The URL that is returning the installation error is - https://us.archive.ubuntu.com/ubuntu/pool/main/l/linux-firmware/.

Attaching the screenshot for reference:

3 Likes

Enabling slow mode. ā€œMe tooā€ posts are completely unnecessary. Please read the entire thread before posting and make sure you’re not just saying ā€œme tooā€ as it adds nothing to the discussion.

Please think about what you write and decide if it adds to the conversation or not. If it’s just a repeat of what’s already been said, please refrain from posting.

Refer to this post on AskUbuntu by @teward :


At the time of this post and answer (September 5, 2025, at approixmately 10:40 UTC-4), it is known to Canonical and many people who are actively working on development, patching, etc. that there was an outage on the primary public repository servers. All security updates and other update pockets were unavailable, and the upload / processing queue for Security updates among others was obscenely backlogged as a result of the outage.

This was reflected on https://status.canonical.com as acknowledged incidents:

Both of these incidents were marked resolved after 36 minutes of outage time at approximately 04:30 UTC-4.

However, it is known that the backlog caused by the outage is causing the mirrors and security updates to be ā€˜broken’ at this time due to the backlog in the queue for processing. This queue is currently very large and there is likely to be issues with mirrors at this time during the update process. As such, you need to be patient and try again several hours from now (up to 24 hours from now as well if you want, just to make sure stuff stabilizes first).

There is nothing you can currently do about this except wait it out. Mirrors that synced during the outage time or are mid-sync right now during the large queue backlog may get the 500 errors as well on the mirrors.


Again, please think about what you write if it adds to this or not. If it’s a repeat of what’s already been said, please refrain from posting.

11 Likes

Looks like security is having issues too, https://status.canonical.com/ does NOT reflect any outages, even though they are occurring.

2 Likes

That’s because it’s resolved, and everything lingering is just mirrors syncing and queues emptying. It takes time!

1 Like

I can confirm that this problem is still present.

E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/l/linux-firmware/linux-firmware_20220329.git681281e4-0ubuntu3.39_all.deb 500 Internal Server Error [IP: 185.125.190.81 80]

Regards

3 Likes

Closing this topic. We don’t need a bunch of ā€œCan Confirmā€ and ā€œme tooā€ posts. Instructions were given as to what needs to happen as 1) a workaround, and 2) what you need to do to get the repos working (you can’t).

The pinned topic on this is Current Status Of Ubuntu Update Errors: Please Read! and comments are closed there to avoid useless discussion.

2 Likes