Getting started
Create your first uptime monitor
Add a website, confirm its first check, and configure how Statixoup decides that the service is healthy. Use the free trial, no credit card required to explore monitor checks, alert delivery, and public status pages. You can begin with one simple URL; this guide explains each setting in plain language so you know what Statixoup is checking and when it should alert you.
Monitoring purpose
Use an uptime monitor to automatically check whether a website or API is reachable and returning the response you expect. The monitor gives you a current health signal, response-time history, downtime records, and incident context so you can react before customers have to report the problem.
Monitor what customers depend on
Choose endpoints that represent real customer access, such as your homepage, app login page, API health endpoint, or checkout service.
Add your website
- 1.
Open Monitors
From the dashboard, select Monitors and choose Create Monitor.
- 2.
Enter the website URL
Provide the full HTTP or HTTPS URL, such as https://example.com, then select Add.
- 3.
Add authentication if requested
If the endpoint requires basic authentication, enter its username and password. For token-based auth, add a matching Authorization or custom header in advanced monitor settings.
Review the first result
Open the monitor to see current status, last check, availability, downtime, incidents, and response-time charts. Longer-period statistics become useful after enough checks are recorded.
Understand plan tokens
Statixoup uses plan tokens to measure usage and quota across free and paid plans. The free plan includes a starter token allowance, while paid plans increase that allowance and unlock more checks, integrations, and team access.
See the pricing guide
Read the pricing token guide to understand monthly token limits, plan upgrades, and usage monitoring.
Configure the check
- Set the check interval available to your plan and a timeout of at least 30 seconds.
- Choose GET, POST, PUT, DELETE, PATCH, or HEAD, then enter the expected HTTP status code.
- Add custom headers when the endpoint requires authentication or another request header.
- Set a failure threshold of at least two consecutive failures before an alert is triggered, and choose whether to send recovery notifications.
- Enable SSL verification to mark invalid or expired certificates as down; optionally enable a certificate-expiry alert.
Expected status matters
The monitor is operational only when its response meets the configured check rules. Use the status code that represents a healthy response for this endpoint.