2 months ago
Hey,
There seem to be a technical issue on a database in my project (99ebe7e0-21fa-4461-864a-1326eea25273?) that caused the DB to get stuck in memory usage of 4GB through the month, and when that went down the disk storage spiked to max.
I don't know what happened but that caused my last bill to be much higher than usual.
2 Replies
2 months ago
Your July invoice was $37.64, with memory accounting for $41.33 of raw usage, up from $14.50 the prior month. This is consistent with a database stuck at high memory consumption as you described. Railway bills for resources actually consumed, so we're unable to adjust charges for usage that was delivered to your services, even when caused by an application-level issue like a database getting stuck.
To prevent this going forward, you can set up usage alerts, limits, and view your per-service cost breakdown at railway.com/workspace/usage.
Status changed to Awaiting User Response Railway • about 2 months ago
Railway
Your July invoice was $37.64, with memory accounting for $41.33 of raw usage, up from $14.50 the prior month. This is consistent with a database stuck at high memory consumption as you described. Railway bills for resources actually consumed, so we're unable to adjust charges for usage that was delivered to your services, even when caused by an application-level issue like a database getting stuck. To prevent this going forward, you can set up [usage alerts](https://docs.railway.com/reference/usage-limits#custom-email-alert), [limits](https://docs.railway.com/reference/usage-limits#hard-limit), and view your per-service cost breakdown at [railway.com/workspace/usage](https://railway.com/workspace/usage).
a month ago
Can I get technical support to understand what happened?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • about 1 month ago