sshd stops working after a period of time

[Arxhexa]

I'm already using sv-enable sshd to keep ssh running in the background. This works fine for a couple of hours but will fail after a longer period of time. I've checked files in $PREFIX/var/log/sv/sshd and it seems ok. Here are some lines:

2022-11-20_16:46:23.79949 Server listening on :: port 8022.
2022-11-20_16:46:23.80024 Server listening on 0.0.0.0 port 8022.
2022-11-20_16:46:29.39072 Accepted password for root from 10.23.7.31 port 1179 ssh2
2022-11-20_16:46:48.98431 Accepted password for root from 10.23.7.31 port 1182 ssh2
2022-11-20_16:57:41.23194 session_signal_req: session signalling requires privilege separation
2022-11-20_16:57:41.24203 session_signal_req: session signalling requires privilege separation
2022-11-20_16:57:41.24307 session_signal_req: session signalling requires privilege separation
2022-11-20_16:57:41.24348 Received disconnect from 10.23.7.31 port 1179:11: 
2022-11-20_16:57:41.24432 Disconnected from user root 10.23.7.31 port 1179
2022-11-20_18:36:58.51402 Accepted password for root from 10.23.7.31 port 2164 ssh2
2022-11-20_18:37:42.77302 session_signal_req: session signalling requires privilege separation
2022-11-20_18:37:42.77391 session_signal_req: session signalling requires privilege separation
2022-11-20_18:37:42.77435 session_signal_req: session signalling requires privilege separation
2022-11-20_18:37:42.77460 Received disconnect from 10.23.7.31 port 2164:11: 
2022-11-20_18:37:42.77529 Disconnected from user root 10.23.7.31 port 2164
2022-11-20_22:02:10.41650 Accepted password for root from 10.23.7.31 port 20722 ssh2
2022-11-20_22:02:16.79189 session_signal_req: session signalling requires privilege separation
2022-11-20_22:02:16.79238 session_signal_req: session signalling requires privilege separation
2022-11-20_22:02:16.79259 session_signal_req: session signalling requires privilege separation
2022-11-20_22:02:16.79277 Received disconnect from 10.23.7.31 port 20722:11: 
2022-11-20_22:02:16.79354 Disconnected from user root 10.23.7.31 port 20722
2022-11-21_00:44:20.35834 Accepted password for root from 10.23.7.31 port 12540 ssh2
2022-11-21_00:44:28.10984 session_signal_req: session signalling requires privilege separation
2022-11-21_00:44:28.11039 session_signal_req: session signalling requires privilege separation
2022-11-21_00:44:28.11061 session_signal_req: session signalling requires privilege separation
2022-11-21_00:44:28.11118 Received disconnect from 10.23.7.31 port 12540:11: 
2022-11-21_00:44:28.11193 Disconnected from user root 10.23.7.31 port 12540

But when I woke up the next day, ssh had stopped working. It's been like this for days, and once I opened a new session sshd came back. I checked sv status sshd when I knew it stopped working and it gave back runsv not running.
Anywhere I can see the logs of runit?
Some termux-info

Termux Variables:
TERMUX_APP_PACKAGE_MANAGER=apt
TERMUX_MAIN_PACKAGE_FORMAT=debian
TERMUX_VERSION=0.118.0
Packages CPU architecture:
aarch64
Subscribed repositories:
# sources.list
deb https://packages-cf.termux.dev/apt/termux-main stable main
Updatable packages:
libmpfr/stable 4.1.1-1 aarch64 [upgradable from: 4.1.0-1]
termux-tools version:
1.31.1
Android version:
8.1.0
Kernel build information:
Linux localhost 4.9.82-perf+ #2 SMP PREEMPT Fri Sep 24 18:34:23 CST 2021 aarch64 Android

Extra: I've disabled doze mode on Android and I have two other network related processes remain safe in ubuntu provided by proot-distro.