a month ago
Hi Railway team,
Since the major incident on May 19, 2026, I am unable to trigger any deployment on one of my projects. Every attempt fails immediately with the toast error:
Failed to trigger deployment — "Problem processing request"
What fails (all of them):
"Deploy Latest Commit" from the dashboard
Automatic GitHub deploys on push/merge (no deployment is created at all)
"Redeploy" of the current ACTIVE deployment — i.e. redeploying the exact same image that already built and ran successfully also fails with the same error
The error appears instantly, before any build starts — no deployment record is created.
Details:
Project ID: 1ea2c293-3f7a-4da6-9945-a9feb080173f
Project name: acceptable-playfulness
Service: lusitanaboat-bot
Environment: production (de03f699-8193-468b-a7b0-6e70d7f6b21a)
Plan: Trial (credit and trial days remaining are fine — header shows "20 days / $4.48 left")
Timeline:
Deployments worked normally until ~08:54 UTC on May 20 (last successful deploy: merge of PR #131, builder Railpack, status SUCCESS).
Since then, every deploy trigger fails with "Problem processing request".
What I already tried (no effect):
Disconnected and reconnected the GitHub repo in the service settings (reconnect did not prompt for re-authorization).
Full dashboard refresh.
Logged out and back in / tried in a private window.
The current deployment is still live and serving traffic — the problem is purely that I cannot create or trigger new deployments. The platform status page shows "Fully Operational", so this seems specific to my project, likely residual from the May 19 GCP suspension incident.
Could you please clear/reset the deployment trigger for this project, or let me know what else I can do?
Thanks!
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. We've published a post-mortem if you'd like more information on the incident. It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you.
It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process.
You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY
If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c
Feel free to respond if your question has not been addressed.
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 • 28 days ago