Hello,

I'm sorry but we have no way of telling you why your application used however much memory it has, we are simply running your app and reporting on how much memory it uses. Similarly to how your power company can tell you how much power you used, but they have no way of knowing why you used the power>

This is not an issue on our side, and thus there is nothing for us to fix here.

Best,
Brody

I found the issue, the staging environment is what took up all the extra RAM. I've attached an image of the increase. The staging branch has been completely unchanged and unused since October, with no commits or anything.

I tried opening the staging URL when I noticed this, and it didn't show me a webpage, just an error. After redeploying the staging environment (again with no changes), the webpage opens up and RAM usage has gone back down to normal levels, as you can see in the attached screenshot.

I am almost certain that this is an issue on your side. I'm not an expert, but it seems to me that something happened on November 28th with your internal system that caused all this. Please look into it, I'm very frustrated with this.

This is not an issue with our platform or internal systems, your app simply started using more memory.

Again, we have no observability in what your code does, so we only report on how much memory it uses and have no way to tell you why your app used the memory that it has.

Again, my staging app has remained been completely untouched for over 2 months.

You have observability on what your hosting infrastructure does, and can look into the logs and events of November 28th on the infrastructure that my app is running on to see what went wrong.

If this is not a priority to you or your team, I'm unfortunately going to have to find a new platform, because I can't have this kind of expense happen again.

The app remaining untouched isn't really applicable here, it was running and started to use more memory, as to why, we have no way of saying.

Yes we have observability into the host that runs your application, but that still does not tell us why your app used the memory it has, and nothing we would have done would effect how much memory your code uses.

Furthermore, you are the only report we have seen of this, cemeting the fact this was solely your application that used the memory shown.

We are sad to see you go, but please keep in mind that without setting fixed resource limits your app using the memory available to it is not behaviour limited to the Railway platform.