Uptime Monitor
The Uptime Monitor is the core of your monitoring strategy. It regularly checks if your website or API endpoint is accessible to your customers. We recommend setting up at least one Uptime Monitor for every publicly accessible page.
How it works
We send HTTP or HTTPS requests to your URL at the interval you choose (e.g., every 30 seconds or every minute). We consider the monitor "Online" if:
- The server responds (no timeout).
- The Status Code matches expectations (default
2xx, e.g., 200 OK).
If an error is detected, we verify it from multiple locations worldwide to avoid false alarms before sending a notification.
Create a website
Where is this in the UI?
In the dashboard, navigate to Websites and click New website / Create website.
Name
Choose a name that is easy to recognize for your team (e.g. "Marketing Website", "Shop API", "Customer Portal").
URL
Uptimeify automatically prepends https:// if you enter a plain hostname (e.g. example.com), so you don't need to type the protocol yourself — but you can always paste the full URL (e.g. https://example.com) as well.
Tips:
- Prefer the canonical target URL (usually
https://…). - If you want to verify HTTP→HTTPS behavior, also use the HTTPS Redirect monitor type.
Status
You can keep a website active or temporarily disable it (e.g. during migrations). A disabled website is not monitored.
Configuration
Basic Settings
- URL: The full address (e.g.,
https://example.com). - Check Interval: How often to check (e.g., 60s).
Advanced Settings
- Expected Status Codes: By default, we check for
200-299. You can adjust this, e.g., to200,301,302if redirects should be considered a success. - Timeout: Maximum time to wait for a response (Default: 30s).
- HTTP Method: Default is
GET. You can also chooseHEAD,POST, etc. - Request Body & Headers: Send JSON data or authentication tokens (e.g.,
Authorization: Bearer ...).
Optional checks
When configuring an Uptime Monitor, you can enable additional checks alongside the basic availability test:
- SSL: Monitor certificate validity and expiration date → see SSL Monitor
- Response Time: Set performance thresholds and get alerted when your site slows down (see Response Time below)
- Keyword / Content Validation: Verify that specific content is present in the response body
- Page Size: Alert on unexpected size changes that may indicate missing resources or bloat
Common pitfalls
URL vs. hostname (DNS/ICMP)
The Uptime Monitor accepts a plain hostname (Uptimeify adds https:// automatically) or a full URL. Some other monitor types work with a hostname without protocol and do not perform HTTP requests.
- DNS Monitor: hostname without protocol (e.g.
example.com) → see DNS Monitor - ICMP Monitor: hostname without protocol (e.g.
server.example.com) → see ICMP Monitor
Authentication / bot protection
If your site uses Basic Auth, token auth, or bot protection, a simple HTTP check may fail.
- Configure auth headers or Basic Auth credentials in the Request Headers field.
- For complex login flows, Playwright monitors are often the more robust choice.
Response Time
In addition to status, we also record the response time (Time to First Byte + Download).
- You can configure alerts if the response time exceeds a threshold (e.g., > 2000ms), even if the status is 200 OK.
Next steps
- Investigate outages and view history: Incidents
Monitoring Types
Uptimeify supports a wide range of monitor types — from HTTP uptime, keyword, and SSL checks to DNS, network services, and synthetic browser flows. Pick the type that matches what you need to watch.
SSL Monitor
Expired SSL certificates are a common cause of downtime and loss of user trust. Browsers display warnings like \"Connection not secure\". Our SSL Monitor helps you proactively prevent this.