Orphaned container still running
lovetimo0421
PROOP

a month ago

On 2026-06-17 we deleted the our service in asia-southeast1-eqsg3a, europe-west4-drams3a, and us-east4-eqdc4a but they are orphaned containers. We only left the US west server. They don't appear in our dashboard but are still running today, we can prove it from their telemetry. Please terminate all container instances of our project outside our configured us-west2 replicas. By the way this ticket service selection is also non sense, i can't even find the exact service i want to select. Its suppose to be the natural-transformation/yumina/production. But i cant find it

Solved

1 Replies

Status changed to Awaiting Railway Response Railway 26 days ago


sam-a
EMPLOYEE

25 days ago

Those containers aren't orphaned. They belong to two PR environments that are still open in your project: yumina-pr-12 and yumina-docs-pr-1. Both have yumina deployments from early/mid June that still carry the old 4 region config, so they're running in asia-southeast1, europe-west4, and us-east4 alongside us-west2.

Your production environment is correctly running only us-west2 with 2 replicas, so the region removal there did go through.

To stop the extra containers, delete those two PR environments (or close the PRs that created them). If you want to keep the environments, remove the extra regions in each one's service settings, since PR environments keep their own region config.

Railway Team


Status changed to Awaiting User Response Railway 25 days ago


Railway
BOT

18 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 18 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...