6b26e039-2715-4aea-8d46-efb8c7eada0c

also experienced this around end of June, which resulted to a huge payment as well (already paid)

the downtimes is me restarting the service, which results to me restarting it every day now or so, it seems to me that there is a memory leak happening, any ideas that can help me track it?

I think this question would better be asked in some kind of mongo forum or community as railway is simply running the stock MongoDB image and reporting on how much memory it's using

this is the MongoDB instance it's connecting on - which I don't have a problem with

I'm more concerned with the spikes happening on the API

oh my bad, your title mentioned mongo so i assumed these screenshots where for the mongo service.

is api service on the v2 runtime?

I'm not sure, how do I check if it's on v2?

in the service settings

ah yes

then there wouldnt be issues with memory reporting, thats simply what your app is using

hmmm could there be a chance that a user is hitting the API multiple times as a script?

it looks like a memory leak to me, so either an issue with your own code, or a 3rd party library you are using

any way I could possibly track this memory leak? sorry new to this

im sorry but this is not the level of support we could provide as it does not relate to railway, im sure there are many great tutorials on how to tackle this

alright, thanks for the help Brody

i wish you the best of luck!