One number for customers and auditors.

The person funding reliability wants a clear scope and price. The person reviewing it wants a traceable availability number. Perstat addresses both, but it does not promise that every organization can replace 4 existing tools without checking its workflows first.

Assess the economics

Compare Perstat against your workflow

Perstat combines external monitoring, status pages, incident response and on-call, and a curated availability record. Whether that replaces one tool or several depends on your organization’s needs:

• Checks
• Status-page access
• Alert channels
• Integrations
• Retention

The pricing page publishes the current plan prices and gates. The comparison pages show product-by-product differences with review dates.

Weigh those details against the contracts and renewal dates in your own stack. Perstat makes no guaranteed savings or consolidation claim.

Check the operating location and procurement status

Perstat is a German GmbH, and the control plane runs in the EU. Application, database, and backup infrastructure sit with a French provider in Frankfurt and Gravelines. Backups are encrypted before upload.

Probe nodes are measurement points, and some sit outside the EU.

The security page lists current controls, providers, and open items. DPA/AVV, TOM, and subprocessor materials are in preparation and are not a finished procurement pack today.

Read the editorial sample

The table shows example data for one quarter of one service. It is a public editorial artifact that demonstrates the calculation, not a self-service customer report.

The sample incident starts at quorum confirmation and ends at confirmed recovery. The sample monitor runs a policy of 1 failed check per region with a quorum of 2 regions, not the default of 2 consecutive checks. The announced maintenance window stays visible and is excluded separately. Availability is floored, never rounded up.

Later false-positive curation is a distinct action. It is attributed, carries a reason and a previewed effect, and can be reversed. See the full editorial sample.

Review the evidence

Measure independently across regions

For supported probe checks, plans select 2, 3, or up to 6 regions. The standard alert policy requires 2 region votes, and alert profiles can change that rule. The network page documents the current topology.

Agent and heartbeat checks do not use regional quorum.

Publish from one shared record

A linked status page and incident view use the same underlying monitor and incident data. Publication and page configuration remain explicit choices. The safe claim is a shared record, not that every public view always matches.

Use the record in your own audit

The record can support your own audit, assurance, or regulatory workflow. Procurement and regulatory conclusions remain with your organization and advisors.

Perstat does not issue an assurance report, make you meet DORA or NIS2 requirements, or make a legal determination.

Limits

• The record is recomputable, attributable, and reversible, but not tamper-proof.
• The published history window depends on the plan and is not a complete object-level deletion schedule. Review the retention boundary against your policy.
• The PDF report per monitor covers 7, 14, 30, or 90 days and is not signed or certified. Organization data can be prepared manually as CSV files with a manifest on request.
• Enterprise SSO through SAML is not available. Sign-in is email-based.
• The scope is uptime and its record, not APM or log management.

Make the decision from the record

Check the product gates against your current stack, then recompute the editorial sample.

See pricing, read the security controls, or open the sample SLA report.