know when your service fails
Monitor websites and APIs from the regions you choose. Check the response you expect, including status codes and body text, with custom headers and authentication where needed.
An uptime monitor and status page in one.
Uptimepage is an uptime monitor for websites and APIs. Check availability from multiple regions, alert your team when something fails, and keep customers informed on a public status page. We run the monitoring service. Your team handles the fix.
free plan · no credit card · github, google or email
delivers via
- slack
- discord
- telegram
- mattermost
- teams
- pagerduty
- ntfy
- gotify
From a failed check to a customer update.
Keep the alert, incident history, and public status together so your team can focus on getting the service back.
page the person on-call
Send each monitor's alerts to the right Slack channel, PagerDuty service, email address, or webhook. Failure thresholds filter brief interruptions, and reminders keep an unresolved incident visible until someone acknowledges it.
keep customers informed
Publish live incidents and scheduled maintenance on a hosted status page with your logo and colours. Customers can follow updates and review the uptime history without signing in.
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.
thresholds, interval floors and failure rules per kind are in the monitor types reference.
For the team responsible when it breaks.
saas teams
keep customers in the loop
Monitor your application and APIs, alert the team, and publish progress on a customer status page while you work on recovery.
platform & sre
check beyond your own network
Compare availability and response times across regions. Bring monitoring into your deployment workflow through the API or Terraform provider.
operations
catch the quiet failures
Watch for missed jobs and expiring certificates or domains. A heartbeat monitor alerts you when a scheduled job stops checking in.
agencies
many clients, one login
Manage client monitors and give each client a branded status page. Share a single monitor when a client needs a closer look.
coming from another tool? compare with uptimerobot, pingdom, uptime kuma, statuspage or better stack.
Managed for your team. Open where it matters.
Use the hosted service and let Uptimepage run the monitoring stack. The source is public, so your team can verify how it works and keep a self-hosted path if your requirements change.
accountability
changes have an owner
Invite teammates with owner and member roles. Pauses, deletions and channel changes land in the audit log with the person who made them.
portability
your reliability data can leave
Export monitors and incidents as JSON. Public incidents stay available through RSS, with an API and Terraform provider for workflows your team owns.
no lock-in
leaving is a migration, not a rewrite
Read the public source, the system architecture, and the security policy. The API and Terraform provider are identical hosted or self-hosted.
Start free. Scale when your team does.
$0 with no expiry · paid tiers from $9, soon
no card to start · AGPL source · export or self-host any time
FAQ
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, cron-job heartbeat, TLS-certificate and domain expiry, and a browser login flow that signs in for real and charts how long each step takes. 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, Mattermost, Telegram, email, PagerDuty, ntfy, Pushover, Gotify, 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.
Put your first service on the monitor list.
Add your website or API, choose where alerts go, and publish your status page when you're ready. Start on the free plan with no credit card.