Changelog · Perstat

On this page

The latest verified product entry is dated 2 October 2026. Product releases and announced API changes are listed separately below.

2026-10-02

Registration. Activation links are sent only to the email address being registered.
API notice: preserve monitor records. Announced today, with removal no earlier than 1 January 2027 at 00:00 UTC. Integrations have more than 90 days to adapt.
- DELETE /monitors/{id} authenticated with an API key will be refused after the notice period. Archiving preserves incidents, check history, SLA rollups and exclusion windows.
- DELETE /projects/{id} with an API key will require moving its monitors to another permitted project using reassign_to. Deleting an empty project remains available.
- Archive over REST with POST /monitors/{id}/archive; restore with POST /monitors/{id}/restore. Restoring returns the monitor paused and requires a free plan slot. The existing MCP tools follow the same behavior. The API reference lists the operations.
- These changes concern API keys. Deletion from a signed-in app session remains available.

PDF report per monitor. The monitor view offers Download PDF report for 7, 14, 30, or 90 days, on every plan. The report is not signed or certified.

Projects over MCP. An agent can create a project with create_project. Like create_monitor, it needs an organization-wide key with monitors:write.

Write tools over MCP. Pipelines and coding agents create, update, pause, archive, and restore monitors over MCP. Every monitor write needs a key with monitors:write.
- Creating a monitor needs an organization-wide key.
- A key narrowed to projects or monitors changes only the monitors it covers.
- Over REST, keys stay read-only.

MCP endpoint for agents. Coding agents and pipelines read organizations, projects, monitors, incidents, and status pages over MCP at POST /mcp, authenticated with an API key.

API keys with scopes. Owners and admins manage organization-bound bearer tokens (pst_...) in the app under Integrations, then API keys. The API reference has the details.
- Scopes cover monitors, incidents, status pages, and webhooks.
- Keys can be narrowed to projects or single monitors.
- Revocation and expiry take effect on the next request.
- Key authentication is active on 7 read endpoints.
- Write scopes were selectable but not yet honored, superseded by the MCP write tools on 2026-07-29.

perstat.io went live. The product’s home moved here, and www redirects to the apex.
app.perstat.io became the product domain. The web app runs under app.perstat.io with the Perstat name, against api.perstat.io. Sign-ins land there.
A public status page on every plan. Every plan now carries at least one public status page, the entry tier included.
Website. The site added the check-type reference at /check-types/, solutions by role at /solutions/, and the live ops globe on the homepage.

Probe fleet expanded to 6 continents. Three new regions came online and joined the existing three. Each inhabited continent now has one region, and all 6 are heartbeating in production.
- New: sa-gru in South America, af-jnb in Africa, and oce-syd in Australia
- Existing: na-ewr in North America, eu-fra in Europe, and as-sgp in Asia

Signed webhooks and Slack. Generic webhook targets shipped with HMAC signatures (x-perstat-signature), secret rotation, and an in-product test fire. Slack incoming-webhook targets shipped with them. Both fire when an incident opens or resolves.

Host agent service watch. Agents watch named services with anti-flapping grace and report them alongside CPU, memory, and disk. The documented update mechanism is signed and runs without root privileges.
Alert hygiene. Acknowledging an incident takes ownership and quiets every device. Reminders go to the owner, not the whole team.

Manual incidents and post-mortems. Incidents can be opened by hand, curated, and published to status pages, with post-mortems and action items attached to the incident.

On-call escalation went live. It runs push, then SMS, then a phone call, until someone acknowledges. Phone numbers are verified by one-time code before they can be paged.

Status page subscribers. Email subscriptions use double opt-in and one-click unsubscribe, and notify subscribers when an incident opens and recovers.

Private status pages. Each status page can be set to draft, public, shared-password, or viewer-account access.