How B2 classifies each platform’s regions

Every commercial region carries three or more availability zones and counts as a full region. Local Zones and Wavelength Zones are edge presence.

Microsoft publishes an availability-zone support flag per region rather than a zone count. Flagged regions count as full; the rest are regions without zone redundancy.

Every launched region carries three or more zones and counts as a full region. CDN, Media CDN and interconnect locations are edge presence.

Graded on availability domains. Only five OCI regions worldwide carry three; Oracle states that it launches new geographies with a single domain.

Graded on the zone count each publishes per region. Three or more counts as a full region; one or two does not.

Graded on per-region launch releases and Huawei’s published global-infrastructure dataset. Four regions whose count is unpublished or internally contradicted are treated as not zone-redundant.

Multizone regions count as full. Single-campus multizone regions and classic data centres do not.

The only AI cloud that documents availability zones as independent failure domains, but no region carries more than two and most carry one, so every region counts as a region without zone redundancy. Regions reserved for selected customers score zero.

None publishes a zone construct — the region is the smallest unit each of them exposes — so every region counts as a region without zone redundancy. Nebius private regions score zero.

AI clouds that publish no region identifiers: Nscale, Firmus, Yotta, Sharon AI, Together AI and Fluidstack. Where there is no published region list, there is nothing a reader can verify, so the metric scores zero rather than relying on an analyst estimate.