Sharp cost estimation spike (400$ estimate from 4$)
Hi, i'm kinda scared.
Is this due to recent changes in pricing?
Could you help me find out what's happening?
66 Replies
Project ID:
7e603fcd-3ad0-4cf7-8c8c-2492422747af7e603fcd-3ad0-4cf7-8c8c-2492422747af
I don't see same order of magnitude spikes in resource consumption, so I'm kinda worried maybe there is something bag happening that is not shown in metrics?
all of mine look like this
i wonder if there's a display bug
one of my apps use about 100MB of memory and cost this much so yours should be 10x that since you're using 1GB so i think the $400 is a bug
your're also using a bit of CPU but not $400 worth π
I've had this today. I had an estimated bill of $10,000.
curious what plan you guys are all on?
It did seem to level itself out and it was (from what I see) because of an issue on my side but I also have a feeling that railway are having either issues with a display bug on pricing or an infrastructure issue.
Im on the Developer Plan
IMO there is no way I am using $156 of usage. But this thing changes like the weather in the UK. I am on the developer, too.
so yeah there's definitely something going on
@ImLunaHey You're probably not being an idiot like me and deploying development mode react apps in production, though π π π
its a spread of random stuff
discohub sounds fun π OP, I don't think you're alone on this. What does your breakdown look like for per-service?
@because_the_internet
See... π
though i do wonder since they said we'll now need to pay for egress π€
im probably way off on that but its the only thing that i can think of that could possibly explain it other than a visual bug
https://blog.railway.app/p/pricing-and-plans-migration-guide-2023#charging-for-network-egress
"From August 1 2023"
yeah just wonder if somehow they broke the display while doing something with that.
Yeah, this isn't the first thread today regarding uptick in pricing.
My guess is they may have messed up on the window that calculates the estimated bill and that it's using a much tighter window now.
When I deploy, it goes crazy up, but once things settle it seems to be OK.
Usage over the past 5 minutes X an entire month? Chaos.
My estimated bill is now $93.03.
oh...
i havent done a deploy
that might be it
I'll try one now π
doing it
hmm mine still seems the same
okay there's something up lol
I'm like 99% certain it's to do with windows
metrics on any of the services look crazy?
If you take a sample of 5 minutes of usage and multiply it by the month, like I said above, you get scary numbers
Also why TF does it cost me 5 cents to deploy a react app π€
5 replicas of a rust site lol
This was caused by me running react in development mode on production but I feel like there's something off here
What's the lag on their metrics? It looks like I can't see less than 3 hours ago
you talking about this?
Nvm!
Seems like you have to click individual services to see a proper view
ah
(Notice frantic commits trying to fix the problem π )
But back to the point: The prices do seem REALLY messed up at the moment. I've had relatively low pricing up until today where it seems to just spike like crazy. I wonder if there's a billing chart where I can see billing-based usage over time. That would be interesting.
Flagging this thread. A team member will be with you shortly.
Woo I got hit too
So I guess there will be changes in pricing? We're getting 5$/month + x10 vCPU/RAM/GB price? π¦
the crazy high prices you're seeing arent correct.
I do wonder about the pricing. Does it really sound right to have $7 worth of costs for running a 1-2GB RAM for the same amount of days? a1.medium costs around 0.02/hr for a 2GB system which would equate to 3.36. It does seem weird considering the costs I had for last month were about $13 in total and we haven't scaled at all in that time. The estimated is definitely a bug but has that had an impact on pricing, too? Odd.
Back to numbers!
okay it's 100% going up per deploy this is funny now
π (haha_I_live_here.jgp)
What are u going to do in this case? can the team charge you less or something?
It happened to me once. It was node-cron when you use timezone in the node-cron function. But the charge was not that big
read through, this isnt an actual issue. it's a visual bug.
@ImLunaHey idk I was being charged $1 an hour this morning for a service that should cost a few cents. I'm guessing there's a combination of visual issue and some overcharging...
I think there's something fishy going on with RAM usage calculation. Kinda dissappointed tbh
JSYK, these look like visual bugs from our side and weβre gonna have a look into it Monday
For the devs looking into this, it seems to be mainly causes by a weird calcuation that's done on deploy. after a deploy settles down the price goes back to what it use to be.
Nice, thank you! Also, while I think there might be a visual bug with estimated price, I still think that I'm currently charged significantly more every hour, even though my usage hasn't changed. I actually decreased my RAM consumption 2-3 fold but hourly pay is still more than before
I'm experiencing the same issue. 8 usd, no change in usage and now estimation us fluctuating up to $300
yes, nothing anyone can do until the devs resolve it. it is simply a display issue.
Im also noticing everytime i do a deploy my mb/minutes go up by like 100 and i was not understanding why the second one was more expensive than the first one since both are the same api just ones hosts the frontend and the other one is just the api, on the first one i let nickpaxs do the build and the container on the second one i created a docker file so i can render the front end from the same server. should not be that much difference in ram but one uses like 4000 and the other like 120 and the 150mb one seems to be more expensive than the other one. why is it that every deploy consumes around 100 minutely GB per deploy
I know its being fixed but wowee is this spooky to see after one staging + prod deploy π« :
FYI I think they may be making changes? My current cost just got halved and my estimates are normal lol
Weβve indeed rolled out a change :). Should take effect on a rolling basis over the next 12h
is the new estimate meant to include egress to?
I noticed my estimates are still higher than they were before the issues. Not by much, but still noticable. I was also wondering if egress is included now. I would have assumed it would be included once the new plan is added. A basic astro site that estimated around 30 cents or less before now estimates over a dollar?
egress/ingress isn't included yet