Status Pages
Turn any HTTP uptime check into a public status page for your users with one click.
Public status pages:
Having a public status page gives your users confidence that your team cares about reliability, and lowers the support burden when outages inevitably do occur.
With HeyOnCall you can now, with one click, turn any HTTP/HTTPS uptime check into a public status page for your website or API. The transition from up to down (and back to up) happens automatically as we monitor your site, so there is no need to manually update your status page.
Integrated monitoring and on‑call:
We go beyond public status pages. We also create incidents when something looks off beyond your configured failure thresholds and timeouts, and page the right people via loud critical alerts to our iOS and Android apps, post the incident to your Slack channel, and keep alerting and escalating until someone on your team acknowledges.
TLDR:
Built for small engineering teams and solo founders, HeyOnCall pairs website monitoring and status pages with on‑call alerting in one product for superior reliability and simplicity. Get impossible‑to‑ignore critical alerts that bypass Do Not Disturb, plus Slack, email, webhooks, and more. Give your users confidence with public status pages that are aligned with your monitoring and alerting strategy.
Status Pages: HeyOnCall vs. Alternatives
| Differentiator |
HeyOnCall
|
Alternatives |
|---|---|---|
| Status pages | Public, hosted webpage updated automatically from our monitoring data. | Varies, but similar. Some require manual updates. |
| Monitoring | Configurable HTTPS probes with assertions that go beyond the URL: response headers, HTTP status codes, redirects, etc. | URL-only 200 OK checks. |
| Alerting | iOS/Android “Critical Alerts” bypass Do Not Disturb and volume/mute settings. Repeat until acknowledged. Will wake you up! | No mobile app. No critical alerts. Emails or Slack alerts are easy to miss for hours. |
| On‑call | Integrated on-call rotation schedules and escalations. | Separate products for monitoring and on-call: requires integration glue between them, so there are more moving parts to fail during an outage. |
| Mobile apps | Lightweight mobile apps for iOS and Android. Designed to reliably deliver alerts and let you quickly acknowledge the incident. | ¯\_(ツ)_/¯ |
| Business hours schedules | Defer important-but-not-urgent alerts (like maintenance or non‑urgent incidents) until your preferred weekdays and hours. | No differentiation between urgent and non-urgent alerts. Burns out your on-call team waking them up for things that can wait until the morning. |
| Silencing | Quick silence with selectable timeout at the trigger, service, or organization-wide level. Ensures you don’t keep getting alerts while you’re fixing the issue, and ensures you don’t inadvertently stay silenced forever. | Mute one monitor at a time. Forget to unmute after the incident is over, so you miss the next incident. |
| False positives (noisy alerts) |
Customer-level: False positives are reduced to your preferences via customizable consecutive-failure thresholds / timeouts. Platform-level: False positives are reduced through continuous control group self-checks, extensively tested codebase, and code paths designed to differentiate our network incidents from yours. |
¯\_(ツ)_/¯ |
| False negatives (missed alerts / blind spots) |
Customer-level: Missed alerts are reduced via: alerts repeat until acknowledged; configurable multiple delivery channels per user; configurable multi-level escalations. Blind spots are reduced via configurable assertion rules on HTTP response headers, etc. Platform-level: False negatives are reduced via extensive CI test suite, continuous production self‑checks, and external monitoring. |
Customer-specific glue (webhook integration) between separate monitoring product and on-call product fails silently (webhooks/auth headers/network issues), resulting in missed alerts right when you need them. |
| Pricing | Simple, flat $/month pricing. Free tier forever. | Annoying $/user/month or $/monitor/month. |
Status Pages FAQ
What is a public status page?
A public status page is a webpage that is hosted outside of your infrastructure and displays the current status and recent history of your product’s uptime and availability.
Why do I need a public status page?
Outages happen, no company is perfect, and even if you do everything right, the universe sometimes just conspires against you. A huge part of keeping your users happy is being open and upfront about when downtime occurs, and letting them know that you are on the case and working to remediate.
What are the benefits of having a public status page when my site is up?
By merely having the “up” status page linked from your website, you let your users know that you take uptime and reliability seriously. This signals that they can depend on your product to be available when they need it.
What are the benefits of having a public status page when my site is down?
A “down” status page signals that your team already knows something is wrong and is working to fix it. It can also help reduce the support burden when outages do occur because your users don't feel the need to contact you.
How do I set up a public status page?
With HeyOnCall you can turn any HTTP uptime check into a public status page by checking the “Public Status Page” checkbox in our dashboard. Once enabled, you’ll see the URL of your new public status page.
How does the status page update from up to down (and back to up)?
The status page updates automatically as we monitor your site, so there is no need to manually change your status page.
Can I create multiple status pages?
Yes.
What status page URL do I share with users?
After you check the “Public Status Page” checkbox, you’ll see the URL of your new public status page. You can share this URL with your users or link to it from your website.
What makes HeyOnCall better than alternatives?
Alternative solutions often require you to stitch together separate monitoring and on-call alerting tools using brittle webhooks between them. For example: would you really trust your self-hosted monitoring server to be able to send a POST request to your third-party alerting service exactly when you’re in the middle of a flaky network outage? :facepalm: Not exactly a recipe for reliability.
HeyOnCall integrates status pages, website monitoring, heartbeat monitoring, on‑call schedules, and alert delivery in one product, which removes fragile links and makes the overall system more reliable.
Status pages. Critical alerts. On-call schedules. Escalations. Monitoring for websites, APIs, cron jobs, and SSL certificates. All built-in and battle-tested. Designed for developers, by developers. Simple, flat pricing. Free tier forever.
How fast can I get started?
Sign up (free tier forever), add a URL, and start receiving checks in about a minute.
Live sandbox resets hourly.
No sign-up required.
No credit card required.
Free tier forever.