3 months ago
Our uptime monitors recently (last 5 minutes) hit a 503 error with the following message.
```
Error 503 Backend.max_conn reached
Backend.max_conn reached
Error 54113
Details: cache-sin-wsssXXX
Varnish cache server
```
Ive seen some discussions in the forums around this topic but with no clear resolution. Is railway experiencing any issues? Does anyone know if this error comes from Railway? And if so under what circumstances might we expect this? If this is not from railway Im going to investigate further up the chain, just wanted to check in here
We also experienced this late last week on a different service for just a minute or 2.
9 Replies
3 months ago
Experienced the same issue, lasted around 10 minutes
3 months ago
Same issue here. I have yet to receive an update from the team.
3 months ago
This is a known issue on our side - the 503 "Backend.max_conn reached" error originates from our edge/CDN layer, not from your application. Our engineering team is actively investigating. We don't have an ETA yet, but we're tracking it.
Status changed to Awaiting User Response Railway • 3 months ago
sam-a
This is a known issue on our side - the 503 "Backend.max_conn reached" error originates from our edge/CDN layer, not from your application. Our engineering team is actively investigating. We don't have an ETA yet, but we're tracking it.
3 months ago
Would be really nice if known issues being investigated were posted to the status page. We've been getting a "503 first byte timeout" error from Varnish for a few hours, trying to figure out which provider that was related to.
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
That's fair feedback, and we appreciate you raising it. We'll pass this along to the team internally. We are actively working on overhauling our status page to provide more granular insights.
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
just got the same exact issue right now, it lasted 10 minutes also. I redeployed and it seemed to have solved the issue.
It goes without saying that a fix is much needed for this if indeed it stems from Railway's edge/CDN layer
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
Yes - we understand and are working with Fastly to ensure we do not have this problem going forward.
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
Thanks Sam, I appreciate the response and am happy to know it’s a priority. As you work to resolve this please let us know if there are any configuration changes on our end that could reduce the occurrence of this issue. Ie replicas, redeploys, etc.
Looking forward to updates here.
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
Will do. Thanks for your understanding.
Status changed to Awaiting User Response Railway • 3 months ago
Status changed to Solved jake • 2 months ago