#Getting Error 503 first byte timeout

14 messages · Page 1 of 1 (latest)

mortal stream
#

Hello, I have an endpoint that takes around 2-10min to load, but I a getting error, screenshot attached.
Worked up until last day, I know that Railway timeout is 15min.
It's a private endpoint that gives me some metrics from Stripe, I can't share it publicly (this is not a private convo).

CleanShot_2026-03-04_at_10.18.49.png
pastel ledgeBOT
verbal sun
#

Hello, I am looking into this

fallow mist
#

been having the same issue for the last 6 hours

verbal sun
#

I've just pushed an update which may fix this - please let me know if you're seeing resolution here.

#

For context, this error happened if you hit an edge CDN POP which isn't close to a Railway datacenter - in this case, the request was sent over the backbone to the origin POP with a lower request timeout than usual.

This change in behavior is due to a recent update we made which causes requests to traverse keepalived connections to origin POPs over the backbone rather than creating individual connections from each edge POP.

mortal stream
#

now it's working

wooden shuttle
#

I also have been getting these and now also

Error 503 Backend.max_conn reached
Backend.max_conn reached

Error 54113
Details: cache-ams21038-AMS 1772621384 4069467462
jolly wedge
pastel ledgeBOT
#

New reply sent from Central Station thread:

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd
">
<html>
<head>
<title>503 Backend.max_conn reached</title>
</head>
<body>
<h1>Error 503 Backend.max_conn reached</h1>
<p>Backend.max_conn reached</p>
<h3>Error 54113</h3>
<p>Details: cache-ams2100090-AMS 1772621452 1757083269</p>
<hr>
<p>Varnish cache server</p>
</body>
</html>

You're seeing this because this thread has been automatically linked to the Central Station thread.

jolly wedge
pastel ledgeBOT
white briar