Skip to content

Status Pages

A published public status page

Status pages let your users check the state of your services in real time.

  1. Go to Status Pages in the sidebar (under Public).
  2. Click New status page.
  3. Give it a title and an identifier (URL) — the page’s slug.
  4. Open the page and pick, under Displayed monitors, which monitors it shows.

A page lives under your organisation’s own slug:

https://okstatus.eu/<your-org-slug>/status/<page-slug>

The org slug comes from Settings → General; the page slug is fixed at creation and cannot be changed afterwards. The status pages list has a Copy link action that gives you the full address.

PlanStatus pages
Free1
Pro5
Max20
EnterpriseUnlimited

Everything below is in the page’s General section:

OptionDescriptionPlan
TitleName shown at the top of the pageAll
Short descriptionIntro text below the titleAll
Accent colorHex colour used for the page’s highlights (default #00e599)Pro
ThemeAuto (follows the visitor’s system), Light or DarkPro
LogoUploaded image or URL, shown in the headerPro
FaviconUploaded image or URL, the browser-tab iconPro
Page publishedAn unpublished page is not publicly reachable at allAll
Show incident historyLists past resolved incidents at the bottom of the pageAll
Visitor issue reportsShows a “Report an issue” form on the page (on by default)All
Password protectionRequires a password to view the pageMax
Heartbeat bar rangesWhich windows visitors can pick: 1h, 6h, 12h, 24h, 7d, 30d, 90dAll

At least one heartbeat range must stay enabled. 90d is opt-in — existing pages keep the six shorter ranges until you tick it.

A status page can also be served from a domain of your own (status.your-domain.com) on Pro and above. Point a CNAME at OKStatus and tell us the hostname — the certificate is provisioned for you. Custom domains are set up by support today (contact@okstatus.eu); there is no self-service field in the editor yet.

Acme Cloud status.acme.io All systems operational API99.98 % Website100 % Dashboard99.71 % Scheduled maintenance · Sat 02:00–03:00 CET Past incidents · 12 Aug — API latency (resolved in 41 min) WHAT YOUR VISITORS GET Overall status banner Per-service state + uptime % 90-day history bars Response time per service Incidents, live and past Maintenance, announced early OPTIONS Custom domain · logo · colours Password (Max) · e-mail + RSS subscribe “Report an issue” button (CC2.3) Embeddable status badge

The status page automatically shows:

  • Overall status — Operational, degraded, or down.
  • Each monitor’s state — With a visual indicator (green, amber, red).
  • A heartbeat bar and uptime % per monitor, over the range the visitor picks from the ranges you enabled.
  • Response time — Average latency per service.
  • Announcements — Free-form banners you publish yourself (see below).
  • Incidents — Ongoing and, if enabled, past ones with all their updates.
  • Scheduled maintenance — Shown in advance to give your users a heads-up.

An announcement is a lighter-weight message than a formal incident — planned work, general information, or an “all clear” — shown at the top of the public page. In the page editor’s Announcements section, give it a title, optional details, and a type: Information, Warning, Outage, Resolved / operational, or Neutral. Announcements can be archived and republished; archived ones stay listed under the editor for reuse.

Use an incident instead when you want subscribers emailed and a resolution timeline.

The editor’s Embed section gives you two ready-to-paste snippets:

  • Pulse badge — a small live SVG pill, on every plan. Details and other badge shapes: Status Badges.

  • Floating status bubble (Max) — an expandable corner widget powered by the same live status:

    <script
    src="https://okstatus.eu/widget.js"
    data-org="YOUR_ORG_SLUG"
    data-page="YOUR_PAGE_SLUG"
    async
    ></script>

Your users can subscribe to your status page to get email notifications:

  1. The visitor clicks Subscribe on your status page.
  2. They enter their email and confirm via a validation link (double opt-in).
  3. On every new incident or incident update, they receive an automatic email.
  4. They can unsubscribe at any time via the link at the bottom of each notification.

Subscriptions are entirely handled by OKStatus — no extra setup needed. Full detail: Alerts from a status page.

Visitors can also flag a problem your monitors haven’t caught yet, using the Report an issue button on the public page. The report — their email, an optional affected monitor, and a message — is emailed to the organization’s owner and appears in the dashboard’s notification bell. It’s clearly marked as visitor-submitted, not a confirmed OKStatus-detected incident, so verify before acting on it. You can turn the form off per page.

Status pages are public by default — reachable without authentication. On Max and above you can put one behind a password instead, for a page meant only for your customers.