Deploy to Asia region locked at peak Europe hours
fragerjap
FREEOP

22 days ago

Hello, my single service and volume are located in the Asia region but I cannot deploy new versions during peak times of another region (attachment).

My General setting Preferred Deployment Region - Southeast Asia, Singapore

My latest deploy in log: [Region: asia-southeast1]

Why am I still seeing the West peak hours warning, while trying to deploy latest commit at 8:40 pm at Singapore?

Attachments

Solved

4 Replies

Railway
BOT

22 days ago

The error message shows the deploy is targeting europe-west4-drams3a (EU West, Amsterdam), not Southeast Asia. The "Preferred Deployment Region" in your workspace general settings is only a default for newly created services. The actual region each service deploys to is controlled by the per-service setting under your service's Settings > Deploy > Regions. Please check that specific service's region setting, as it appears to be set to EU West rather than Southeast Asia, which is why the EU West peak hours restriction (8 AM - 8 PM Europe/Amsterdam) is blocking your deploy.


Status changed to Awaiting User Response Railway 22 days ago


fragerjap
FREEOP

22 days ago

My service's Settings > Deploy doesn't contain Regions option, it only appears in Scale for replicas, the info AI assistant provided may be outdated.

My Deployment tab shows asia-southeast1-eqsg3a though.


Status changed to Awaiting Railway Response Railway 22 days ago


22 days ago

You would need to be on a paid plan in order to bypass these restrictions.


Status changed to Awaiting User Response Railway 22 days ago


brody

You would need to be on a paid plan in order to bypass these restrictions.

fragerjap
FREEOP

22 days ago

I understand, thank you, but it would be nice to have a proper message for a free-plan, 'cos now it just says I'm trying to deploy to Europe during peak time, while actually deploying to Asia out of peak time (as follows from all the options and region log), this confusion generates questions.


Status changed to Awaiting Railway Response Railway 22 days ago


Status changed to Solved brody 22 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...