Skip to main content
This guide walks you through creating a monitor from start to finish with practical examples.

​
Before You Start

Make sure you have:
  • ✅ Created your UptimeIO account
  • ✅ Verified your email address
  • ✅ Created an organization
If you haven’t done these yet, see the Quick Start Guide.

​
Creating an HTTP Monitor

The most common monitor type for websites and APIs.
1

Navigate to Monitors

From your dashboard, click “Monitors” in the sidebar, then click ”+ New Monitor”.
2

Choose Monitor Type

Select “HTTP/HTTPS” from the monitor type options.
UptimeIO automatically detects HTTP vs HTTPS from your URL.
3

Enter Basic Details

Fill in the required fields:
Name: My Website
URL: https://example.com
Name: A descriptive name you’ll see in your dashboard URL: The full URL including https://
4

Set Check Interval

Use the slider to set how often to check:
  • Free plan: Minimum 5 minutes
  • Solo plans: Minimum 60 seconds (1 minute)
  • Team/Organization plans: Minimum 30 seconds
  • Paid plans: Minimum 60 seconds (1 minute)
  • Enterprise: Minimum 30 seconds
Start with 5 minutes for non-critical sites, 60 seconds for important services.
5

Configure Timeout

Set how long to wait for a response:
Timeout: 30 seconds (default)
  • Fast sites: 10-15 seconds
  • Standard: 30 seconds
  • Slow sites: 45-60 seconds
6

Select Regions

Choose monitoring regions:Auto (Recommended for beginners):
  • UptimeIO selects 2 regions automatically
  • Balanced load distribution
  • No configuration needed
Manual:
  • Select specific regions (Asia, Europe, North America, etc.)
  • Requires at least 2 regions
  • Best for targeting specific geographic areas
Use “Auto” unless you have specific regional requirements.
7

Add Notification Profile

Select or create a notification profile:Option 1: Use existing profile
  • Select “Team Notification Profile” (created automatically)
Option 2: Create new profile
  • Click “Create New Profile”
  • Name it (e.g., “Website Alerts”)
  • Add your email address
  • Click “Create”
8

Create Monitor

Click “Create Monitor” at the bottom.
You’ll see a success message and be redirected to the monitor details page.
9

Wait for First Check

Your first check will run within 30-60 seconds. You’ll see:
  • ✅ Current status (Up/Down)
  • 📊 Response time
  • 🌍 Region checked from
  • ⏱️ Next check time

​
Example Configurations

​
Simple Website

Name: Company Homepage
URL: https://example.com
Type: HTTP/HTTPS
Interval: 5 minutes
Timeout: 30 seconds
Regions: Auto

​
API Endpoint

Name: Production API
URL: https://api.example.com/health
Type: HTTP/HTTPS
Interval: 60 seconds
Timeout: 10 seconds
Regions: us-east, europe, asia

​
E-commerce Checkout

Name: Checkout Page
URL: https://shop.example.com/checkout
Type: HTTP/HTTPS
Interval: 60 seconds
Timeout: 45 seconds
Regions: Auto

​
Advanced Options

Default is GET, but you can choose:
  • HEAD: Faster, doesn’t download body
  • POST: For APIs that require POST
  • PUT, PATCH, DELETE: For specific API endpoints
Method: GET (default)
Default accepts 2xx and 3xx codes.
Expected Status Codes: 200-299, 300-399
Change if your endpoint returns different codes:
Expected Status Codes: 200, 201, 204
Add custom headers for authentication or content negotiation:
Headers:
  Authorization: Bearer your-token
  Content-Type: application/json
Enable to follow up to 5 redirects:
Follow Redirects: Yes (default)
Max Redirects: 5
Disable if you want to detect unexpected redirects.
For password-protected endpoints:
Auth Type: Basic
Username: monitor-user
Password: your-password
Supports Basic and Digest authentication.

​
Testing Your Monitor

After creating a monitor, test it immediately:
1

Click Test Now

On the monitor details page, click “Test Now” button.
2

View Results

Results appear in seconds showing:
  • ✅ Success or ❌ Failure
  • Response time
  • Status code
  • Region tested from
3

Verify Configuration

If test fails:
  • Check URL is correct
  • Verify expected status codes
  • Increase timeout if needed
  • Check authentication credentials

​
Common Issues

Possible causes:
  • Timeout too short
  • Firewall blocking UptimeIO
  • Expected status codes don’t match
  • SSL certificate issues
Solutions:
  1. Increase timeout to 30-45 seconds
  2. Check expected status codes
  3. Verify SSL certificate is valid
  4. Whitelist UptimeIO if using firewall
Cause: You’ve reached your plan’s monitor limit.Solutions:
  • Delete unused monitors
  • Pause monitors you don’t need right now
  • Upgrade to a higher plan
Cause: Manual tests use different logic than scheduled checks.Solutions:
  • Wait for scheduled checks to run
  • Check incident details for specific errors
  • Verify multi-region consensus (3 failures from 2+ regions)

​
Next Steps

Understanding Incidents

Learn how incidents are created and resolved

Setting Up Alerts

Configure notifications for your monitors

Monitor Types

Explore all monitor types

Reading Metrics

Understand uptime and performance metrics