Status page
A public page that shows whether your services are up or down, what incidents happened, when maintenance is scheduled, and who is subscribed to get alerts.
What a status page is
A status page is a public page that shows the current state of your services. It lists each component, its current status (operational, degraded, or down), and an uptime bar for the last 90 days. It also shows active incidents with updates, scheduled maintenance windows, and a form for visitors to subscribe to email alerts.
Visitors can see at a glance whether a problem is on your side or theirs. Subscribers get an email when an incident opens, when it is updated, and when it is resolved. Each subscriber must confirm their email address before they start receiving alerts.
What belongs on a status page
The core elements are the component list, active incidents, scheduled maintenance, and a subscribe form. Components are the services you watch: a web API, a database, a third-party integration, or any endpoint you can check with an HTTP request.
Each component shows its current state and a 90-day uptime bar with one bar per day. Grey bars mean no data for that day. The overall banner at the top summarizes the health of all components: All systems operational, Partial outage, Major outage, or Under maintenance.
Components and checks
A component is one URL that is checked on a schedule. The check is a simple HTTP request (HEAD or GET) with an expected status code (default 200 to 399). You can also require a keyword to be present in the response. The check runs through an SSRF guard that blocks private addresses and limits redirects to five.
Checks are performed at the interval you set, from 5 minutes on the free plan to 1 minutes on Pro. Each plan has a component cap: 3 on Free, 20 on Pro, 100 on Business.
Incidents and the two-failure rule
An incident opens automatically when a component fails two checks in a row. This rule prevents false alarms from a single bad check. The incident stays open until the component passes two checks in a row, at which point it is marked as resolved.
You can also create manual incidents with a title and status (investigating, identified, monitoring, resolved). Each incident can have multiple updates that are emailed to subscribers. Past incidents are kept for 30 days on the public view.
Maintenance windows
Scheduled maintenance is announced ahead of time. You set a title, a start time, an end time, and the components affected. During the maintenance window, those components show as under maintenance and no auto incidents are opened for them.
Maintenance windows are kept for 30 days on Free and up to 400 days on Business, along with the rest of the history.
Subscribers and alerts
Visitors subscribe by entering their email address. They receive a confirmation email and must click the link before they are added to the list. This double opt-in keeps the subscriber list clean and compliant.
Subscribers get an email when an incident opens, when it is updated, and when it is resolved. Each plan has a subscriber cap: 100 on Free, 2000 on Pro, 10000 on Business.
The 90-day uptime bar
The uptime bar shows one bar per day for the last 90 days. Green means the component passed all checks that day, red means one or more checks failed, and grey means no checks were performed. The bar is a quick visual summary of reliability over time.
Raw check results are kept for 30 days on Free, 180 days on Pro, 400 days on Business. Daily uptime summaries are kept longer: up to 400 days on the Business plan.
Try a page before you sign up
The preview tool on the home page (/) needs no account. Paste a public page address, add a selector if you want one, and read the exact text that would be watched. Up to 20 previews a day are allowed from one address.
The pricing page (/pricing) lists the plans, the interval each one allows and what each one costs. It reads the same plan configuration the server enforces, so the numbers match.
Status page questions
How does a status page differ from a personal uptime alert?
A personal uptime alert checks one URL and sends an email when it goes down. A status page monitors multiple components, shows their current state to the public, and lets visitors subscribe to alerts. The same check engine runs both, but a status page is a shared communication channel while a personal alert is for one person.
What happens when a component fails?
A component must fail 3 checks in a row before an incident opens. This prevents false alarms from a single bad check. When the component passes two checks in a row, the incident is marked as resolved and subscribers are notified. If a component cannot be reached at all, a notice is sent after 3 failed checks without inventing a diff.
Can visitors subscribe without confirming?
No. Every subscriber must click a confirmation link in an email before they are added to the list. Unconfirmed subscribers are deleted after 7 days. This double opt-in keeps the list clean and respects the visitor's inbox.
What intervals are supported?
Free checks every 5 minutes at the fastest, 1 minutes on Pro and 1 minutes on Business. Checks are never counted, so a component runs at its own interval all month.