Two services "froze" and stopped responding to requests – fixed after redeploy?
efstajas
PROOP

3 months ago

Very strange thing just happened; two of our services (which are not inter-dependent at all) suddenly appeared down on monitoring (timeout), which hits health endpoint over private networking.

Attempting to connect to the services via public networking failed with 502 after a while.

Looking at the deploy logs of the affected services, they didn't log anything at all since around 12:10 CET — despite being quite chatty usually. No errors were visible, it's like they suddenly froze up.

After redeploying the services, they came back to life immediately.

Any idea what happened? Don't think this was caused by anything on our end

$20 Bounty

2 Replies

fra
HOBBYTop 5% Contributor

3 months ago

were the metrics fine at that time? memory/cpu all good?


efstajas
PROOP

3 months ago

Yeah memory / cpu were all good. I saw in retrospect that we received this email right around the time the services went down, but only for 1/2. very weird. :/

Screenshot_2026-03-06_at_15.53.53.png

Attachments


Welcome!

Sign in to your Railway account to join the conversation.

Loading...