Skip to main content
This guide takes you from sign-up to a running monitor with alerts. It takes a few minutes.

​
1. Create your account

1

Sign up

Go to app.uptimeio.com and register with your full name, email address and a password of at least 8 characters.
2

Verify your email

Click the link in the verification email. You cannot create monitors until your email address is verified.

​
2. Create your first monitor

1

Start the wizard

Open Monitors in the sidebar and click Create Monitor.
2

Choose the type and target

HTTP is selected by default. Enter the URL, for example https://example.com. For another type (keyword, ping, port, DNS, heartbeat), open Monitoring something else?. Each type has its own guide, starting with HTTP.
3

Set the interval

Expand How often we check and use the Check Interval slider. The default is 5 minutes. The shortest interval is 5 minutes on Free and 1 minute on Pro and Scale. The longest is 24 hours.
4

Choose locations

In the same section, Monitoring Regions controls where checks run. Checks run from multiple probe locations. On Pro and Scale you can pick the locations; on Free UptimeIO chooses for you.
5

Pick who gets alerted

Select one or more notification destinations. If you have none yet, add one under Destinations in the sidebar (email, Slack, webhook, Telegram or Pushover). See Notifications.
6

Create the monitor

Click Create Monitor. The first check runs shortly afterwards and the results appear on the monitor’s page.

​
3. Test it

From the monitor’s page click Test Now to run a check immediately and see the response time, status and result per location.

​
How a failure becomes an incident

UptimeIO avoids false alarms by confirming failures from several locations before it opens an incident:
1

A check fails

A failed check does not open an incident by itself.
2

Retries from other locations

The check is repeated from other locations a second apart.
3

Confirmation

An incident opens only when several locations confirm the failure. You are then notified on the monitor’s destinations.
Recovery is confirmed the same way before the incident is resolved. See Understanding Incidents.

​
Common questions

Free 50, Pro 100, Scale 500. Paused monitors still count toward the limit. See Plans & Billing.
Yes. A paused monitor stops checking and does not alert. Resume it at any time; it is scheduled straight away.
Failures are already confirmed from several locations. You can also increase the Timeout or adjust the expected status codes in the monitor’s HTTP Configuration section.

​
Next steps

Monitor types

HTTP, keyword, ping, port, DNS and heartbeat

Notifications

Email, Slack, webhooks, Telegram and Pushover

Status pages

Publish a public status page

API reference

For developers: automate with the API