Everything you need to know about configuring and using Uptime Monitor.
Uptime Monitor is a monitoring platform that tracks the availability and performance of your websites, APIs, servers, and services. It supports 9 different monitor types and 9+ notification channels.
Monitors web pages and API endpoints. Supports GET, POST, PUT, DELETE methods. Configure custom headers, request body, expected status codes, and authentication (Basic Auth or Bearer Token).
Sends ICMP echo requests to check if a host is reachable. Useful for monitoring server availability at the network level.
Tests TCP connectivity on a specific port. Great for monitoring databases (3306), mail servers (25/587), FTP (21), SSH (22), and custom services.
Fetches a URL and checks if specific text is present (or absent). Use this to detect content changes, error messages, or verify critical page content.
Provides a unique URL endpoint that your cron jobs or services should ping at regular intervals. If a ping is missed within the expected window, an alert is triggered.
# Example cron job that pings every 5 minutes
*/5 * * * * curl -s https://your-server.com/api/heartbeat/YOUR_TOKENMonitors SSL/TLS certificate validity and expiration. Get alerts days before your certificate expires.
Validates DNS records (A, AAAA, CNAME, MX, TXT, NS). Alerts when records change unexpectedly.
Checks domain registration expiration dates via WHOIS. Get early warnings before your domain lapses.
Takes a hash of page content and alerts when the content changes. Useful for detecting defacements, unexpected edits, or content updates.
To create a new monitor:
The monitor will start checking immediately and appear on your dashboard.
Heartbeat monitors use a "push" model. Instead of Uptime Monitor checking a service, your service pings Uptime Monitor at regular intervals.
# Ping via curl
curl -s https://your-server.com/api/heartbeat/abc123
# Ping via wget
wget -q -O /dev/null https://your-server.com/api/heartbeat/abc123Both GET and POST requests are supported. If no ping is received within the expected interval, an incident is created and notifications are sent.
Uptime Monitor supports the following notification channels:
| Channel | Configuration Required |
|---|---|
| Email (SMTP) | SMTP server, port, username, password, recipient |
| Slack | Webhook URL |
| Discord | Webhook URL |
| Telegram | Bot token, Chat ID |
| Microsoft Teams | Webhook URL |
| Google Chat | Webhook URL |
| PagerDuty | Integration key |
| Webhook | URL, method, headers |
| Zoho Desk | OAuth credentials, department ID |
Each monitor can be linked to multiple channels. Manage channels in Settings > Notification Channels.
1. Go to your Slack workspace settings > Apps > Incoming Webhooks
2. Create a new webhook and select the target channel
3. Copy the webhook URL into the Slack channel configuration
1. Open Discord channel settings > Integrations > Webhooks
2. Create a new webhook
3. Copy the webhook URL into the Discord channel configuration
1. Message @BotFather on Telegram to create a bot
2. Get the bot token
3. Get your chat ID (message @userinfobot)
4. Enter both in the Telegram channel configuration
Configure a custom HTTP webhook with your URL, method, and headers. The payload includes monitor name, status, response time, and incident details in JSON format.
Each account gets a unique public status page URL at /status/YOUR_USER_ID. The status page displays:
Configure your status page in Settings > Status Page. You can set a custom title, description, and optionally protect it with a password.
Incidents are automatically created when a monitor goes down. You can:
Incidents are automatically resolved when the monitor recovers. The full timeline is visible on the status page and in the settings panel.
Schedule maintenance periods to:
Create maintenance windows in Settings > Maintenance. Set the start time, end time, and add an optional description.
Access built-in tools at /tools:
Analyze SSL/TLS certificates: issuer, validity dates, protocol version, cipher suite, and certificate chain.
Query DNS records for any domain. Supports A, AAAA, CNAME, MX, TXT, NS, and SOA record types.
Check HTTP security headers: Content-Security-Policy, X-Frame-Options, Strict-Transport-Security, X-Content-Type-Options, and more.
The API uses token-based authentication. Include the token in the Authorization header:
Authorization: Bearer YOUR_TOKENDisplay live uptime status and response time badges on your README, documentation, or website. Two badge endpoints are available for each monitor.
<img src="https://yourdomain.com/api/badge/MONITOR_ID" alt="Uptime">
<img src="https://yourdomain.com/api/badge/MONITOR_ID/response" alt="Response Time">| Parameter | Description | Example |
|---|---|---|
?label= | Custom left-side label text | ?label=My%20API |
?theme=dark | Dark background variant | ?theme=dark |
Badges are rendered as SVG images and cached for 60 seconds. They update automatically as monitor status changes.
Synthetic monitoring executes multi-step API checks in sequence, simulating real user workflows. Each step can make an HTTP request, validate the response, and extract variables for use in subsequent steps.
Each step in a synthetic monitor defines:
Add assertions to validate each step's response:
If any assertion fails, the entire synthetic check is marked as failed and alerts are triggered.
Extract values from a step's JSON response and reference them in later steps using {{variableName}} syntax:
Step 1: POST /api/auth/login → extract "token" from response
Step 2: GET /api/data with header Authorization: Bearer {{token}}Synthetic monitors run automatically every 5 minutes via cron. Each run executes all steps in order and records pass/fail status plus total execution time.
Track detailed performance metrics for your API endpoints beyond simple uptime.
Click on any HTTP monitor to expand its detail panel. Switch to the Metrics tab to see P95/P99 latency charts, error rate trends, and status code distribution over time.
Automated weekly summaries are emailed every Monday at 9:00 AM IST to your registered email address.
Admin users can generate a report on demand from Settings → Reports → Send Weekly Report Now. The report is generated and delivered to your email within a few minutes.
Fine-tune when and how you receive alert notifications with advanced rules.
Prevent alert flooding by setting a cooldown period (default: 5 minutes). After an alert fires, duplicate alerts for the same monitor are suppressed during the cooldown window. Recovery notifications are always sent.
Restrict notifications to specific days and hours:
Toggle per monitor whether a recovery notification is sent when the service comes back online. Enabled by default.
Collaborate with your team by inviting members, assigning roles, and managing access.
Go to Settings → Team → Invite Member. Enter the person's email and select a role. They receive an email invitation with a link to accept and join your workspace.
| Role | Permissions |
|---|---|
| Admin | Full access: monitors, channels, team, billing, settings |
| User | Create/edit monitors and channels. Cannot manage team or billing |
| Viewer | Read-only access to dashboard, status pages, and reports |
Free: 1 seat, Solo: 1, Team: 5, Enterprise: unlimited. Upgrade your plan or contact support for additional seats.
Export your monitoring data as CSV files for offline analysis, compliance, or reporting.
Exported CSV files contain: timestamp, status (up/down), response time (ms), status code, error message (if any), and monitoring location.
Uptime Monitor is a fully installable Progressive Web App. Use it like a native app on desktop and mobile.
The PWA caches essential assets for offline access. You can view your dashboard, recent monitor data, and status pages even without an internet connection. Data syncs automatically when connectivity is restored.