a month ago
My primary and worker services stopped working yesterday and do not rebuild since. they worked just fine until then. I'm a pro subscriber. can you please help me resolve it? it's really affecting my production systems.
7 Replies
a month ago
We can see that your Primary and Worker services in the "Yelp API (New)" project are currently stuck in a deploying state. This is related to a known platform-wide disruption that we are actively working to resolve. Your services should recover once the issue is fully mitigated, and no action is needed on your end.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
We can see that your Primary and Worker services in the "Yelp API (New)" project are currently stuck in a deploying state. This is related to a known platform-wide disruption that we are actively working to resolve. Your services should recover once the issue is fully mitigated, and no action is needed on your end.
a month ago
the services are not just "stuck" in deployment. 2 of them keep failing...
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We confirmed that both your Primary and Worker services are crashing (not just stuck), repeatedly exiting because they cannot reach your Redis service - the connection times out after 10 seconds on each attempt. Your Redis service does show as deployed, so this is consistent with the ongoing platform-wide disruption that is affecting internal networking between services. We are actively working to resolve this, and your services should recover once mitigation is complete.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
We confirmed that both your Primary and Worker services are crashing (not just stuck), repeatedly exiting because they cannot reach your Redis service - the connection times out after 10 seconds on each attempt. Your Redis service does show as deployed, so this is consistent with the ongoing platform-wide disruption that is affecting internal networking between services. We are actively working to resolve this, and your services should recover once mitigation is complete.
a month ago
whats the timeline for this?
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
sam-a
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](https://blog.railway.com/p/incident-report-may-19-2026-gcp-account-outage). 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.
a month ago
Your status page says things are back to normal but my builds are still failing
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We went ahead and redeployed your services for you - they should be coming back online now. Apologies for the impact from this disruption. If you notice any other services still having issues, redeploying the affected service (not restarting) will fix them. Let us know if anything else comes up.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved mykal • about 1 month ago