The Experiment that Generated a Nightmare. Analysis of the Incident Related to the Google Vertex AI Service

Introduction: Setting the Scene

This report provides an in-depth analysis of the escalation of a conflict that began with a seemingly harmless cloud experiment and evolved into a serious financial and procedural dispute with a technological giant. The study focuses on the case of a user (the creator of this website) who, on August 28, 2025, while attempting to generate video clips for free in Google AI Studio, unexpectedly transitioned into the paid mode of the Vertex AI service.

The problem started when a message on the Google AI Studio page informed about a limited number of free data for testing, while encouraging the user to „use the Gemini API” and displaying a „Get API Key” button. For a user who already had an API key from another Google Cloud project, the interface suggested that this was a simple path to bypass the free limit and continue testing without incurring costs. There were no clear warnings about the price list or a cost calculator on the page, which led to the rational, though mistaken, assumption that the service was free. Such a design approach, which fails to provide clear pricing information at the moment of service activation, raises serious doubts about compliance with consumer law.

The Moment of Impact: August 28, 2025

After activating the Vertex AI service using the existing API key, the user generated a dozen 8-second video clips. The value of the received service was negligible, as only two of the clips were even partially consistent with the commands entered. Nevertheless, this short-lived and unproductive use initiated an avalanche of events. Within a few hours of the experiment, Google’s billing system entered a state of contradictory and chaotic functioning. The user received a notification about a “payment booked” of 200.00 PLN, and simultaneously, within just a few hours, the system warned of “outstanding payments” and “suspicious activity on the Google account.”

This fundamental inconsistency in communications points to a serious systemic flaw where various components of Google’s payment infrastructure operate in an uncoordinated manner. Such chaos put the user into a state of alarm and a feeling of threat, which forced them to immediately block their payment card. This action initiated a long and exhausting communication process with the support department, whose goal was to clarify the escalating, unjustified charges.

The Support Labyrinth: A Case of Deliberate Misdirection

First Encounter: Lack of Understanding the Core Problem

The initial correspondence with Google Cloud support, represented by agent A…, proved that the company operates based on rigid, procedural rules, ignoring the user’s substantive arguments. The agent reported that the fees of 1,538.41 PLN were related to the Vertex AI service, and the free trial credits had expired, which resulted in the account being automatically „upgraded” to the paid version. This response omitted the key issues raised by the user: the lack of conscious consent to a paid subscription, the lack of price transparency, and the extreme disproportionality of the fees to the value of the service obtained.

Procedural Impasse: The „Fraud” Tactic

A crucial moment in this dispute was the incorrect redirection of the case. Although the user clearly described the problem as a „bill shock” caused by a lack of transparency, the case was forwarded to the „unauthorized transactions team.” Following this decision, subsequent responses from agents, including M…, were nearly identical, boilerplate messages. M… repeated twice that the „unauthorized transactions team… was unable to confirm fraudulent activity” and therefore „is unable to provide further assistance.”

Such action constitutes a systemic strategy that allows for the use of an automated, low-cost problem-solving path, while avoiding substantive discussion about the flaws in the business model. By incorrectly classifying a justified consumer complaint as a false claim of fraud, Google deliberately creates a communication impasse, forcing the user to abandon their original argument or seek alternative paths to resolution.

Breaking the Impasse: The Power of a Precise Question

Faced with repetitive, unproductive responses, the user made a final attempt to break the impasse by asking one, impossible-to-ignore question: “What is the official total amount that Google Cloud is trying to require me to settle?”. This direct inquiry, after days of vague and confusing communications, finally yielded a concrete answer. A new agent, R…, confirmed that the total amount due was 3,398.37 PLN. This exchange, though seemingly trivial, reveals a fundamental flaw in the support process, which is unable to provide basic financial information without direct pressure from the customer.

The Impossible Bill: Technical and Logical Absurdity

Unjustified Claim: 1580 Video Generations

At the height of the dispute, Google provided a billing report that revealed the scale of the alleged consumption. According to the report, on August 28, 2025, the user was charged for 1580 generations of the „Veo 2 Video Generation” service. The user formally disputed this data, proving that it is a physically and logically impossible claim for one person to realize.

The technical analysis of this situation proves the absurdity of the bill. Assuming that generating one video clip, including time for prompt writing, process initiation, and file saving, takes just 1-2 minutes, executing 1580 generations would require over 38 hours of continuous, uninterrupted work in a single day. The user’s actual use was limited to “a few dozen attempts.” Such a glaring disproportion between the actual action and the data in the billing report unequivocally indicates a failure on Google’s side. The most probable causes are an error in the billing system that multiplied a single request, or a security vulnerability that allowed unauthorized API calls.

The table below illustrates the technical and logical contradiction present in the Google billing report:

Demand for Server Logs: Seeking Accountability

To prove the defectiveness of the Google system, the user demanded the provision of detailed API logs for the „Travel…” project from August 28, 2025. These logs, containing timestamps, source IP addresses, and call parameters, are the only reliable evidence of the origin and number of operations. Google’s unwillingness to provide this data confirms the non-transparency of its system and indicates that the company is unable to prove the validity of its claim. Charging a client for fees that cannot be supported by transparent and verifiable data is a violation of fundamental principles of fair trade.

Systemic and Global Problem: Flawed Assumptions of the „Pay-As-You-Go” Model

The incident is not an isolated case. It reflects systemic flaws in the architecture of Google Cloud’s billing. The collected evidence, including the report on „Analysis of Systemic Billing Practices,” documents over 30 global cases where users received astronomical, unexpected bills. The main causes of these events include:

• Lack of Default Spending Limits: The „pay-as-you-go” model is designed without a built-in mechanism that would automatically stop charging after a set threshold is exceeded. As a result, even a minor code error (e.g., an infinite loop) or a compromised API key can generate bills reaching tens or hundreds of thousands of dollars in just a few hours.
• Delayed Alerts and Reporting: Users often receive notifications about exceeding the budget with a significant delay, when costs have already reached substantial amounts.
• Errors on Google’s Side: The latest incidents, including those with Gemini services in 2025, prove that the problem may lie in software flaws and the billing systems of the provider itself. In one documented case, charges for the Gemini API service continued to rise even after the API keys were deleted, which definitively excludes user fault.

The table below provides a summarized list of global incidents that show that Google Cloud billing problems are a common phenomenon, and their triggers are repetitive.

In-Depth Analysis of Selected Cases

The $450k Incident (Reddit thread)

The $450k case is the most glaring example of a culmination of systemic flaws. As shown by the analysis of reports, the bill was generated after an API key in an acquired application was compromised. The lack of hard usage limits at the project level allowed an unauthorized user to make an astronomical 19 billion Translation API calls over 45 days. This incident exposes critical gaps in Google’s proactive security, as neither the user nor Google received any real-time alerts that could have immediately detected and stopped the anomaly. Initially, Google refused to waive the bill, citing its terms and conditions. Only after wide publicization of the case on public forums, especially Reddit, did the company yield to pressure and offer a partial refund. This pattern of conduct suggests that decisions on waivers are made ad hoc, often under the influence of public opinion, rather than based on fair and consistent support principles.

BigQuery and Translation API Incidents

Many cases of high bills are related to services whose costs are difficult to predict. The incident with the 58,000 EUR bill for just 17 queries in BigQuery reveals a fundamental gap in price transparency. The user, unaware that each query in this service scans enormous amounts of data across the entire database, quickly generated massive fees. A similar situation occurred with a startup that received a bill for 85,000 USD due to an error in Translation API integration. It took the company weeks to get a response from the support team, with the threat of account suspension looming. These examples prove that Google’s billing model lacks precise tools for cost forecasting, and delays in usage reporting exacerbate the problem, allowing further, uncontrolled charging.

Gemini Incidents (2025)

The latest incidents related to generative AI services, such as Gemini, provide the strongest evidence of systemic errors on Google’s side. On developer forums, including discuss.ai.google.dev, reports emerged in 2025 about a critical billing error that generated bills worth over 70,000 USD for non-existent usage of Gemini 2.5 Flash Native Image Generation. These reports are significant because users claimed that the charges continued to rise (by nearly 10,000 USD per day) even after all associated API keys were deleted, which definitively excludes user fault and points to an internal Google error. Additionally, users noticed that the official status page did not reflect these issues, which deepened frustration and made it difficult to prove the system’s defect. This situation proves that Google not only shifts responsibility for human errors onto customers but is also unable to ensure transparency and control over costs generated by its own software.

Polish and European Cases

The phenomenon is not limited to the USA or India. In the Polish development community, on the Pasja Informatyki forum, an incident was noted where a developer received a bill for 26,000 PLN for just two hours of Google Maps API testing. The user was threatened with debt collection, and the lack of responsiveness from Google led to legal considerations. This case, like other European ones (e.g., the 58,000 EUR BigQuery bill), shows that systemic gaps are a global problem, and communication and procedural barriers for users from other regions only deepen their helplessness in the face of the technological giant.

Legal Analysis and Regulatory Context

Growing Scrutiny of Big Tech Practices in the USA and EU

Google Cloud’s billing practices are not an isolated problem in the broader context of growing legal and regulatory scrutiny over dominant technology companies. The increase in pressure from antitrust bodies and consumer protection agencies, both in the United States and the European Union, indicates a growing awareness of the systemic threats posed by dominant platforms. Problems with price transparency and accountability fit into a broader pattern of alleged non-transparent business practices by the company.

Key Rulings and Judgments

2025 Jury Verdict ($425M)

From a legal point of view, one of the key precedents is the federal jury verdict from 2025, which ordered Google to pay 425 million dollars for violating user privacy. The verdict concerned allegations of continued data collection even after millions of users had turned off the activity tracking function.

Legally, this verdict is analogous to the billing situation because it indicates that courts are willing to hold Google accountable for misrepresentation and lack of transparency. Despite the company’s assurances that „privacy tools give people control over their data,” the jury found that the company acted non-transparently and contrary to its declarations. The same logic can be applied in the billing context, where Google declares a „pay-as-you-go” model, but the actual lack of control and preventative mechanisms leads to unlimited financial liability on the client’s side.

US Department of Justice Lawsuit vs. Google

The US Department of Justice antitrust lawsuit against Google, in which the company was found to be a monopolist in the search engine market, also provides important context. The court imposed an obligation on Google to share data with competitors, which is intended to limit its market dominance. Although this case does not directly concern cloud services, it confirms Google’s position as an entity with monopolistic practices, which is important in the legal argument regarding responsibility in customer relations. Regulatory authorities worldwide consistently question Google’s dominant market position and its consequences for consumers and competition.

Rulings in EU Jurisdiction

The European Union is also conducting a number of proceedings against Google. Based on the EUR-Lex database, key rulings can be identified, such as:

• Case T-334/19 (Google LLC and Alphabet Inc. vs. European Commission), concerning the abuse of a dominant position in the online search advertising intermediation market.
• Case C-460/20 (TU and RE vs. Google LLC), concerning the processing of personal data in the context of the right to be forgotten.

These rulings prove that Google’s practices are under constant, global legal scrutiny, and the lack of transparency and abuse of market position are phenomena for which the company is consistently held accountable in various jurisdictions.

Regulations as a Response to Market Gaps (e.g., EU Data Act)

The reaction to market gaps and lack of transparency is also the growing number of regulations. An example is the EU Data Act, which will enter into force on September 12, 2025. This act aims to increase competition in the cloud sector by requiring providers to charge for data transfer „at cost.” In response to this, Google proactively withdrew from these fees by introducing the Data Essentials program, which enables free data transfer to other clouds. This move, although beneficial to users, proves that Google is aware of the flaws in its model and is willing to modify it under regulatory pressure. This strengthens the argument that existing problems are problems that can and must be solved.

Conclusions and Recommendations

Summary of Systemic Gaps in Google Cloud Billing

This report, based on the analysis of over 30 documented cases, proves that Google Cloud billing problems are not a series of isolated events but the result of systemic flaws in the service design. The lack of default, hard spending limits, insufficient proactive alert mechanisms, and non-transparent pricing for AI-based services constitute gaps that make the „pay-as-you-go” model risky and potentially financially catastrophic for the user.

Conclusions Regarding Lack of Transparency and Accountability

The „shared responsibility” model in Google Cloud is only balanced in theory. In practice, the burden of unlimited financial liability for errors, which are largely possible due to the fundamental design flaws of the provider itself, falls on the clients. Even in cases where the problem lies in a Google system error (as in the Gemini incidents), the user encounters a lack of transparency and ineffectiveness of support channels.

Recommendations for Changes in Company Policies

To solve the identified problems, Google Cloud should implement the following changes:

• Default, Hard Spending Limits: Introduction of a default limit at the project level, the exceeding of which automatically blocks further charging.
• Improve Price Transparency: Simplification of pricing models for services whose costs are difficult to predict (e.g., BigQuery, AI/ML) through more accurate calculators and simulations.
• Streamline the Support Process: Ensuring faster, less automated, and more empathetic customer service for billing issues.
• Proactive Alerts: Default activation of budget alarms that not only inform about exceeding a threshold but can also automatically stop services.

Legal Recommendations for Complainants

The complaint should refer to legal analogies from other proceedings against Google. The argumentation should be based on the thesis that the lack of transparency in billing and non-transparent support practices are part of a broader, documented pattern of misleading business practices for which the company has already been held accountable in other jurisdictions. Legal precedents, such as the $425 million verdict in the USA or EU rulings, provide a strong basis for arguing that current billing practices are inconsistent with expectations for transparency and fairness in consumer relations, which may be subject to legal oversight.

Appendices and List of Sources

Press Materials / Press Kit