Quick Start

This guide walks you from signing up to a working first monitor. Goal: under 5 minutes.

Step 1 — Create an account

1. Go to okstatus.eu and click Get started for free.
2. Sign in with Google, GitHub or GitLab, or create an account with an email and password. Enterprise customers can sign in through their own identity provider with Sign in with SSO and their organisation slug.
3. Accept the Terms of Service.

Authentication is handled by Keycloak, hosted in France. No password ever reaches OKStatus itself when you sign in with a provider or SSO.

Step 2 — Create your organization

The onboarding wizard runs in four short steps, each with a one-line explanation you can switch off (“Expert mode”). The first one asks for:

• Workspace name — Shown in the dashboard (e.g. “Acme Corp”).
• Slug — The prefix of every status page URL you will publish (okstatus.eu/acme-corp/status/…). Editable later in Settings → General, but changing it breaks existing links.

Your time zone and date format are set afterwards, in Settings.

Step 3 — Add your first monitor

1. From the dashboard, click New monitor.

2. Choose the type:

   • HTTPS / HTTP — Monitor a website or API (most common).
   • Ping — Check that a server responds at the network level.
   • DNS — Verify a DNS record resolves to the expected value.
   • TCP — Test connectivity to a specific port.
   • gRPC — Health-check a gRPC service.
   • PostgreSQL / MySQL / MongoDB — Connect and run a real query.
   • SMTP / IMAP / Redis — Speak the protocol, and authenticate when you give the monitor credentials.

   LLM canary monitors have their own section in the sidebar.

3. Enter the URL, host or connection string:

   https://my-site.com

   Test now runs the check immediately, from your browser’s request, so you can see the answer before saving.

4. Configure the options:

   • Interval — Check frequency (5 min on Free, 1 min on Pro, 30 s on Max).
   • Regions — Where to monitor from. Free picks one; Pro allows 3 and Max 5 per monitor.
   • Content check (HTTP) — Verify the response contains a keyword, or that a JSON path holds an expected value.

5. Attach an alert channel on the last step, then click Create.

The first check starts immediately. Within seconds you’ll see your service’s status.

Is your site really available in Germany?

On Pro and above, select several regions to catch geographic routing issues. A site reachable from Paris can be unreachable from Frankfurt because of a misconfigured CDN.

Step 4 — Configure an alert

A monitor without an alert isn’t very useful. Configure at least one channel:

1. Go to Alerting → Channels.
2. Click Add a channel.
3. Choose the type. On the Free plan that means Discord, Telegram or a generic Webhook; Email, Slack and the rest start at Pro — the full grid is on Alert channels.
4. Apply to all my monitors is ticked by default, so the channel starts attached to every monitor you have right now. Untick it to pick monitors yourself.
5. Click Test to confirm the destination actually receives something.

Anti-false-positive logic

OKStatus doesn’t fire an alert on the first failure. A region only confirms a failure after two consecutive failed checks, and a multi-region monitor is only down when more than half its regions agree — one region alone is a partial outage, not an outage. Result: less noise, more reliable alerts. Full rules: Status & uptime.

Step 5 — Create your status page

1. Go to Status Pages in the sidebar and create one.
2. Customize the title, description, and logo, and pick the monitors it shows.
3. Leave Page published on.
4. Share the URL — okstatus.eu/your-org-slug/status/your-page-slug — with your users. The list has a Copy link action for it.

Visitors can subscribe by email to get notified of incidents.

What’s next?

• First Monitor in detail — Advanced options (headers, assertions, SSL).
• Configuring alerts — Email, Discord, webhooks, step by step.
• Status Pages — Custom domain, branding.
• Scheduled Reports — Recurring PDF reports by email.