Re:Incident with GitHub Actions and Codespaces
by yed on Thursday April 14, 2022 @02:08AM
(#31023865)
To put these billing errors in context, our account suddenly showed ~$12,000,000 in usage fees. I saw some others posting bills high as 100s of millions. Pretty heart attack inducing.
[ Parent
| on HN ]
Re:Incident with GitHub Actions and Codespaces
by dx034 on Thursday April 14, 2022 @02:43AM
(#31024024)
That these were so scary shows the downside of usage-based fees. If you run on dedicated hardware, you always know what you'll have to pay, no matter how you utilize the system.
The risk of surprise bills, even with the advantage of higher scalability, is one of the major factors to put me off many cloud services. I wouldn't want to run a business where you always have the risk of some bug or unforeseen behavior destroying your budget.
Re:Incident with GitHub Actions and Codespaces
by bencollier49 on Thursday April 14, 2022 @04:17AM
(#31024466)
I've said this over and over again. There should be laws in place enabling a person or company to set a hard limit on spend.
It would be a pro-innovation law because people would then have the confidence to innovate.
Re:Incident with GitHub Actions and Codespaces
by OJFord on Thursday April 14, 2022 @06:11AM
(#31024996)
I also think it'd be good for companies. If you usually pay (say, numbers don't matter, except that AWS or whoever doesn't care until they get bigger I suppose) 1k-3k and set a 'don't surprise me too much' limit of 5k, then when something unexpected happens, instead of having a bad time pleading with them to let you off 12k or whatever and feeling cautious about using it again perhaps with some sour taste even if they do let you off, you think 'woah, glad I have the limit', and pretty much get on with your day; AWS or whoever gets an unexpected 2-4k instead of writing off 9-11k, and keeps the happy customer (at the customer's expense instead of its own).
Re:Incident with GitHub Actions and Codespaces
by bencollier49 on Thursday April 14, 2022 @03:48PM
(#31032370)
I agree, unless... It could be that they're making most of their money from spikes. It would be interesting if that were the case.
Re:Incident with GitHub Actions and Codespaces
by OJFord on Thursday April 14, 2022 @07:38PM
(#31034896)
I don't think so, surely most comes from far bigger fish than the type to have (not have time/resources to avoid) spikes and care about them.
Re:Incident with GitHub Actions and Codespaces
by Dave3of5 on Thursday April 14, 2022 @04:59AM
(#31024667)
I agree cloud providers shouldn't be able to bankrupt their users due to high usage. IMO it should be mandatory to set a limit it makes sense from a finance side.
In my case my cards don't have $12 million of a limit so they could not actually charge me that amount of money. It makes sense if you use invoice type billing i.e. like a company but as an individual these insane bills can't actually run.
Re:Incident with GitHub Actions and Codespaces
by blibble on Thursday April 14, 2022 @05:36AM
(#31024835)
they wouldn't be able to charge your CC but this isn't really relevant to what you owe them
they can still attempt to come after you for that $12 million
Re:Incident with GitHub Actions and Codespaces
by Dave3of5 on Wednesday April 20, 2022 @04:54AM
(#31094317)
Of course but I cannot ever pay that amount so what would be the point from their side. It would be more sensible to stop after they run out of money on my CC.
Re:Incident with GitHub Actions and Codespaces
by sascha_sl on Thursday April 14, 2022 @05:36AM
(#31024830)
These emails we got were about billing limit (which is meant to be a hard limit on github) being hit too. Either the bug ignored such limits (ours was in the low thousands) or it created charges so fast that the limit couldn't apply anymore.
Re:Incident with GitHub Actions and Codespaces
by xrd on Thursday April 14, 2022 @02:40AM
(#31024008)
You didn't read the blog post from GitHub saying they were switching to Zimbabwean dollars because the dollar is falling out of favor as the reserve currency?
Re:Incident with GitHub Actions and Codespaces
by jotm on Thursday April 14, 2022 @04:46AM
(#31024613)
Damn.
Well, when you owe $10,000 it's your problem, when you owe $10,000,000 it's their problem :D
Re:Incident with GitHub Actions and Codespaces
by prepend on Thursday April 14, 2022 @07:25AM
(#31025437)
I think this code wasn’t supposed to go into effect until Microsoft moves beyond their friendly stage and moves into maximum revenue extract stage.
Re:Incident with GitHub Actions and Codespaces
by karussell on Thursday April 14, 2022 @02:15AM
(#31023903)
yeah, better than coffee ;) ... we had $78,610,108
Re:Incident with GitHub Actions and Codespaces
by fishnchips on Thursday April 14, 2022 @03:27AM
(#31024245)
Our account is still showing $188,536,934.07 overage.