Hey there! We've found the following might help you get unblocked faster:

• 🧵 COntainer not loading my app. Suddennly stopped

• 🧵 Docker container being stopped after deployment

• 🧵 ParadeDB PostgreSQL Container Fails to Initialize Due to Volume Mount Issues

If you find the answer from one of these, please let us know by solving the thread!

Hi there, we sometimes rebalance the workloads on the platform as you see from the tooltip you have above your workload.

Since you are Hobby, we did redeploy your workload as you can see.

I don't mind the rebalancing. I'm saying that the service was not redeployed and just stopped. The next deployment was done from me manually after 1 hour.

Now I have 'This service was migrated to a legacy region in EU West'.

Can we investigate why the service was stopped and not redeployed as you're saying?
Also can you point me where exactly I can find the 'as you see from the tooltip you have above your workload.' because I'm not sure I'm looking on the right place?

Today we faced the same issue. The instance 5422726 suddenly stopped responding to the application. We tried to redeploy, but the next two deploys (bc66fb9 and 6becbb4) failed with
```
Pre-deploy › Migrate volumes (07:05)

Volume migration failed.
```
We had to wait a while so that the next deployment was successfull (24 minutes after the lasgt failed).

Can you elaborate what is happening? We have not changed anything on our side and there are suddenly some database problems.

Also the redeploys of the databases have changed the collation version so we had to take care of that too.

Hi Petar,

This was caused by an incident related to a single degraded host in EU earlier today: https://status.railway.com/cmelkuddv0004havczuftvf3w

We apologize for the inconvenience. If you experience this again, please let us know.

Regards,
Christian