Statuspage is an established incident-communication product. Its own documentation directs teams to monitoring integrations, email automation, or its API for automated infrastructure updates. realuptime status combines the endpoint monitor and public page, and exposes four named regional readings on the page.
| Feature | realuptime status | Statuspage |
|---|---|---|
| Product focus | Endpoint monitoring plus a public status page | Incident communication across public, private, and audience-specific pages |
| Endpoint monitoring | Built in | Via monitoring integrations or API |
| Regional evidence | Four named region readings | Depends on the connected monitoring tool |
| Automatic incident updates | Built in for monitor transitions | Via integrations, email automation, or API |
| Free tier | 1 page, 3 monitors | Up to 2 public pages, 25 components, 100 subscribers |
| Free notification channels | Slack | Email, Slack, and Microsoft Teams |
| Subscriber notifications | Not available yet | 100 subscribers on Free; 250 on Hobby |
| Scheduled maintenance | Not available yet | Core feature on public-page plans |
| Team access | No team-member roles yet | 2 team members on Free; 5 on Hobby |
| REST API | Growth and Scale | Included on public-page plans |
| Entry paid plan | $29/mo Growth | $29/mo Hobby |
| Custom domain | Not available yet | Hobby plan and above |
Verified August 4, 2026. Sources: Atlassian Statuspage pricing, Atlassian Free plan details, Atlassian Statuspage integrations.
Statuspage runs no checks of its own — the page shows whatever an operator or a connected monitoring tool tells it. realuptime status is the monitor and the page in one product: every state a visitor sees is a measurement it took itself, shown as four named regional readings side by side instead of a single hand-set component. There is no second tool to wire up, and the page can never disagree with the monitoring behind it — it is the monitoring.