Skip to main content

Uptime monitoring and a status page in one.

Uptimepage checks your websites and APIs every minute from several regions, alerts your team the second one goes down, and gives customers a live public status page. Free, open source, and running in about a minute.

sign in with github or google · no password · no email opt-in

https 41 ms tls ok · 62 d dns 18 ms https 122 ms dns 46 ms
🇺🇸 N. Virginia 🇫🇮 Helsinki 🇸🇬 Singapore more rolling out

delivers via

  • slack
  • discord
  • email
  • telegram
  • teams
  • pagerduty
  • ntfy
  • whatsapp

Monitoring, alerts, status page, incidents.

website & api monitoring

HTTP, TCP, DNS, ping. Custom headers, basic-auth, bearer tokens, response-code expectations, TLS verification. From a marketing website to an internal API.

page the person on-call

Slack, Discord, Telegram, WhatsApp, SMS, PagerDuty, email, webhook, and more. Per-monitor channels with dedupe and flap-suppress so a single failed check stays quiet, and reminders that repeat until someone acknowledges.

public status page

Brand colour + logo. 90-day timeline, live incidents, scheduled maintenance, RSS feed, JSON API, embeddable SVG badge. An open source status page you fully control.

incident timelines

Auto-opened on a down monitor, auto-closed on recovery. Add a public note your customers see in real time.

scheduled maintenance

Plan a window, the status page shows it ahead of time, the alert engine stays quiet during it. No false pages for planned work.

team members

Invite by email or GitHub handle. Role-based access: owners, members. Audit log of who changed what.

share one monitor, no login

Send a client or a vendor a link to a single monitor and they see the live dashboard, uptime, latency and incidents, with no account and nothing else of yours. Credentials, headers and tokens are redacted. Revoke or expire it whenever.

one token, every monitor

Store a value once and reference it as {{api_token}} from any monitor's headers or body. Rotate it in one place and every monitor picks it up on the next check. Secrets are sealed at rest, never read back to you, and refused in URLs where they would leak.

running while you sleep

Checks don't pause for nights, weekends, or holidays. Pro runs them every 60 seconds and keeps 90 days of history, so the 3am blip you slept through is still on the chart months later.

Eight ways to ask is it up.

One monitor list, eight kinds of check. Each one carries the same alerts, the same incidents, and the same status page.

  • up

    GET acme.com/health

    200 · 118 ms · eu-helsinki

    expect 200, body holds "ok". headers, auth, redirect rules.

    docs

    Reads the whole response. It checks status, headers and body text from every region you picked.

    read the http docs
  • up

    dial db.acme.com:5432

    connected · 24 ms

    the port answers. no payload sent, nothing to break.

    docs

    Anything with a port. Postgres, redis, smtp, game servers: if you can name the host and the port, you can monitor it.

    read the tcp docs
  • up

    A api.acme.com @1.1.1.1

    203.0.113.24 · matches

    answer checked against 203.0.113.x. resolving is not the same as resolving right.

    docs

    A wrong answer is an outage too. A hijacked or stale record pages you as fast as a dead resolver.

    read the dns docs
  • up

    icmp echo gw.acme.com

    rtt 12.4 ms

    for routers, gateways and hosts that open no port at all.

    docs

    Is the box even there? When ping answers but http fails, the host is up and the app broke.

    read the ping docs
  • up

    expect ping every 1h

    last 04:12 · on schedule

    grace 10 min. your cron calls us, silence is the alert.

    docs

    Backups fail quietly. The job reports in after each run; miss one report and we page you.

    read the heartbeat docs
  • up

    cert CN=acme.com

    41 days left

    warn at 30, down at 7. a failed renewal surfaces with time to spare.

    docs

    Nobody checks cert dates by hand. We read the days left off every handshake and page you while there is time to renew.

    read the tls docs
  • up

    rdap acme.com

    96 days left

    asked at the registry. an expired cert breaks https, an expired domain is gone.

    docs

    Companies have lost domains to one missed invoice. The rdap check asks the registry for the expiry date and nags you months ahead.

    read the domain docs
  • up

    login flow · 6 steps

    3.1 s · saw "Dashboard"

    a real browser signs in. catches the dead oauth secret a 200 hides.

    docs

    Login forms break more often than servers do. A real browser walks yours on schedule and pages you when a step dies.

    read the flow docs

thresholds, interval floors and failure rules per kind are in the monitor types reference.

Where it fits.

saas & sre

page on-call, one tool

Monitor production, page the on-call when it breaks, and give customers a status page, one tool, no second vendor.

indie hackers

a status page from day one

Ship a polished status page on day one, hosted free or self-hosted. No real-company invoice.

internal tools

watch every dependency

One open source uptime monitor for payment provider, mail sender, third-party API. Page when one wobbles.

agencies

many clients, one login

Give each client a branded status URL. 1 account, many pages.

coming from another tool? compare with uptimerobot, pingdom, uptime kuma, statuspage or better stack.

Free to start. Open source to keep.

$0 with no expiry · paid tiers from $9, soon

AGPL · self-host with no limits · no credit card

FAQ

Is it really free?
The Standard plan is $0 a month with no credit card. The first 1,000 accounts get the more generous founding plan and keep it for life. Pro and Team are paid and coming soon. Whatever plan you sign up on stays yours, and you can self-host the whole thing under AGPL for free.
Can I use my own domain for the status page?
Every org gets your-org.uptimepage.dev out of the box. A custom CNAME (status.yourcompany.com) is coming. Drop a line if you need it sooner.
What kinds of monitors are supported?
HTTP/HTTPS, TCP port, DNS lookup, ICMP ping. Per-monitor headers, basic-auth, bearer tokens, expected status code, content-match, TLS verification, follow-redirects rules.
Where do alerts come from?
Slack, Discord, Teams, Telegram, email, PagerDuty, ntfy, Pushover, WhatsApp, or any HTTPS webhook. Each monitor binds its own channels, so a marketing-site flap doesn’t page on-call.
Can I export my data?
Always. JSON export per monitor and incident. RSS for public incidents. SVG badges you can drop in a README.

in production

Zero to a public status page in one sitting. One tool, no second vendor.
Yerkebulan Rakhimov Founder, postmine.tech status page ↗

Try it on the site you already run.

Sign in, paste a URL, ship a public page in under 5 minutes.

start free