a month ago
My service premcell_os is experiencing persistent build failures with repeated Metal builder rescheduling and no compilation output.
Failed deployments:
- 111a951d-9980-43ef-9e85-082a3b25616b (2026-07-16 22:57) — rescheduled 4 builders, no output
- ee6588b6-d294-495e-b792-8b1af0f87f84 (2026-07-16 17:52) — same pattern
Project & Service:
- Project: abundant-compassion (833484f7-1f20-492f-a905-fcf21a69d952)
- Environment: production (aab143f1-9768-4fc6-9483-27bc38dc7710)
- Service: premcell_os (94635495-3167-4a64-9f29-5f9d61dd0105)
- Repo: DevLuanguedes/premcell_os (main branch)
- Builder: RAILPACK
Important: The same commit (fb2607a225e4932e52a33c98411c2c330a3d141d) built and deployed successfully in deployment 83393d12-1880-4196-8fd6-5534c7ca140d (2026-07-15), so code is not the issue.
This is a Metal builder infrastructure problem that needs investigation.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Builds for services that deploy from GitHub started failing around 22:40 UTC because GitHub is having an API outage on their side. The build gets scheduled but we can't pull your code from GitHub, so it fails with no build logs. Your running services aren't affected.
We're tracking this at https://status.railway.com/incident/8BVRVAAM and GitHub's own status is at https://www.githubstatus.com/incidents/gxycch3076xk. Once GitHub recovers, pushing a new commit or redeploying will work again with no action needed on your end. If you need to ship right now, the CLI still works because it uploads your code directly: run railway up from your project directory.
Railway Team
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • 29 days ago