UptimePad setup guide
Set up the first useful alert quickly: monitors, SSL checks, DNS drift, alert routes, API access, status pages, and server monitoring.
Create the monitor
Add the URL, expected status code, and alert threshold. Free checks run every 5 minutes.
Turn on SSL and DNS
Track certificate expiry and the DNS records that should not drift during deploys.
Choose alert routes
Start with email, then add Slack, Discord, PagerDuty, webhooks, or push as your plan allows.
Publish a status page
Group public monitors into a basic status page that stays separate from the dashboard.
Monitors
Create HTTP, SSL, DNS, performance, and API monitors from the dashboard.
Notification channels
Configure Email, Slack, Discord, Teams, Telegram, PagerDuty, OpsGenie, Webhook, Prometheus, and Web Push.
API reference
Use API keys for monitor automation, reporting, and external integrations.
Server monitoring
Install the lightweight server reporter and link servers to monitors on Pro and Scale.
Cloudflare and blocked probes
If a monitor shows Cloudflare, bot protection, or a blocked probe response, allow UptimePad checks through your firewall or WAF rules. Keep the monitor target public, allow normal HEAD and GET checks, and avoid challenge pages for monitoring paths.
Support
Account, billing, import, and monitor setup questions belong in the dashboard support flow after sign-in. Include the monitor URL, expected status code, and the alert channel you were configuring so the first reply can be useful.
Security reports
Report suspected account access, notification abuse, exposed API keys, or probe-blocking regressions through the dashboard support flow. Do not include secrets in the first message.
API access for monitors and reporting
Pro and Scale teams can create API keys for monitor automation, reporting, imports, and incident workflows.
curl https://app.uptimepad.com/api/v1/monitors \
-H "Authorization: Bearer $UPTIMEPAD_API_KEY"