New Multi-region uptime checks and custom-domain status pages

Cloud Status Reliability Rankings

Explore current provider checks and incident evidence while the status reliability sample grows.

Source-attested sample rebuilding · no records currently meet this view's publication floor

Evidence you can explore now

1,871 vendors with a verified current provider check. A fresh check shows source coverage; it does not qualify a reliability rating or prove every customer is unaffected.

What this view needs before ratings appear

Each 30-day comparison needs at least 576 verified hourly observations. A 90-day percentage needs 1,728. SLA evidence also needs the provider's published numeric target and a direct source link.

Unverified and legacy records do not count toward these requirements. There is no promised publication date: missing observations and unmatched notices can extend the wait.

Recently checked providers

Sample of 12 verified current checks, listed alphabetically. Open a service to inspect its source, observation history and community reports.

Recent provider incident evidence

How we calculate the status reliability signal

The signal summarizes known provider-status observations over the selected period. Operational observations contribute to the reported share; maintenance and unknown periods are kept separate. Internal collection timing, normalization rules, and quality controls are not published.

This is a vendor status-page signal, not end-to-end probe uptime, component-weighted availability, or an SLA calculation. See also transparency grades and our methodology.