AWS Billing Bug Shows Trillion-Dollar Estimates, Causes Developer Panic

This morning, thousands of AWS users received billing alerts showing estimated charges ranging from millions to over a trillion dollars. One user reported a $1.7 billion estimate on an account that normally runs under $5 per month. Another saw $627 billion. The record appears to be $1.22 trillion.

The cause was a unit conversion bug in AWS's S3 billing calculations - the system was apparently confusing bytes with gigabytes, creating an off-by-2^30 error in estimated costs.

What Happened#

Starting around 9:42 AM UTC on July 17, 2026, AWS users began receiving budget alerts with astronomically inflated cost estimates. The issue affected S3 storage billing calculations, multiplying actual costs by approximately one billion.

A user on Hacker News described the scale:

"I've got an estimated bill for $1.7 BILLION over this month. Normal usage is less than $5."

AWS acknowledged the issue on their health status page, classifying it as "Inaccurate Estimated Billing Data" affecting S3 services.

The technical explanation appears straightforward: storage amounts measured in gigabytes were being calculated as if they were bytes, creating a 2^30 multiplier on all S3 cost estimates.

The Human Impact#

Beyond the technical bug, the incident revealed how much developers rely on AWS billing alerts as an early warning system - and how terrifying it is when that system fails spectacularly.

Comments from the HN thread paint a picture of genuine panic:

"I was actually in the toilet when I got an email I owe them $36,869,876,146.51. I literally just shit myself."

"Probably the closest I've ever been to getting a heart attack. Normally less than $1 per month, and now suddenly $284,006,266,443.74. Whatever the bug is on their end, this is unforgivable."

"I got one for 8 billion while I was eating lunch. Thankfully I managed to not vomit."

"I got a budget alert that I owe $286,486,223.88 on a hobby AWS account, almost got a heart attack."

Several users noted they immediately started deleting infrastructure, fearing a security breach:

"I got an email with a bill of $233 million and an estimated $433 million until the end of the month. I panicked and nuked my entire setup - I really wonder how many people did the same."

What HN Is Saying#

The Hacker News discussion accumulated over 600 comments and 900+ points within hours. The conversation split between dark humor about the numbers and serious concerns about AWS's quality assurance.

On the absurdity of the numbers:

"I got 109 billion - am I the winner?"

"Sorry mate, $241,946,798,744.75 for Glacier here."

"Mine is showing $627,487,837,871.49. I might be a winner."

"It's ok, I owe them 1.22 trillion."

On the QA failure:

"I'm shocked it wasn't caught by tests, alerts about unusual changes in the billing system, or even accounting. Like surely the P&L reports look all kinds of wrong right now, they have to be showing like 6M% profit margins and revenue measured in quadrillions."

"Either way it shows their QA and testing procedures are incompetent. It's just not acceptable for a utility like AWS to move fast and break shit."

"I'm also a little surprised this didn't trip a circuit breaker. For something as non-real-time as billing, I'm surprised they don't have an automated kill switch that pauses the billing system and fires a page if variance in bills spikes."

Some commenters speculated about AI-generated code causing the bug:

"AI slop. Or just a distracted dev."

"Vibecoded the billing system, raised revenue 9000%. Great for that promo package."

Others pushed back on blaming AI specifically, noting that unit conversion bugs predate language models by decades.

The Broader Problem with Cloud Billing#

This incident highlights a persistent fear among cloud users: the possibility of catastrophic surprise bills. Even though this bug was obviously wrong - no one believes they actually owe trillions - it exposed how little control users have when billing systems malfunction.

One commenter raised a hypothetical:

"Makes you wonder - what if there really would be an incident where some massive amount of traffic got routed to your infrastructure by some heavyweight player? Say Wikipedia accidentally switches their IP to your CloudFront? Would you really be on the hook for $500k?"

Another noted the emotional damage even for obviously incorrect bills:

"This is embarrassing for Amazon, but I'd take laughably wrong over subtly wrong any day. If the bug made bills 20% higher I probably wouldn't have queried it."

The health implications were raised multiple times:

"This is real risk. Someone could really have a serious health problem."

"I wonder how many people died of heart attack when they saw this."

AWS Response Timeline#

1. 09:42 UTC - First reports of inflated billing appear on HN and Reddit
2. ~10:00 UTC - AWS Health Status page acknowledges "Inaccurate Estimated Billing Data"
3. ~13:00 UTC - Users report estimates returning to normal values
4. 14:00+ UTC - Estimates largely corrected, though some users still saw inflated numbers

AWS has not released a detailed postmortem as of this writing. Given the scale of the incident - affecting what appears to be all S3 users globally - a root cause analysis would be valuable.

What You Can Do#

While this particular incident is resolved, it highlights the importance of billing safeguards:

Set up budget alerts with multiple thresholds. Having alerts at 50%, 80%, and 100% of expected costs gives you earlier warning of anomalies.

Enable AWS Cost Anomaly Detection. This ML-based service identifies unusual spending patterns and can catch both real overages and billing bugs.

Consider AWS Organizations billing policies. Service Control Policies (SCPs) can prevent certain high-cost actions even if credentials are compromised.

Keep billing contacts current. AWS sends billing alerts to the account email - make sure someone is actually monitoring it.

Have a response plan. Know who to contact and what to do if you receive an unexpected bill. AWS Support can help, but response time varies by support tier.

The Takeaway#

The bug itself was simple - a unit conversion error. But the impact revealed how much anxiety exists around cloud billing, and how a single software bug can cause genuine physiological stress to thousands of developers simultaneously.

AWS will fix the bug and move on. But the incident should prompt reflection on whether billing systems for critical infrastructure should have more circuit breakers, more sanity checks, and more human review before sending alerts that can cause panic.

As one commenter put it:

"They should pass a law saying they should have to pay you the amount over the correct bill as compensation; I bet they'll stop making mistakes like this pretty quickly after that."

That's probably not happening. But better testing might.

Sources#

• HN Discussion
• AWS Health Status
• Reddit r/aws thread