Answer “is it down?” before support does.
One outage becomes a pile of duplicate tickets. A branded page on your own domain answers everyone at once and emails the people who subscribed.
Your domain, your brand, no watermark.
Point a CNAME at UptimeStatus, set the custom domain on the page, and status.yourcompany.com serves it. Your logo and accent color come from the page settings, and there is no "powered by" badge in the footer, on any plan. Competitors sell that back to you as an upgrade.
Each page also declares its own language, so a German status page reads as German to screen readers and search engines. Free includes 1 status page, Pro includes 10, and a self-hosted install includes as many as you want.
Public for customers, gated for everyone else.
Not every status page belongs on the open internet. A page for internal tooling, or an SLA page for one large customer, needs a lock on it. Each page picks its own access mode: public, password protected, restricted to email domains, or restricted to IP ranges.
Password entry happens right on the page, no accounts required. And because access is a per-page setting, the same team can run a public page and a locked one side by side.
What ships on every status page.
- Component groups organize monitors into named sections like API, Web, or Database. Grouping is opt-in per page, and ungrouped monitors still render.
- 90 days of uptime bars per monitor, computed from the same stored check results the dashboard uses. Nothing hand-tuned, nothing invented.
- Email subscribers visitors leave an email and get notified when an incident opens. Every email carries a one-click unsubscribe link.
- RSS incident feed every page serves its incident history at /status/your-slug/feed, ready for feed readers and internal tooling.
- Status report updates post announcements to the page without opening an incident. Subscribers get emailed on each update.
- Maintenance banners scheduled maintenance windows render as planned work, not as an outage, so deploys never look like downtime.
Leaving another provider takes one request.
Already on Atlassian Statuspage, Instatus, or Better Stack? Point the importer at your existing page and it recreates the title and every component as monitors on a new page you own.
One honest caveat: those providers do not expose a per-component check target, so imported monitors start disabled with a placeholder URL. You re-point each at a real endpoint, enable it, and the migration is done. No re-typing forty component names.
curl -X POST https://uptime-status.org/api/status-pages/import \ -H 'Content-Type: application/json' \ -d '{ "provider": "statuspage", "source_url": "https://acme.statuspage.io", "team_id": 1 }'
Subscribers keep themselves in the loop.
A subscribe form sits on the page itself. When an incident opens or you post an announcement, subscribers get an email with a one-click unsubscribe link. Prefer machines over inboxes? Every page also serves its incident history as an RSS feed.
Status pages, answered.
How do I put the page on my own domain?
Point a CNAME like status.yourcompany.com at the app and set the custom domain on the page. Visitors see your title, your logo, and your accent color, with no vendor watermark on any plan.
Can I keep a status page private?
Yes. Beyond fully public, a page can require a password, restrict viewers to specific email domains, or restrict access by IP range. The email-domain option checks the address a visitor enters rather than verifying mailbox ownership, so treat it as a soft gate and reach for the password or IP options when it really matters.
How do subscribers get notified?
A subscribe form sits on the page itself. When an incident opens, or when you post a status report update, subscribers get an email. Every email includes a one-click unsubscribe link tied to an unguessable token.
Can I import my existing status page?
Yes, from Atlassian Statuspage, Instatus, or Better Stack. One request snapshots the source page and recreates its components as monitors on a new page. Imported monitors start disabled with a placeholder URL, because those providers do not expose a per-component check target, so you re-point each at a real endpoint and enable it when ready.
What do the uptime bars show?
90 days of history per monitor, computed from the check results your monitors actually recorded. The page and the dashboard read the same data, so the numbers always agree.
Pairs well with.
Uptime monitoring
The checks behind the page: 30-second Pro intervals from six regions, with full diagnostics on every failure.
Learn moreIncident management
Failed checks open incidents automatically, and the timeline you build lands on this page.
Learn moreNotifications
Email, Slack, PagerDuty, and seven more channels tell your team before the status page tells your users.
Learn moreStart monitoring in under 2 minutes.
No credit card required for the self-hosted, open-source version.