Statux Synthetics Help Center

Everything you need to set up, manage, and optimize synthetic monitoring for your websites, APIs, and internal services.

Browse Topics

Getting Started

New to Statux Synthetics? Follow these steps to create your first synthetic check and start monitoring your endpoints in minutes.

Step 1: Create Your Account

Sign up at statux.io/sign-in with your email address. You can also sign in directly at synthetics.statux.io/sign-in. All Statux products share a single account, so if you already use Statux Pages or Statux Alerts, you are ready to go.

Free trial: Every new account starts with a free trial so you can explore all features before choosing a plan.

Step 2: Create an Organization

Organizations are the top-level container for everything in Statux Synthetics — checks, relays, teams, webhooks, and billing all belong to an organization.

  • After signing in, click Create Organization from the dashboard.
  • Enter a name for your organization (for example, “Acme Corp”).
  • Choose a unique slug (for example, acme-corp).
  • You can invite additional team members later from the Organization settings.

Step 3: Create Your First Synthetic Check

A synthetic check is an automated probe that tests one of your endpoints at regular intervals and reports whether it is up, down, or degraded.

  • Navigate to Checks in the sidebar.
  • Click Create Check.
  • Select a check type: HTTP, HTTPS, or TCP.
  • For HTTP/HTTPS checks, enter the full URL of the endpoint you want to monitor (for example, https://api.example.com/health).
  • For TCP checks, enter the host and port (for example, db.example.com on port 5432).
  • Set the check interval — how often Statux should test the endpoint (for example, every 1 minute, 5 minutes, or 15 minutes).
  • Configure the expected status code for HTTP/HTTPS checks (default is 200).
  • Set a timeout threshold — how long to wait before marking the check as failed.
  • Click Create Check to save and start monitoring immediately.
Tip: Start with an HTTP check against your website's health endpoint. This gives you immediate visibility into availability and response time.

Step 4: Understand Check Results

Each check reports one of four statuses after every run:

  • Up — The endpoint responded successfully within the expected parameters (correct status code, within timeout).
  • Down — The endpoint did not respond, returned an unexpected status code, or the connection was refused.
  • Degraded — The endpoint responded successfully but the response time exceeded the degraded threshold, indicating performance issues.
  • Unknown — The check has not yet run, or there was an internal error preventing result collection.

Step 5: Set Up Notifications with Webhooks

Do not rely solely on checking the dashboard — set up webhooks to get notified automatically when a check changes status.

  • Navigate to Webhooks in the sidebar.
  • Click Create Webhook.
  • Enter a destination URL where you want to receive notifications (for example, a Slack incoming webhook URL or a custom API endpoint).
  • Select which events to subscribe to — check.down, check.recovered, or all events.
  • Click Create Webhook to activate.
What next? Explore Relays if you need to monitor internal services, or Analytics to dive into performance trends and uptime data.

Need Help?

Cannot find what you are looking for? Our support team is here to help.