There are two kind of bugs: in the app and in the setup (the config + data). If it’s in the app, it will be on all setups in sleeping or an active state. The more common bug is in a setup.
To claim the bug, it need to be reproduced, otherwise the fix would not be implemented fast enough.
Thank you for confirming, that you do not have this issue too. So far it looks like related to the data or config of this particular node.
Unfortunately this cannot be classified as a bug per se. You may get the same behavior if you specify a wrong external address or port, your logs blows up with messages “ping satellite failed”.
The logs are used to identify the issue, silencing them is not a solution. OP can silence them by the way, either globally reducing the log level to none or partially using --log.custom-level
But I prefer to find a root cause instead.