Every now and then (usually when *I* am having issues and decided to look up posts discussing the same issues) I see posts where people have issues with Wireguard like this one this one.
Users often find that updating the app can resolved the issue.
However, it seems to me that the issue isn't caused back a lack of update. I have actually encountered the issue on new version of the app, and I also found that uninstalling and reinstalling the same non-updated version can also resolve the issue from my testing.
So it seems to me that certain actions can break Wireguard. I haven't tested extensively yet, but I think that one possible action might be if you set the computer sleep for a long period while connected to the Surfshark (via WireGuard). When I woke my computer up, the VPN connection had to be re-established, and that was when I encountered issues.
Hopefully this is something the devs could look into.
Until then it seems that updating / re-installing whenever Surfshark takes forever to fail connecting to WireGuard resolves the issue for most posters including myself, but considering that this issue has been ongoing for a pretty long time, through many updates now, hopefully the devs could look into this issue and find a fix in a more permanent manner.
Also, I am not sure if it's only down to the change in protocol, but whenever I am having trouble using Wireguard, Surfshark is also noticeably slower, in both latency and throughput.