# Status and reliability

Myaza Trust is monitored every minute from Johannesburg, London, Frankfurt, Amsterdam, Virginia and California by an independent monitoring service that runs outside our own infrastructure.

## Live status

The [status page](https://status.myaza.co) shows the current state of each service, active incidents and scheduled maintenance. It stays up even if Myaza itself does not. You can subscribe there to be emailed when we post an incident or maintenance update.

## Availability record

The [reliability record](/reliability) shows measured production availability over the last 7, 30, 60 and 90 days, with a daily timeline, each service's median response time, monthly history, incidents and the methodology. A day with failed checks and no declared incident is marked as such rather than hidden.

For a procurement or security review, send the [shareable report](/reliability/report?period=90d), or download it as a PDF from that page. Any past period can be requested with `?from=YYYY-MM-DD&to=YYYY-MM-DD`.

The same data is available as JSON:

```bash
curl "https://trust.myaza.app/api/public/reliability?period=90d"
curl -o report.pdf "https://trust.myaza.co/api/reliability/report?period=90d"
```

## How availability is calculated

Availability is the share of checks that succeeded, over complete UTC days. A check is one request from one region; a slow but successful answer counts as available and is reported separately. Checks that failed during scheduled maintenance are **not** excluded. Days before monitoring began are shown as having no data, never as available.

These figures describe observed availability. They are not a service level agreement; contractual commitments, where agreed, are set out in your agreement.