Monitoring
Learn how UptimeObserver monitors your websites, APIs, and services around the clock, ensuring you're the first to know when something goes wrong.
How Monitoring Works
-
Check Frequency
Configure how often your endpoints are checked—from every 30-seconds to custom intervals. Choose the frequency that matches your service's criticality.
-
Global Monitoring Locations
Choose monitoring regions across Europe and North America. The bot's region and IP table is the authoritative reference for available regions and firewall addresses.
Paid plans support selecting up to 3 additional regions for redundancy. Free is limited to 1 region.
-
Response Time Tracking
Track response times over time and identify performance degradation before it affects your users.
-
Instant Alerts
Get notified immediately when issues are detected via your preferred integrations.
Monitor Types
UptimeObserver supports different types of monitoring to match your needs:
| Type | Description | Use Case |
|---|---|---|
| HTTP(S) | Checks website availability, HTTP response codes, and SSL certificates | Websites, REST APIs, web applications |
| DNS | Monitors DNS records and validates expected values | Domain configuration, DNS propagation, failover verification |
| Port | Checks whether a connection to a public TCP port succeeds | Web servers, mail servers, custom TCP services |
| Ping | Host reachability and network latency | Verify example.com responds to ICMP echo requests |
| Heartbeat | Receives pings from your cron jobs and scheduled tasks; alerts if not received on schedule | Backup scripts, nightly data pipelines, scheduled maintenance tasks |
Setting Up Your First Monitor
Creating a monitor in UptimeObserver takes just a few steps:
- Log in to your UptimeObserver dashboard
- Navigate to Monitors under monitoring
- Click "New Monitor" and select your monitor type
- Configure your endpoint and alert settings
- Click Create Monitor, wait for a check result (or send the first heartbeat), then add Down and Up alerts
See the complete guide to creating a monitor
Understand Retry, Down incidents, and recovery
Understanding the UptimeObserver Bot
The UptimeObserver Bot checks your sites from our servers. HTTP checks are signed automatically using Web Bot Auth, with no setup required. If your site blocks checks, use the guides below to allow monitoring requests.
-
Bot Identification
Find monitoring IPs and learn how to recognize requests from UptimeObserver in your logs.
-
Firewall Configuration
UptimeObserver is a Cloudflare verified bot. If your WAF still blocks monitoring requests, identify the blocking feature and configure an exception.
Best Practices
Monitoring Tips
- Start with critical endpoints : Monitor your most important pages first (homepage, login, checkout, API endpoints)
- Use appropriate intervals : Critical services may need 1-minute checks; less critical can use 5-15 minutes
- Set up multiple alert channels : Use email + Slack/SMS for redundancy
- Monitor from user perspective : Check the URLs your customers actually use
- Use the right monitor type : HTTP for web services, DNS for domain records, Port for public ports, Ping for host reachability, and Heartbeat for cron jobs and scheduled tasks.
Need Help?
If you need assistance setting up monitoring, reach out using the "Need Help?" button on the bottom right corner or email us at support@uptimeobserver.com.