Transient APT repository errors on Termux 0.118.3 (packages-cf mirror) — appeared on startup, later upgrades succeeded

[Talash666]

• Short description:

On startup Termux suggested running termux-change-repo because of repository issues. I tried switching mirrors and updating; initially I saw repo errors (see apt-update.log). After switching and running pkg update && pkg upgrade the packages upgraded and installed successfully (see excerpt below).
I’m filing this for visibility and to provide logs in case there is an underlying mirror or repo configuration problem.
Device & Termux
Device: POCO 2207117BPG (Android 13 / SDK 33)
Termux app: com.termux 0.118.3 (F‑Droid build)
Subscribed repos: packages-cf termux-main, packages-cf termux-root, packages-cf termux-x11, tur-repo (tur.kcubeterm.com)
What I saw
On launch Termux showed: "For fixing any repository issues, try 'termux-change-repo' command."
I run termux-change-repo and then pkg update && pkg upgrade. At first there were repository errors (see apt-update.log). After trying mirrors the upgrade proceeded and finished; package setup output included many packages being unpacked and set up (excerpt below).
Excerpt from successful upgrade (for context)
Preparing to unpack .../19-qt5-qttools_5.15.18_aarch64.deb ...
Unpacking qt5-qttools (5.15.18) over (5.15.16-1) ...
...
Setting up tmux (3.6-1) ...
Setting up nodejs (24.11.1) ...
Setting up postgresql (17.0-5) ...
Setting up clang (21.1.6) ...
Processing triggers for mandoc (1.14.6-6) ...

Files / logs attached
termux-info: ~/termux-info.txt
apt update output: ~/apt-update.log
apt update output: ~/apt-update.log
Commands to run / reproduce
termux-change-repo
pkg update && pkg upgrade
termux-info > ~/termux-info.txt
apt update 2>&1 | tee ~/apt-update.log
/system/bin/logcat -d -t 3000 > ~/termux-logcat.txt

Steps I tried to fix
Run termux-change-repo and try official and alternate mirrors.
Run pkg update && pkg upgrade — packages were upgraded successfully.
Collected logs and termux-info for reporting.
Question / request
Was this a transient mirror issue or is there an underlying problem with the packages-cf mirror or repo configuration?
Anything else you want me to collect or try (specific mirrors, network checks, or config files)?
If you’d like, I can:
Produce the issue in a single copy-ready block (I already did), or
Walk you through opening the issue in your browser step by step.
Which do you want me to do next?

[sylirre]

You should use mirror located near your region rather than relying on central one.

The central repository hosted on one server but has two domains packages.termux.dev and packages-cf.termux.dev. The latter is a Cloudflare-backed endpoint used as default repository. However central repository mainly intended to be used for development purposes only, it is a place where packages being uploaded from CI/CD and then seeded to other mirrors. Its bandwidth is limited and it has no redundancy either.

If central server fails, the Termux package maintainers will be the first people who will face the issue. We don't need a notification from the users about this.

Please do what the app says:

For fixing any repository issues, try 'termux-change-repo' command.