3 months ago
How could it be possible that I would reach $124.57 at the end of the month for a service which has so far consumed $4.05, essentially in MEMORY costs while another service, also essentially based on memory costs, is estimated at $67.39 by the end of February for $15.91 so far (this is my most expensive service on a monthly basis).
Please fix this estimate bug ASAP.
Thanks
22 Replies
I also see that a service which last month had
42979.01 minutes = 23.1 hours per day now would account for 16881.48 minutes in memory in 3 days for the same DB with exactly the same Mb, under 1GB.
Which does not make any sense.
See the Memory trend on the DB and WEB APP for January until Today, no increase. So why do I get almost 4x the billing per day for the first 3 days of the month of February????
Current billing period so far = 12.5 days.
if current cost = $4.05 ÷ 12.5 = 0.324 × 30 = $9.72, not $124.57.
For the other service above.
Current cost = $3.11
30-day projection:
$3.11 ÷ 12.5 × 30 = $7.46, not 49.28 etc
Current cost = $2.43
30-day projection:
$2.43 ÷ 12.5 × 30 = $5.83, not $29.95
What happened to your computation logic? @Brody ?
3 months ago
#🛂｜readme #5
So since there is no immediate reaction, I felt compelled to ping you since we spoke in the past.
Some estimates decreased but still far off.
Can you fix it completely and confirm all billing for the first 12.5 days of the period is correct.
3 months ago
I also notice it. Haven't deployed anything new and have stable usage with no visible changes, but current usage and estimates I see is 2x and more than it should be (I had very stable cost per month for the last ~3 months).
3 months ago
yeah I'm on a free trial and my 5$ ran out when I didn't have any services running except a db, went from consuming a few cents/hour to $5 in a few hours lol
3 months ago
Railway had an incident yesterday and one today affecting parts of the metrics pipeline (check https://status.railway.com/)
The “Estimated cost” is derived from those metrics, so while
metrics are degraded it can show incorrect spikes/dips (and may change again as data
backfills once the pipeline is healthy).
https://station.railway.com/questions/there-is-a-scary-bug-in-cost-estimates-f-25fa34ae#tmjk Was anyone misbilled as a result of this?
3 months ago
No, you’re billed for your actual resource usage, not the estimate.
Status changed to Solved medim • 3 months ago