{
  "type": "article",
  "title": "How a Customer's Two-Cent Cloud Bill Ballooned to $1.5 Billion Overnight",
  "summary": "Amazon Web Services customers woke up to estimated bills running into the billions and even trillions of dollars after a pricing bug hit its billing system. The company says the charges are bogus and no one has to pay.",
  "content": "Waking up to a routine cloud invoice is one thing. Waking up to an email saying you owe more than $1.5 billion is quite another. That is exactly what happened to Bill Radjewski, the person behind CollegeFootballData.com, who opened his inbox to an alarming alert from Amazon Web Services and learned that his usage fees had somehow crossed the billion-dollar mark, with his August 1 statement projected to climb past $3 billion.\n\nThe figures were absurd on their face. Radjewski has held the account for more than six years, and by his own account his monthly charges have never once topped two cents. He backed that up with screenshots of his three most recent monthly invoices, each of which came to a grand total of $0.01. \"I've had this account for 6+ years and in that time my monthly spend has never exceeded $0.02,\" he said.\n\nHe was far from the only one\nReplies flooding the AWS Support account on X made it clear the problem was widespread. Other customers were staring at equally ridiculous quotes: $22 billion for one, $75 billion for another, $110 billion for someone else. The mood online swung between panic and dark humor. \"Blud why did you hit me with a cost of 5 million USD what did I even do,\" one rattled user wrote.\n\nWhat Amazon says went wrong\nAmazon spokesperson Aisha Johnson pointed to the AWS Service Health Dashboard for details. The company did not put a figure on how many accounts were hit, but the dashboard flagged the problem as \"global.\" According to that same dashboard, the billing console \"began displaying incorrect estimated billing data\" on Thursday, July 16, at 10:38 pm EDT.\n\nEngineers started digging in roughly six hours later. They traced the root cause to \"an issue with unit pricing within the estimated billing computation subsystem,\" though no further detail was offered about what actually broke. In later updates, the company said it was \"rolling back a recent change to the billing computation subsystem,\" trying to restore its \"last known good estimated bill computation,\" and that it had \"paused estimated billing computations\" in the meantime.\n\nNo need to panic, or pay\nAmazon expects everything to be sorted out by the weekend and stressed that \"there are no customer actions required at this time.\" In other words, nobody is actually on the hook for these cartoonish sums. Some customers chose to lean into the absurdity instead. One Reddit poster shared a \"cost and usage overview\" in the AWS subreddit showing $7.1 trillion in service fees run up since July 1, a figure more than double Amazon's entire market value.\n\nWhat this means for you\n• For AWS customers: The billion and trillion-dollar figures are a system error, so you owe nothing extra and need to take no action; correct billing should return by the weekend.\n• For businesses on the cloud: It is a reminder to double-check billing alerts before reacting, since even a two-cent account briefly showed a multi-billion-dollar balance.\n\nQuestions & Answers\n\n1. What went wrong with AWS billing?\nThe company traced the root cause to an issue with unit pricing within the estimated billing computation subsystem. The billing console began showing incorrect estimated billing data from Thursday, July 16, at 10:38 pm EDT.\n\n2. Do affected customers have to pay these huge bills?\nNo. The company stressed there are no customer actions required at this time, and the charges are erroneous.\n\n3. How big were the erroneous bills?\nSome accounts showed up to $1.5 billion, while others saw quotes of $22 billion, $75 billion and $110 billion. One Reddit user's account displayed $7.1 trillion.\n\n4. When will the issue be fixed?\nAmazon expects the problem to be resolved by the weekend.\n\n5. Who is Bill Radjewski?\nHe runs CollegeFootballData.com and has held his AWS account for more than six years, with monthly spend that never topped $0.02, yet he was billed more than $1.5 billion.\n\n6. How is Amazon fixing it?\nThe company is rolling back a recent change to the billing computation subsystem, reverting to its last known good estimated bill computation, and has paused estimated billing computations for now.",
  "url": "https://trendkia.com/en/technology/eka-grahaka-ka-do-senta-vala-klauda-bila-ratonrata-1-5-araba-dolara-kaise-bana-gaya-8413",
  "category": "Technology",
  "publishedAt": "2026-07-17",
  "tags": [
    "AWS billing glitch",
    "Amazon Web Services",
    "cloud billing error",
    "AWS estimated bill",
    "Bill Radjewski",
    "AWS outage"
  ],
  "language": "en",
  "site": "TrendKia"
}