Hear about it first

Every incident, every update and every planned maintenance, the moment our team posts it. Pick the way that reaches you.

Email

We send a link to confirm the address first, and every email has a link to stop them. Nothing else is ever sent to it.

A Freesbe channel

If your team uses Freesbe, incidents can post into a channel of your own, as cards that turn green when the incident is resolved, like any other alert. An admin connects it inWorkspace settings → Integrations → Monitoring → Freesbe status, picks the channel, and that's all: there is nothing to paste. SeePost Freesbe status to a channel.

Webhook

Your own systems get a JSON POST for every incident update. Sign up with one request; the answer holds a secret that signs every delivery:

curl -X POST https://status.freesbe.net/api/subscribe/webhook \
  -H "content-type: application/json" \
  -d '{"url": "https://example.com/hooks/freesbe-status", "scope": "all"}'

{"id": "01J…", "secret": "…", "url": "https://example.com/hooks/freesbe-status"}

scope is all or outages. Each delivery carriesX-Status-Timestamp and X-Status-Signature: sha256=<hex>, the HMAC-SHA256 of <timestamp>.<body> with your secret. A delivery that doesn't get a 2xx is retried with growing waits for about a day; a webhook that keeps failing is switched off. The body:

{
  "type": "incident.created" | "incident.updated" | "incident.resolved",
  "incident": { "id", "title", "impact", "components", "state", "startsAt", "resolvedAt", "updates", … },
  "update": { "state", "body", "at" },
  "url": "https://status.freesbe.net/incidents/01J…/",
  "sentAt": 1762156800000
}

To stop: DELETE https://status.freesbe.net/api/subscribe/webhook/<id> withAuthorization: Bearer <secret>.

RSS or Atom

For readers and monitors: status.freesbe.net/feed.xml (RSS) orstatus.freesbe.net/atom.xml (Atom). One entry per incident, updated with each update.

Maintenance calendar

Planned work as events in your calendar: subscribe tostatus.freesbe.net/maintenance.ics (in most calendars, "Add calendar from URL" or "Subscribe"; the address also works as webcal://status.freesbe.net/maintenance.ics). Each event links to the maintenance notice.

Machines

GET /api/summary.json answers with the overall status, every part's status and 90-day uptime, and the open incidents, cached for a minute and open to any site./badge.svg is a small badge for a README:

[![Freesbe status](https://status.freesbe.net/badge.svg)](https://status.freesbe.net/)

/api/status.json has everything this page shows, and/api/history.json?month=YYYY-MM a month of history.