Quickstart

This guide takes you from an empty project to a monitored endpoint with alerts and a public status page. It takes about ten minutes.

1. Create a project

After signing in, StatusCheck asks for a project name. Projects are the unit of ownership in StatusCheck: monitors, channels, status pages, and billing all belong to a project, and you can invite as many teammates as you like to it.

2. Add an HTTP monitor

1. Go to Monitors → New monitor.
2. Choose HTTP and enter the URL you want to watch, for example https://api.example.com/health.
3. Pick a check interval. Every 60 seconds is a sensible default; paid plans go down to 30 seconds.
4. Choose the regions the check should run from. Start with three regions spread across continents. That is enough for StatusCheck to confirm a failure without paging you for one region’s network blip.
5. Leave Expected status at 2xx unless your endpoint deliberately returns something else.
6. Save.

The first results arrive within one interval. Open the monitor to see the response-time chart and the per-region timing waterfall (DNS → TCP → TLS → first byte → download).

Don’t want to point a monitor at your production endpoint yet?

Use https://example.com while you explore. It answers from every region and rarely goes down.

3. Connect an alert channel

1. Go to Channels → Add channel.
2. Choose Slack, authorize the workspace, and pick a channel such as #incidents.
3. Back on your monitor, open Alerting and select the Slack channel.

Email is enabled for every project member by default. SMS, phone calls, webhooks, PagerDuty, and Opsgenie are added the same way.

4. Test the alert

Temporarily change the monitor’s Expected status to 5xx and save. Within one or two check intervals, once at least two regions have seen the mismatch, StatusCheck opens an incident and posts to Slack. Change the expected status back, and the recovery notification follows the same path.

5. Publish a status page

1. Go to Status pages → New status page.
2. Give it a name and a subdomain, for example acme.statuscheck.io.
3. Add a component named “API” and attach the monitor you just created.
4. Publish.

Your page is live immediately. From the page settings you can add a custom domain such as status.acme.com, turn on subscriber notifications, and adjust branding.

Next steps

• Concepts explains regions, confirmation, and the status vocabulary.
• Heartbeat monitors watch cron jobs and background workers that can’t be probed from outside.
• On-call & escalation makes sure the right person is paged, and someone else if they don’t acknowledge.