24 days ago
Workspace: Lever Tech's Projects (13af77e8-890f-4f61-aa18-dd05d57f432c)
Project: Projetos Lever (d87c5720-dde5-465a-9f3a-fdf5bb42e08e)
Service: fg-atacado (f834436c-9c12-4317-bf8b-7d31f7bf9deb)
4 consecutive deploy failures today in us-west2 with "No space left on device" — both Nixpacks (nix store) and Railpack (apt cache) hit the same error, meaning the builder host disk is full systemically, not a per-builder issue.
Deployment IDs: 2b842893, df789c33, 7f05840c, 050c61b1
Just upgraded to Pro to unblock. Have a client delivery call in a few hours. Please rotate the builder pool or migrate me to another region.
1 Replies
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
Your build failures are caused by a platform-side issue currently affecting build infrastructure, not your configuration. You can follow progress here: https://status.railway.com/incident/KVZ1Z8GY
Pro plan builds are still processing but under degraded conditions. As a workaround, you can try switching your service's deploy region (found under the Scale section of your service settings) to route builds through a different builder pool.
Status changed to Awaiting User Response Railway • 24 days ago
Status changed to Solved sam-a • 24 days ago