ae620a01-d3a8-4dca-a2b5-93af7c8cd912

What are you running? What is this service doing?
I don't think Railway is at fault here, what are the last logs before crashing?

omg

please send metrics for your service, is it topping out?

@Adam memory looks fine

I think those dips are when app crashes in memory?

Hm yeah, potentially. It's very unlikely Railway is at fault here, have you tried running your API locally for this long to ensure it doesn't crash?

yeah

but then again running api locally doesnt have traffic so

Sure, that's fair. Unfortunately there's not a whole lot to go on here, but it's likely a code issue. More logging would be helpful to diagnose this

brutal

If it's a nodejs app you can try using the NODE_OPTIONS=--max-old-space-size=32768 env var, it sets it to 32gb

But that won't remove the memory leak though, it will only give your app more mem to use before crashing

real

!s