this has been noticed multiple times recently in various tests. i think the source of the issue is something else because for some reason only the mobile instance is only connected to store nodes and not any bootstrap nodes (which then causes further issues because since there are peers available the node thinks it is online but peerexchange, lightpush and filter protocols won't work since there are no peers supporting those protocols)
similar issue noticed here status-im/status-go#5679 where there is DNS failure. this leads to only store nodes being connected which doesn't have peer-exchange enabled hence leading to failure of filter,lightpush and peerexchange client side protocols leading to reliability issues.

the logs that we are observing are side-effect of the issue which is somewhere i am suspecting is somewhere else in status-go code. Probable suspect is how the bootstrap nodes are set or something in the waku initialization sequence of status-go is failing and causing no other peers to be connected.

#21386 is the mobile PR that reduces log flooding and might provide some useful logs to help root-cause the issue i.e why node is able to connect to store nodes but no other bootstrap nodes.

#21386 is the mobile PR that reduces log flooding and might provide some useful logs to help root-cause the issue i.e why node is able to connect to store nodes but no other bootstrap nodes.

Thank you @chaitanyaprem! I have triggered e2e in this PR and faced the issue. I have attached logs in this comment, please take a look #21386 (comment)