49 Replies
2 years ago
62ccf963-e8af-4a94-a0aa-51864ea706c5
2 years ago
i swear its not physically possible for this app to use that much ram
2 years ago
Weird that it all spiked at the same time
2 years ago
Any logs for what happened at that time?
2 years ago
Give it a restart and let us know if it happens again
2 years ago
i restarted
2 years ago
??????

2 years ago
is it counting builder ram?
2 years ago
and why is my network spiking
2 years ago
all my fucking railway graphs are reporting different
2 years ago
things
2 years ago
I'm gonna go ahead and !t this
2 years ago
!t
2 years ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response adam • over 1 year ago
2 years ago
Sounds like this has been fairly flat for a while, have you made any code changes lately?
2 years ago
Or is this a new project
2 years ago
No and it’s rust
2 years ago
it's rust
elaborate please
2 years ago
this service usually uses anywhere between 9 and 15 megabytes of ram
2 years ago
4 gigabytes is news to me
2 years ago
still happening?
2 years ago
no

2 years ago
also i can't tell if im being charged for this shit or not
2 years ago
how long did it go on for
2 years ago
bruh what the hellll

2 years ago
maybe about a day
2 years ago
what did you do to stop it?
2 years ago
not sure
2 years ago
interesting
2 years ago
I just opened this thread, that looks similar (https://discord.com/channels/713503345364697088/1261606742605828127) Did you enable the new builder by chance?
2 years ago
i did
2 years ago
fwiw I did ask five if the metrics would report on the builder deployment for a given service and was told "should not" but now with two reports something is going wrong
2 years ago
said in jeremy's thread too, but will bring this to the team Monday
2 years ago
thanks G
2 years ago
!t
2 years ago
!t
2 years ago
Hey there Alex, the Railway team is running an investigation, this is estimated to take about a week, we will keep you in the loop.
Thanks,
Angelo
Status changed to Awaiting User Response Railway • over 1 year ago
2 years ago
Today I had a deploy failure email that I haven't investigated yet. When I logged into the dashboard I saw an unexpectedly high bill for said project

2 years ago
this is what I see in the deploy history

2 years ago
I never deployed via CLI
2 years ago

2 years ago
what the

2 years ago
oh that's the hoursly cron
2 years ago
This is not your thread, please create a new one
2 years ago
I was linked here by alex which is why I shared here
2 years ago
my bad adam
2 years ago
all good, if we’re seeing multiple reports of the same thing it’s usually better to make more threads so the team sees the multiple instances
2 years ago
🙏
2 years ago
A fix was merged for this, let me know if you experience these issues again!
Status changed to Closed brody • over 1 year ago