Hi, my service has been running happily for 5 months, but the most recent deployment says “Unhealthy.” I did a re-deploy and it is just stuck in “starting” without any logs or anything. Seems like a possible infrastructure issue, but the status page says everything is ok.
Can someone please help?
Thanks
Hi David, looks like we’re in the same boat, we had 2 services like that.
I started looking into it 2 hours ago, and now somehow after a lot of redeploys & pause & resumes I’ve got them started.
One took 12 minutes to start, the other 18.
But: not sure why it started working suddenly.
Thanks. I am looking at the deployment through the CLI as well, and it doesn’t provide much more details as far as what the problem is. I’ll keep trying to redeploy since that has worked for you. What region are you in? I am in Washington, D.C. so I wonder if it localized to that region.
I’m in Frankfurt.
Just saw this comment from a Koyeb team member - system is under high load and situation should get better again:
I had a ver similar thing happen. My service randomly went “unhealthy”, and now will not start back up. Stuck in starting for 30 minutes now. If this is a known issue, the status page should be updated.
Mine just finally succeeded. Completely agree with the status page not reflecting what is going on. I understand that issues can occur, but you need to have visibility into when they are occurring otherwise you get a bunch of these types of messages.
Hello, we did have some delays on provisioning this weekend, the incident is now resolved