Before you renew
Vendor scorecards
How these numbers are worked out
Vendor scorecards
Every recorded change between 16 Aug 2026 and 22 Aug 2026 — 7 days observed
| Cloud | Increases / year | Rises · falls | Typical risesampled | Largestsampled | Spreadsampled |
|---|---|---|---|---|---|
| Azure132,678 recorded increases | too soon to say | 132,678131,643 | +314.7%mean +22225.7% | +605885.2% | 1,871 SKUson 2 days |
| GCP1,011 recorded increases | too soon to say | 1,0111,472 | — | — | — |
| AWSno increase recorded | too soon to say | 090 | — | — | — |
Counts and rates are exact over the span above. The three columns marked sampled rest on the 2,000 most recent of 133,689 recorded increases — a median needs the individual values, and reading every one of them would be a whole-archive scan on each page view. Suspected listing corrections are excluded throughout: a placeholder price becoming a real one is not a vendor raising a price, and counting it would put whoever publishes the most placeholders at the top of this table. Typical rise is the median, because these distributions have long tails and a handful of very large moves on sub-cent meters drag any mean somewhere useless. These are published list prices, so a scorecard describes what a vendor does in public — not what it does to your account at renewal, which is negotiated and private.
A scorecard is a summary of what is already on the changes page, so every figure here can be traced back to the dated rows it came from. Nothing on this page is a forecast.