Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The September 1 change removes a specific overage-control restriction. It does not establish a September 10 eligibility expansion for Pay-as-you-go subscriptions or AI developer tools.
- Projects must link to a Cloud Billing account receiving valid monthly invoices and have at least one active, supported, non-free-trial subscription.
- Overages apply to seat-based editions such as Standard, Plus and Standard Emerging Market. Pay-as-you-go already charges for all usage and does not use this switch.
- A feature stops at its pooled quota when overages are disabled. Enabling them bills excess usage; storage and indexing also have separate shared-pool rules.
- Without a monthly spend limit, excess usage continues to accrue charges. Even with a cap, stopping may take several minutes and spending may slightly exceed it.
- Billing eligibility, editions, quotas and IAM are not network faults. A fixed exit has diagnostic value only with clear DNS, TLS, proxy 407 or connection-timeout evidence.
What changed: the September 1 overage-control restriction removal
The September 1, 2026 Gemini Enterprise release note says overage controls can now be configured for all projects linked to invoiced Cloud Billing accounts. Customers who received an email titled [Billing Update] New Gemini Enterprise overage billing controls launching Aug 17, 2026 previously could not enable overages even with invoiced billing. Google now explicitly says that restriction no longer applies.
The entry gives only a date, without an exact time or time zone, so the precise release time is UNKNOWN. It concerns overage controls, not Pay-as-you-go subscription eligibility, and does not announce general availability of AI developer tools on September 10. Keep these boundaries so two billing mechanisms are not described as one release.
Separate seat-based overages from Pay-as-you-go
Seat-based editions such as Standard, Plus and Standard Emerging Market have pooled feature quotas. When a quota is reached, the feature stops unless an administrator enables overages, which allow continued use at official overage rates. Standard Emerging Market still serves eligible customers only; the September 1 change did not remove its own eligibility conditions.
Pay-as-you-go is different: all feature usage is already billed by consumption, so the overages switch does not apply. Seeing overage controls does not establish access to a Pay-as-you-go subscription, developer tools, a particular region or pricing. Those are separate account and product facts.
Eligibility: invoiced account, active subscription and administrator role
Before configuring overages, the project must link to a Cloud Billing account receiving valid monthly invoices, have at least one active, non-free-trial supported subscription, and be operated by a Gemini Enterprise Administrator. Stop for ordinary online self-service billing, free-trial-only access, unsupported editions or missing administrator roles.
Export an eligibility record with project ID, billing-account type, invoice status, edition, seat count, subscription state, administrator and billing owner, current pooled quota and switch settings. If any field cannot be verified, do not keep toggling controls. Preserve console evidence and ask Google Cloud support or the account team to confirm.
Cost boundaries: overages, shared pools and spending caps
With overages enabled, consumption beyond an edition's included feature quota is billed by usage. Storage and data indexing share a pool per project and location, and exceeding it may automatically generate charges. One edition's switch does not disable every cost. Use current bills and official prices for rates, currencies, support fees and taxes.
Google explicitly warns that enabling overages without a monthly spend limit allows unlimited continued billing for feature use beyond pooled quotas. The cap can cover the Gemini Enterprise app, Agent Platform and AI coding tools such as Antigravity, within the Vertex AI API billing-service scope.
Safe changes: preserve old state and validate with a small budget
First save current switches, selected editions, pooled usage, billing period and spending limits. Second set a finance-approved low monthly spend limit and budget alerts. Third enable only one nonproduction project or low-risk team. Fourth use a minimal task to exceed one controllable quota. Fifth verify usage, charges and service scope in Usage & Spending and Cloud Billing.
One success establishes control behavior only for that project, edition and time; it cannot be generalized to other locations, features or projects. Google says automatic stopping at the spending cap may take several minutes and actual charges may slightly exceed it. A cap does not guarantee zero overspend, so test volume and stopping thresholds must remain conservative.
Troubleshooting: Usage limit reached is not necessarily a network issue
For Usage limit reached, first distinguish a project's monthly spend cap from a feature's pooled quota with overages disabled. If the switch is absent, check invoiced billing, active subscription, edition and administrator role. If billing tabs are absent, also check viewing permissions such as Billing Viewer or Billing Administrator.
Only after eligibility, quotas and IAM are satisfied, with remaining DNS failures, TLS handshake errors, proxy 407 or connection timeouts, consult the systematic proxy connection checklist. A fixed exit cannot produce monthly invoices, raise pooled quotas, grant administrator access, enable overages or cancel charges.
Stop and roll back: restore switches and keep watching bills
For unexpected charges, incorrect edition scope, ineffective spending caps, unreconcilable usage, expanded permissions or unacceptable business-continuity effects, stop new tasks and disable overages for the project or affected edition. Features at pooled quota will stop afterward, so prepare manual workflows or supported alternatives in advance.
After rollback, monitor Usage & Spending and Cloud Billing until delayed charges appear, retaining before-and-after states, times and responsible people. Completion means provable eligibility, recoverable prior state, reconcilable costs, validated caps and alerts, and rehearsed disabling behavior. PRODUCT_FIT=CONDITIONAL_NETWORK_ONLY.
Sources
Frequently Asked Questions
What specifically opened on September 1?
Google removed an overage-control restriction: invoiced projects that had received a specified billing email previously could not enable overages. That restriction no longer applies.
Does this make Pay-as-you-go subscriptions available to every project?
No. The release note concerns only overage controls and does not establish changes to Pay-as-you-go subscriptions, AI developer tools, region or account eligibility.
Which editions can enable overages?
The official configuration page lists seat-based editions including Standard, Plus and Standard Emerging Market, requiring invoiced billing, at least one active non-trial subscription and administrator permissions.
What happens with overages disabled?
A feature stops at its pooled quota, usually recovering when the quota resets or the next billing period starts. Storage and data indexing also have separate shared-pool rules.
Does a spending cap stop charges immediately?
Not necessarily. Google warns stopping can take several minutes and spending may slightly exceed the limit. Combine small-budget tests, budget alerts and manual stop conditions.
Can a fixed IP remove Usage limit reached?
No. The platform controls quotas, caps, editions, billing and IAM. A fixed exit helps diagnose only network evidence such as DNS, TLS, 407 or connection timeouts.