Quick Start

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

1. Create your account

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

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

Start the wizard

Open Monitors in the sidebar and click Create Monitor.

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.

Set the interval

Choose how often to check. 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.

Choose locations

Checks run from multiple probe locations. On Pro and Scale you can pick the locations for regular checks; on Free UptimeIO chooses for you.

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.

Create the monitor

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

Or create it with the API

Create a read_write API key in Settings > API Keys (details), then:

curl -X POST https://api.uptimeio.com/api/monitors \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "My Website",
    "type": "HTTP",
    "target": "https://example.com",
    "interval_seconds": 300,
    "monitoring_regions": [],
    "http_config": { "method": "GET", "expected_status_codes": [200] }
  }'

"monitoring_regions": [] lets UptimeIO choose locations automatically. See Create a monitor for every field.

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:

A check fails

A failed check does not open an incident by itself.

Retries from other locations

The check is repeated from other locations a second apart.

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

How many monitors can I create?

Free 50, Pro 100, Scale 500. Paused monitors still count toward the limit. See Plans & Billing.

Can I pause a monitor?

Yes. A paused monitor stops checking and does not alert. Resume it at any time; it is scheduled straight away.

How do I reduce false positives?

Failures are already confirmed from several locations. You can also increase the timeout or adjust the expected status codes for your endpoint.

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

Automate everything

Getting Started

Monitor Types

Essentials

Notifications

Integrations

Status Pages

Account & Team

Plans & Billing

1. Create your account

2. Create your first monitor

Or create it with the API

3. Test it

How a failure becomes an incident

Common questions

Next steps

Monitor types

Notifications

Status pages

API reference

​1. Create your account

​2. Create your first monitor

​Or create it with the API

​3. Test it

​How a failure becomes an incident

​Common questions

​Next steps

Monitor types

Notifications

Status pages

API reference

1. Create your account

2. Create your first monitor

Or create it with the API

3. Test it

How a failure becomes an incident

Common questions

Next steps