Pricing not coherent
Hello guys, hope you are fine. I looked at the usage/pricing page as changes were applied recently.
Tbh, most of the numbers do not match (expected, current, etc). I usually have a bill of 20 (team) + 20, around 40. Here, not sure what the month gonna be :/
26 Replies
Project ID:
7fc7bc42-6e0c-449e-92b2-6706b93a0592
7fc7bc42-6e0c-449e-92b2-6706b93a0592
your screenshot says 45.53$ that's not too far off from your expected price?
Especially since it looks like you have had a gradual increase in ram and cpu usage on that one project. Your estimation includes both projects, not just the one
The estimated cost being lower than the current cost is odd
There are some bugs going around regarding pricing. The team will get to it on Monday
Flagging this thread. A team member will be with you shortly.
Hello, Yes, I did not highlight the problematic numbers, thank you @Adam for spotting it 🙂 thanks also Brody and Vin of course 🙂
Being at 34 dollar the 5th of august while being charge 40 for a month was my first reaction btw
Adam has better eyes than us old folk
Unknown User•16mo ago
Message Not Public
Sign In & Join Server To View
@Angelo
bad
Unknown User•16mo ago
Message Not Public
Sign In & Join Server To View
agree ;-;
Gotcha, the math still doesn’t add up aside from that
31$ + 20 ≠estimated 45
very bad math
Thank you for the follow up, indeed, quick (too quick) math it seems 😄
Hey @nightmarebegood,
This seems to just be a visual bug on that page due to using the incorrect billing period (feb to sep). Your actual usage for this month is much lower (~$5). We will give another update once this bug is fixed
Can you also please confirm if this is still and issue
Mmmh, I still see some incoherence
The estimated bill and actual bill are not matching the details
Still the issue I highlighted earlier that didn’t get picked up on. Team plan costs aren’t added to the estimated cost or current. Just usage
and the same estimated < current issue
@jr tagging in here
I will take a look tomorrow. It seems like the billing period (feb to sep) is still incorrect for you. Just want to reassure that we are not charging for this and it is still a frontend thing.
Hey there, we've found the issue regarding this visual bug and a fix will be out soon
Perfect, Thanks. Indeed, I just saw the period today (from feb 03 to sep 01), strange
Can you please send a screenshot
@nightmarebegood ^
here it is 🙂
Just did a hard refresh (u know ctrl alt r)
seems better at least, dates are ok
estimated also (seat 20 + usage 28)