You are not logged in.
> cat /etc/pacman.d/mirrorlist
Server=https://archive.archlinux.org/repos/2026/04/12/$repo/os/$arch
> sudo pacman -Syu
:: Synchronizing package databases...
core.db failed to download
extra.db failed to download
error: failed retrieving file 'core.db' from archive.archlinux.org : The requested URL returned error: 404
error: failed retrieving file 'extra.db' from archive.archlinux.org : The requested URL returned error: 404
error: failed to synchronize all databases (failed to retrieve some files)This started happening yesterday, i.e. pointing my mirrorlist to `2026/04/11` will result in the exact same 404s. When I switch back to `2026/04/10`, though, everything is working perfectly fine again.
A quick test with `curl` also confirms that something seemingly broke on the 11th:
> curl -s -o /dev/null -w "%{http_code}\n" https://archive.archlinux.org/repos/2026/04/10/core/os/x86_64/core.db
200
> curl -s -o /dev/null -w "%{http_code}\n" https://archive.archlinux.org/repos/2026/04/11/core/os/x86_64/core.db
404
> curl -s -o /dev/null -w "%{http_code}\n" https://archive.archlinux.org/repos/2026/04/12/core/os/x86_64/core.db
404Interestingly enough, when I open https://archive.archlinux.org/repos/202 … /os/x86_64 in a web browser, the directory listing has an entry for `core.db`, but clicking on it also causes a 404.
Is anybody else experiencing the same issue right now?
Offline
Is anybody else experiencing the same issue right now?
Yes, seems a problem w/ the snapshot of the last two days - other files you'd expect in those paths are just missing and the present directory entries are undersized.
Offline
What would be the recommended way to report this issue to the Arch team, in case they're not aware of it already?
Offline
Probably https://gitlab.archlinux.org/archlinux/ … work_items (there's a related bug from 2019 in there)
Offline
Thanks for pointing me in the right direction. I don't have an account set up over there yet; I'll go ahead and create one tomorrow.
Offline
Account creation unfortunately can take a while (14d+)
If this isn't fixed after the weekend (in 24h) please bump this thread to remind me to file a bug.
Offline
Unfortunately, the problem still persists with snapshot `2026/04/13`.
please bump this thread to remind me to file a bug.
Thank you, I'd highly appreciate that.
I'll try to get my account set up and approved in the meantime.
Offline
Thanks.
https://gitlab.archlinux.org/archlinux/ … _items/437 - now let's see ![]()
Offline
This is still happening and the ticket hasn't been touched in 5 days, perhaps it needs to be bumped?
Offline
Bumped/inquired at https://gitlab.archlinux.org/archlinux/ … ote_456204 which happened around the same time.
Offline
Offline
Hopping in on this as I believe I may be encountering this issue.
I had just commented on the topic in IRC.
I just didn't know if this was the first time ever that I would've encountered a file so freshly built that didn't yet sync with the providing mirror I chose.
I was updating, when I encountered a 404, even though I used `-Sy`, but even with `-Syy`, I was still getting a 404 for `jq-1.8.1-2-x86_64` package at the kernel.org mirror (also `libqaccessibilityclient-qt6-0.6.0-3-x86_64` when testing more).
I started uncommenting servers I thought would be reasonable, but more 404's for the jq package kept adding up.
I then used `--debug` and sed uncommented every server, and there were like 21 servers that 404'd before getting to `mirror.xeonbd.com` which had it I guess, but errored with: `Exceeded the maximum allowed file size (16384) with 16384 bytes` for the sig file. Same with the `au.mirrors.cicku.me` mirror.
The jq and accessibility packages were considered corrupt so were deleted and re-downloaded.
I kept those unproblematic mirrors uncommented and got all of the packages now, and it's now starting the unpacking step.
Offline
Your issue would be unrelated to archive.archlinux.org as you are dealing with mirrors, not the Arch Linux archive.
Offline