Home Corrections
🐛 Pricing errors · Source fixes · Provider updates

Corrections
Policy

Cloud pricing changes quickly. If you spot stale prices, incorrect plan specs, missing provider details, broken source links, or unclear assumptions on getInfra.cloud, tell us. We verify corrections against official sources and update the site transparently.

🎯

Why corrections matter

getInfra.cloud compares cloud providers, VPS plans, GPU instances, object storage, India data centre coverage, billing models, and related trust signals. Much of this data changes without public announcements. Providers update pricing, rename plans, adjust regions, add GPUs, remove older tiers, or change billing assumptions.

Our goal is not to pretend that pricing data is perfect forever. Our goal is to make the data source-driven, clearly dated, and easy to correct when something changes. Every correction request helps Indian developers, founders, DevOps teams, AI teams, and infrastructure buyers make better decisions.

Core rule

We correct factual errors. We do not change rankings, comparison labels, or editorial conclusions unless the underlying verified data changes.

🚨

What you can report

Send us a correction when you find a clear mismatch between getInfra.cloud and an official provider source.

💰

Wrong pricing

Incorrect VPS, GPU, storage, bandwidth, support, or add-on price shown on a provider or comparison page.

🧾

Incorrect plan specs

Wrong vCPU, RAM, GPU memory, storage type, bandwidth limit, billing unit, or monthly equivalent.

🌍

Region or data centre changes

New India region, removed region, changed city coverage, GPU availability change, or data residency clarification.

🔗

Broken or weak sources

Dead source links, outdated pricing URLs, missing official documentation, or unclear reference links.

☁️

Missing provider data

A listed provider has launched a new GPU, compute, storage, Kubernetes, or managed service plan we have not added yet.

⚖️

Unclear assumptions

A pricing note needs clearer tax, exchange rate, reserved pricing, spot pricing, or billing-cycle context.

✉️

How to submit a correction

Email us with enough information to verify the issue quickly. The more specific your report is, the faster we can correct it.

Subject line
Correction: [Provider/Page] - [Issue]
Page URL
The getInfra.cloud page where you found the issue.
Current value
The price, spec, region, or claim currently shown on getInfra.cloud.
Correct value
The updated value you believe should be shown.
Source proof
Official pricing page, product documentation, status page, calculator link, provider announcement, or verified support/documentation reference.
Suggested email format
Provider: E2E Networks
Page URL: https://getinfra.cloud/providers/e2e-networks
Issue: H100 hourly price appears outdated
Current getInfra value: ₹___/hr
Correct value: ₹___/hr
Official source: [paste provider pricing URL]
Notes: Price changed on the provider page after the June 2026 refresh.
🔬

How we review corrections

1

We confirm the affected page and data field

We identify whether the issue affects one provider page, a comparison page, the main pricing table, GPU pricing, object storage, data centre coverage, or multiple site sections.

2

We check official sources first

We prefer official provider pricing pages, product documentation, pricing calculators, public announcements, support documentation, and publicly available compliance or data centre pages.

3

We update related pages together

If a changed price affects the provider page, comparison table, GPU page, or side-by-side comparison pages, we update all affected placements instead of fixing only one visible instance.

4

We add a dated update note when needed

Material updates are added to the pricing changelog so users can see what changed, when it changed, and whether the correction affected a page recommendation.

⏱️

Correction priority levels

Priority
Examples
Target handling
High
Major pricing error, wrong GPU type, misleading monthly equivalent, incorrect India availability, or broken recommendation-driving data.
Reviewed urgently. Usually targeted within 48 hours after verification.
Medium
New plan, added region, updated bandwidth limit, missing source link, provider page improvement, or product category addition.
Reviewed during the current refresh cycle or next scheduled update.
Low
Minor wording issue, formatting issue, old screenshot, repeated wording, small layout problem, or non-critical clarification.
Added to the maintenance queue unless it affects data accuracy.
☁️

For cloud providers

Providers are welcome to report outdated pricing, missing products, incorrect plan specifications, broken source links, changed data centre coverage, or updated compliance details. Provider corrections are useful when they make the page more accurate for users.

However, getInfra.cloud does not accept requests to remove fair criticism, suppress competitor comparisons, change neutral labels into promotional language, or improve ranking position without verified data changes.

Accepted requests
  • • Correct a stale price with an official pricing URL
  • • Add a newly launched GPU, VM, or storage plan
  • • Update data centre or India region availability
  • • Fix compliance, SLA, or support details with source proof
  • • Replace a broken source link with a current official page
Not accepted
  • • Paid ranking changes or sponsored priority
  • • Removing competitors from comparison pages
  • • Replacing neutral findings with sales claims
  • • Adding unverified performance or uptime promises
  • • Hiding pricing limitations that affect buyers
⚠️

What we do not treat as corrections

Some requests may be important feedback, but they are not factual corrections unless they can be verified against reliable evidence.

Opinion disagreement

A provider, user, or reader may disagree with a comparison summary. We review the feedback, but we only change the page when the underlying facts, sources, or assumptions are wrong.

Private pricing without public context

Custom enterprise discounts, negotiated contracts, reseller pricing, and private quotes may differ from listed prices. We may mention them as custom pricing, but we do not use them as the default public baseline.

Marketing claims without proof

Claims such as fastest, most reliable, lowest latency, best support, or enterprise grade must be backed by official, public, and specific evidence before we add them to provider pages.

📌

How corrections appear publicly

Material corrections are added to the pricing changelog when they affect pricing, rankings, page conclusions, or buyer-facing comparison data. Minor copy fixes may not receive a public changelog entry unless they affect accuracy.

Example changelog entry

2026-06-10 · Updated AceCloud A100 GPU pricing after official source verification. Adjusted related GPU pricing table and AceCloud provider page. Correction submitted by reader and verified against provider pricing page.

The public log helps users understand whether a page recently changed, why it changed, and whether older screenshots or third-party references may no longer match the current version.

📬

Send a correction

Use the relevant contact option below. We read every correction report and prioritise updates that affect price accuracy, provider comparisons, or buyer decisions.

🐛

Report pricing error

Wrong price, stale GPU rate, outdated VM plan, or billing mismatch.

Email correction
☁️

Provider update

New service, updated source, changed region, or official provider correction.

Send update
🔗

Source issue

Broken link, outdated source URL, missing official reference, or unclear citation.

Report source
Correction Facts
Primary contact Email
High-priority target 48 hrs
Preferred source Official
Paid corrections No
Ranking influence No
Found an error?

Send the page URL, the incorrect value, the corrected value, and an official source link.

Email Correction → View Changelog →

Help Keep Cloud Pricing Accurate

Found a stale price or missing provider detail? Send us the source and we will verify it.