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
Your sites are monitored from multiple regions across Europe for comprehensive coverage and accurate uptime data. More regions are coming soon.
-
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 if a specific public port is open and responding | web servers, mail servers, custom services |
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
- Save and start monitoring
See the complete guide to creating a monitor
Understanding the UptimeObserver Bot
The UptimeObserver Bot performs all monitoring checks from our servers. When troubleshooting issues or configuring firewalls, you may need to identify or whitelist our bot.
-
Bot Identification
Learn about our User-Agent string and IP addresses used for monitoring requests.
-
Firewall Configuration
If you use Cloudflare or other WAF solutions, whitelist our bot for accurate monitoring.
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.
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.