oak pumice
My deployment has been stuck for 15+ minutes on container creation/starting phase.
Service: faicy-server (faicy.up.railway.app)
Region: us-east4-eqdc4a
Build completed successfully in ~40s (all cached), but deployment is stuck after "image push" step. It's not progressing to "Creating containers" or starting the service.
Previous deployment works fine.
Should I try redeploying or is there a known issue?
Update: Tried redeploying - getting "Container failed to start" → "Failed to create deployment"
Build completes successfully, image pushes fine (98.6 MB), but then Railway waits 27 minutes and fails with "Container failed to start".
This is clearly an infrastructure issue in us-east4 region. Can someone from Railway team look into this?
lethal meteor