3 hours ago
Hello Railway Support Team,
Deployment IDs:
3531c44b-ebba-4bf4-9b74-4a1d9595bece
6fd5c5fc-da4f-45e2-9807-47f15994481e
ceb90494-6049-40ed-b39c-5d3b5a6f882a
You stated that CLI-triggered deployments are not affected by the GitHub outage.
Could you please clarify why our CLI-triggered builds failed and whether these specific deployments were actually affected by the incident?
If they were unrelated to the outage, we would appreciate an investigation into the underlying build worker error and termination logs.
Could you please escalate this case to your technical engineering team for further investigation?
Our Production service remains operational, but we cannot safely deploy updates until this issue is resolved.
Best regards,
IBSMO Technical Team
6 Replies
3 hours ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 3 hours ago
0x5b62656e5d
Can you share the build logs?
2 hours ago
Three CLI-initiated Production builds failed: 3531c44b-ebba-4bf4-9b74-4a1d9595bece, 6fd5c5fc-da4f-45e2-9807-47f15994481e, and ceb90494-6049-40ed-b39c-5d3b5a6f882a. All completed npm ci --include=dev. The first two Turbopack logs stop at “Creating an optimized production build ...”; the Webpack attempt then reports exit code: 1 without a compiler diagnostic. Sanitized build logs are attached. Could you check unfiltered stderr, the build worker’s termination reason, and any OOM, timeout, or infrastructure event? We were told the GitHub incident did not affect CLI deployments; how, if at all, does it relate to these failures?
2 hours ago
Could you reattach the logs? Not sure if it got uploaded properly.
Also, does the build work locally?
0x5b62656e5d
Could you reattach the logs? Not sure if it got uploaded properly. Also, does the build work locally?
2 hours ago
yep I am working locally
Three CLI-initiated Production builds failed:
3531c44b-ebba-4bf4-9b74-4a1d9595bece
6fd5c5fc-da4f-45e2-9807-47f15994481e
ceb90494-6049-40ed-b39c-5d3b5a6f882a
All three successfully completed npm ci --include=dev.
The first two builds (Turbopack) stopped at "Creating an optimized production build ...". The third attempt used Webpack and exited with code 1, without a compiler diagnostic.
The same application package builds successfully in an isolated Linux x86_64 environment using Node.js 24/npm 9, including TypeScript validation and page generation.
Production uses Nixpacks, while our working Staging environment uses Railpack.
I've reattached the sanitized build logs.
Could you please investigate:
The unfiltered build stderr output.
The build worker's termination reason.
Any OOM, timeout, or infrastructure-related events.
Whether the GitHub outage could have affected these specific CLI-triggered builds, despite the earlier statement that CLI deployments were unaffected.
Could you also confirm that the attached logs are visible?
Thank you for your help.
2 hours ago
I recommend using Railpack or a Dockerfile, as Nixpacks is deprecated.
(And if you’re attaching the build log as a file, try uploading it as a .txt. Somehow still not able to see any attachments being uploaded…)
0x5b62656e5d
I recommend using Railpack or a Dockerfile, as Nixpacks is deprecated. (And if you’re attaching the build log as a file, try uploading it as a `.txt`. Somehow still not able to see any attachments being uploaded…)
2 hours ago
Thank you for the recommendation.
Our Staging environment already uses Railpack successfully, while Production is still using Nixpacks.
We'll prepare and validate a Railpack-based deployment in an isolated test service before making any changes to Production.
I'll also convert the sanitized build logs to .txt files and try uploading them again.
Thanks for pointing us in the right direction!