Status page app that updates itself when something breaks
UptimePilot publishes a branded status page for your product, fed directly by the monitors that already watch it. When a check confirms an outage, the affected component changes state, your team posts an update in a few clicks, and subscribers get the news by email instead of opening a ticket.
What a status page does for your team
During an incident, the same question arrives through every channel at once. Is it down, is it just me, when will it be back. Each answer costs an engineer or a support person several minutes, at exactly the moment they are needed on the fix.
A status page answers that question once, in public, for everyone. Customers check one address, see which part of the service is affected, read the latest update and decide what to do. Support links to it in every reply. Account managers send it to large clients. The team keeps working.
- Fewer "is it down?" tickets and chat messages while an incident is open
- One place that states what is affected and what is not
- A written record of incidents and maintenance that customers can read later
- A credible signal of transparency in enterprise security reviews and vendor questionnaires
Status page app built on real monitoring data
Many status pages are updated by hand, which means they show "All systems operational" until someone remembers to change them. In UptimePilot, every component on the page can be linked to one or more monitors. When a linked monitor is confirmed down from a second region, the component switches to an outage state automatically. When the checks pass again, it returns to operational, and your incident update closes the story.
- Components that mirror your product, such as Website, API, Dashboard, Checkout, Email delivery
- Component status driven by HTTP, keyword, API, ping, TCP port and heartbeat monitors
- Incident updates with states (investigating, identified, monitoring, resolved) and timestamps
- Scheduled maintenance announced in advance, with start and end times shown in the visitor's timezone
- Subscriber email updates, so customers opt in once and hear about new incidents and maintenance automatically
- Your logo, your brand colors and a clean layout that reads well on a phone
- A custom domain such as status.yourcompany.com on Team and higher plans
- Password protection for internal or client-only pages on Business and higher plans
App status page or system status page, the same tool
A public app status page tells customers how the product is doing. A system status page for internal use tells employees whether the VPN, the intranet, the build server or the mail relay is healthy. Both use the same components, the same monitors and the same incident editor. Protect the internal one with a password, keep the public one open, and run them side by side from one account.
How the status page works on UptimePilot
- 01 Add monitors for the things customers depend on. Most teams start with the homepage, the login page, the main API endpoint and a synthetic monitoring check for the signup or checkout path.
- 02 Create a status page and add components. Give each component a name your customers recognize, not an internal hostname.
- 03 Link monitors to components. One component can depend on several monitors, so "API" can turn red if either the US East or the EU Central endpoint fails confirmation.
- 04 Set the look. Upload a logo, pick colors, choose which components are visible, and point your custom domain with a single CNAME record.
- 05 Turn on subscriptions. Visitors enter an email address and confirm it, then receive incident and maintenance updates.
When an outage happens, the alert reaches the on-call person through email, SMS, Slack, Microsoft Teams or webhook, with escalation if nobody acknowledges it. The same person opens the incident on the status page, writes a short first update and keeps it current until resolution.
Writing incident updates people trust
The first update matters most, and it should go out within minutes, even if it only says what is affected and that the team is investigating. After that, a steady rhythm works better than long silences: an update every 30 minutes during a major incident is a reasonable default, even when there is nothing new. Name the impact in customer terms (logins fail, checkout returns an error, emails are delayed), avoid internal jargon, and give a time for the next update. Our guide to status page best practices covers wording, cadence and post-incident summaries in detail.
Status page hosting and custom domains
Your status page is served separately from your own infrastructure, which is the point: if your servers are down, the page that explains it is still up. A custom domain needs one CNAME record at your DNS provider. Once it resolves, UptimePilot issues and renews the TLS certificate for that hostname, so visitors see a valid padlock on status.yourcompany.com without any certificate work on your side.
Uptime history on the page is calculated from the same check results that feed your uptime reports. A 90 day bar per component shows days with incidents at a glance. Scheduled maintenance windows are excluded from alerting and can be shown as maintenance on the page, so planned work does not look like an outage.
Who sees what
Public pages are open to anyone with the link. Password protected pages, on Business and Enterprise, suit client portals for agencies, internal IT pages and partner pages for B2B customers. Only team members with the right role can publish incidents, so a support agent can post updates without being able to delete monitors.
Which plan fits your status page
| Plan | Status pages | Branding and access | Price billed yearly |
|---|---|---|---|
| Starter | 1 | Logo, colors, components, subscribers | $24 per month ($288 per year) |
| Team | 5 | Adds custom domain | $49 per month ($588 per year) |
| Business | 20 | Adds password protection and removes UptimePilot branding | $124 per month ($1,488 per year) |
| Enterprise | 50 | Custom domain and password protection, SSO (SAML) for your team | $299 per month ($3,588 per year) |
Monthly billing is $49, $99, $249 and $599. Every plan includes all check types, multi-region confirmation, email, Slack, Microsoft Teams and webhook alerts, maintenance windows and escalation. Agencies that publish a page per client usually choose Business, which makes each page a white label status page on the client's domain. See the full comparison on pricing, or compare list prices with the Atlassian Statuspage alternative breakdown.
01
Can the status page update automatically?
Yes. Each component can be linked to monitors. When a linked monitor is confirmed down from a second region, the component shows an outage without anyone touching the page. You still write the incident updates yourself, because customers want a human explanation, not just a red dot.
02
Can I use my own domain for the status page?
Yes, on Team, Business and Enterprise. Add a CNAME record such as status.yourcompany.com, and UptimePilot provides the TLS certificate for it automatically.
03
Can I make a private status page?
Yes. Password protected status pages are included on Business and Enterprise. They suit internal system status pages, client-only pages for agencies and partner pages.
04
How do customers subscribe to updates?
Visitors enter an email address on the status page and confirm it. From then on they receive an email when an incident is opened, updated or resolved, and when maintenance is scheduled.
05
Does scheduled maintenance trigger alerts?
No. During a maintenance window, monitors linked to the affected components keep checking but do not send alerts, and the status page shows the planned work instead of an outage.
06
How many status pages do I get?
Starter includes 1 status page, Team 5, Business 20 and Enterprise 50. Every plan includes components, incident updates, scheduled maintenance and subscriber emails.
Publish a status page your customers can rely on
Connect your monitors, add your components and point your domain. The next time something breaks, your customers find the answer before they write to support.