UptimeStatus
Know the moment something breaks.
Open-source uptime, SSL, DNS, and status-page monitoring — self-hosted, or fully managed by us.
Monitoring in four steps
New here? Start here — most teams have their first alert routed in a few minutes.
Create your account
Sign up free — 5 monitors, no card — or self-host the whole thing from the repo.
Quick start → 2Add your first monitor
Point a monitor at a URL, host, or port. Uptime, SSL, DNS and more each become a check.
Browse monitors → 3Route your alerts
Attach Email, SMS, Slack, Discord, Teams, PagerDuty and more — routed per monitor.
Notifications → 4Publish a status page
Give customers a page on your own domain that reflects your monitors in real time.
Status pages →Is it up?
Uptime
HTTP(S) checks with status code, latency, and keyword assertions — from multiple regions.
Reference →Ping
ICMP reachability for hosts that don't speak HTTP.
Reference →TCP port
Confirm a port accepts connections — databases, SMTP, custom services.
Reference →Cron & heartbeats
Watch scheduled jobs by expecting a ping on a cadence, and alert when one is overdue.
Reference →Health checks
Parse a JSON health endpoint and alert on degraded fields.
Reference →Certificates & DNS
SSL certificates
Expiry warnings at 30/14/7/1 days and fingerprint-change detection.
Reference →Domains
WHOIS-based domain-registration expiry warnings.
Reference →DNS records
Snapshot A, AAAA, MX, TXT, NS, CAA and alert on any change.
Reference →DNS blocklists
Watch your origin IP against public spam and abuse blocklists.
Reference →Fast and safe
Performance
Track response-time trends and catch slow regressions.
Reference →Lighthouse
Scheduled Lighthouse audits with performance-trend alerts.
Reference →Broken links
Crawl a site and report broken links and mixed content.
Reference →Port scan
Detect newly exposed ports on your servers.
Reference →Server metrics
Push CPU and RAM from your box and chart host telemetry.
Reference →AI checks
Describe an assertion in plain language; an AI check verifies it.
Reference →When things go wrong
Incidents
Failed checks open a timeline incident automatically — acknowledge and resolve.
Reference →Notifications
Ten channels, routed per monitor, with issue-vs-down severity.
Reference →Status pages
Public or access-controlled pages, custom domains, subscribers.
Reference →Maintenance
Schedule windows so planned work doesn't page you or dent your uptime.
Reference →Self-hosting & API
Deploy
Clone the MIT-licensed repo and run it on a single box behind a reverse proxy.
Deploy guide →Configuration
Env vars and config files for database, mail, notifications, and SSO.
Configure →Scaling & regions
Add regional check workers with the push-probe consensus model.
Scale →CLI
Operate everything from buddy — serve, migrate, queue, deploy.
API
A JSON API for monitors, incidents, and status — same-origin under /api.
API reference →