Your Postgres service is currently in SLEEPING status. The serverless docs note that slept services are de-prioritized and in rare cases may require a rebuild to come back online. You can try a restart (not a redeploy) from the deployment's 3-dot menu in the dashboard or via railway restart in the CLI, as restarts reuse the existing image without triggering a new build. If a full redeploy is needed, the Free plan peak-hours restriction (08:00-20:00 SGT for Southeast Asia) only blocks during those hours, so you can redeploy outside that window.

I do not see a railway restart command in the CLI and neither does restart show up on the deployment's 3-dot menu

The restart option isn't available for sleeping deployments since the container is already stopped, so that suggestion was incorrect. When a serverless service won't wake from traffic, a redeploy is the required fix. On the Free plan, you can redeploy outside peak hours (before 08:00 or after 20:00 SGT), or upgrade to the Hobby plan to remove the restriction entirely.

I understand but there should be some way to allow waking a sleeping service if Railway itself has de-prioritized it.

There is currently no way to force-wake a serverless service that has stopped responding to traffic other than a redeploy. On the Free plan, you can redeploy outside peak hours (before 08:00 or after 20:00 SGT), or upgrade to the Hobby plan to remove the restriction entirely.

Looking for any user or Railway staff response

Is it possible to get a one time allowance to switch my region to something that has reduced overlap during my daytime?

Unfortunately, no, because if the Team did this for you, then the Team would need to do it for others.