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.

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.

the site has been down all day -- this was the demo day with my board and I am really frustrated that the site is still down over health checks and countless attempts to fix it.

We completely understand your frustration, especially with the timing of your board demo. Your Postgres and api-server are both showing as running successfully now. The api-server's most recent deployment came up cleanly - migrations passed and the server is listening. Could you confirm the site is accessible on your end?

The direct Railway API keeps returning 502. It is not fixed.

having the same issue, and I'm up against a deadline as well. It's so frustrating. Hang in there.

I'm a novice, so it makes me feel a little better to know I'm not alone, but it also makes me more frustrated that you and others are dealing with this and the endless workarounds to get sites up and running. Hopefully, today is a better day!