Getting Error 503 first byte timeout
nevo-david
PROOP

3 months ago

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

Attachments

Solved

12 Replies

3 months ago

Hello, I am looking into this


notbnull
PRO

3 months ago

been having the same issue for the last 6 hours


3 months ago

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


3 months ago

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.


nevo-david
PROOP

3 months ago

now it's working


gazhay
PRO

3 months ago

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

3 months ago

1772621380_fOi2X8ybip.png

Attachments


justsl
PRO

3 months ago


3 months ago

railway.com affected

1772621498_6MkmqkYNaw.png

Attachments


yuvalreg
PRO

3 months ago

Also had this issue. It seems to be resolved for now.


yakuo
PRO

3 months ago

The problem occurred again and has been resolved.


3 months ago

Can you open another thread for that, it is a different error.


Status changed to Solved brody 3 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...