I don’t see any findings other than you seeing process hangs. Many things could cause that, for example a database read or write taking “forever” for whatever reason.
What you could do is run with --debug-profiler-listen ($STPROFILER) and see if you can talk to the profiler when it’s hung. For example if you run it with STPROFILER=localhost:9090 you can get a goroutine trace at http://localhost:9090/debug/pprof/goroutine?debug=1. That would show what is wedged where.
If it’s dead enough that you can’t even talk to the profiler then your culprit is in the Go runtime or the OS, and we can’t help you any more.