A place for the numbers that matter
A future home for capacity and availability measurements, with their context attached.
Content revised · English
- Live measurements
- None connected
- Catalogue entries
- 35 plans
- Billing totals
- 105 cycle totals
- Region choices
- 8
Subject to product compatibility.
Measurement comes first
Catalogue figures are derived from stored plan data. No customer-server capacity, uptime, latency or incident counters are connected, so the page presents configuration evidence rather than unmeasured operational results.
What should be published
A useful operational record identifies what was checked, when it was checked and how customers were affected.
- Endpoint availability and probe methodology.
- Service and regional incidents with timestamps.
- Maintenance scope, expected effect and follow-up.
- Capacity figures with a clear definition.
A report you can interpret
A failed probe does not automatically mean every service is unavailable. The eventual status page should distinguish control-plane issues, customer traffic, regional connectivity and individual service events.
Review the proposed service framework
The draft service-level page explains which definitions must exist before an availability commitment can become a contract.
| Dataset | Definition to publish | Current boundary |
|---|---|---|
| Availability | Endpoint, probe locations and period | No connected monitor |
| Incidents | Start, affected system, impact and resolution | No production history |
| Capacity | Allocated / free resources and sample time | No live inventory feed |
| Maintenance | Notice, expected interruption and outcome | Prepared process |
| Catalogue | Capacity and compatibility per plan | Inspectable configuration data |