What is an UpCanary status page?
Automated status pages that reflect your actual service health - no manual updates required.
A status page tells your users whether your product is working. Most status page tools require you to manually post updates when something goes wrong - UpCanary’s status pages update automatically based on your real monitor data.
How UpCanary Status Pages Work Differently
Traditional status pages are manually maintained. Someone has to notice the outage, log in, write an update, and post it - often 10–20 minutes after users are already affected.
UpCanary status pages are driven directly by your monitors. The moment a monitor detects downtime, the status page reflects it. No human action required.
- Automatic status updates - component health mirrors your live monitor state
- Real-time delivery - changes are pushed to visitors instantly via server-sent events, no page refresh needed
- Uptime history - visitors can see the reliability trend over the past 30, 60, or 90 days
- No credibility gap - your status page says what your monitors actually see
Visibility Modes
Every status page has one of three visibility settings:
| Mode | Who can access |
|---|---|
| Public | Anyone with the URL - no login required |
| Protected | Anyone who has your access key |
| Private | Only signed-in members of your team |
Public pages are ideal for customer-facing status. Protected pages work well for internal dashboards or beta users. Private pages are for internal operations visibility only.
See Visibility & Access Control for full details.
What Visitors See
A published status page shows visitors a clear picture of your service health:
- Overall status banner - a single headline like “All Systems Operational” or “Partial Outage”
- Component list - each monitor you’ve attached appears as a named component with its current status (Operational, Degraded, or Down)
- Uptime history - a visual history bar for each component showing availability over time
- Active incidents - any open incidents with their current status and timeline
- Third-party services - statuses of external dependencies like AWS, Stripe, or GitHub that you’ve subscribed to
Real-Time Updates
Visitors who have your status page open receive live updates without refreshing. When a monitor state changes, the status banner, component badge, and any affected incidents update immediately across all open browser tabs.
Pages in This Section
- Create a Status Page - get your first page live in minutes
- Customize & Brand - themes, layout blocks, and branding options
- Visibility & Access Control - public, protected, and private modes
- Components & Monitors - attach monitors and organize them
- Service Dependencies - show third-party service statuses
- Custom Domains - use your own domain like
status.yourcompany.com - Subscribers - let users subscribe to email updates
- Incidents - create and manage incident timelines