Quick update:
Not much success here. The issue is likely a bug in the latest version of the web framework I updated to a few weeks back. Can’t rule out it’s triggered by something on my end of things, but so far I’ve failed to identify the root cause. To be continued…
The service is now under their watchful eye as well. On top of that, I have set up better health checks and automated restarts should the service become unresponsive. Let’s see how this goes…