12 days ago
Today for a 30 minutes time window some of my deployments starts responding with:
Error 503 Connection reset by peer Connection reset by peer Error 54113 Details: cache-gru-sbsp2090070-GRU 1772397555 2083755660 Varnish cache server
Nothing was changed in code/deployment settings, but for a time windows of 30 minutes my apps starting acting like that.
Anyone have the same issue?
11 Replies
12 days ago
I faced the same issue a few minutes ago. I noticed that even Railway forum (station) and dashboard was experiencing the same 503 error.
12 days ago
Also saw the same thing
12 days ago
Yes all of Railway was down for five minutes. There needs to be some mention of this; it was not just Asia.
12 days ago
I pinged them on Twitter because I couldn't even report the issue through regular channels. (We're in North America)
12 days ago
Right, station was down, all of RW. This is the third or fourth full-stop outage in the past two weeks, and it belongs on the status page and with some RCA.
12 days ago
Yes I also experienced this earlier this evening - I would much rather the pace of rolling out new features was reduced in favour of platform stability. In my view there is nothing more important.
johndavi
Right, station was down, all of RW. This is the third or fourth full-stop outage in the past two weeks, and it belongs on the status page and with some RCA.
12 days ago
yeah this is the final straw for us unfortunately. Great product, just not reliable
12 days ago
Apologies, we had an incident affecting requests across multiple regions, which is now resolved. Our dashboard and forum were also briefly impacted. Details: https://status.railway.com/incident/cmm87wjsl01d9g5utfc7kmomf - if you're still seeing 503s, please let us know.
Status changed to Awaiting User Response Railway • 12 days ago
12 days ago
thanks, but this needs to be clarified as it was not only asia as you note above (and we experienced)
Status changed to Awaiting Railway Response Railway • 12 days ago
11 days ago
Sorry for the miscommunication here - we've updated the incident at https://status.railway.com/cmm87wjsl01d9g5utfc7kmomf to reflect the actual impact
We only saw impact in Asia before the other regions were hit, and we should have updated that when we confirmed impact across regions
Status changed to Awaiting User Response Railway • 11 days ago
4 days 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 • 4 days ago


