Availability Index methodology 1.1: retired listings no longer count as unavailable
- — Changed: from methodology 1.1 a configuration counts for a month only if the provider offered it then, meaning it was priced in the catalogue or reported in stock at least once. Listings a provider has retired are excluded instead of being scored as 0% available
- — New: September 2026 is published under both versions. The edition first published under methodology 1.0 is unchanged (/research/gpu-cloud-availability-index/2026-09); the methodology 1.1 restatement (/research/gpu-cloud-availability-index/2026-09-v1.1) uses the same history and freeze time and reads H100 27%, H200 48%, A100 51% and B200 15% of covered hours, with its own CSV and JSON
- — Changed: editions from October 2026 onward use methodology 1.1 only; each edition page states which version it was computed under