Uptime status page
An uptime status page watches your components with HTTP checks, confirms outages with two failures, and resolves automatically when the component recovers.
Uptime checks behind the page
Each component is checked on a schedule through an HTTP request (HEAD or GET). The check runs through an SSRF guard that blocks private addresses and limits redirects to five. You set the expected status code range (default 200 to 399) and an optional keyword.
Checks run at the interval you set, from 5 minutes on Free to 1 minutes on Pro. Each plan has a component cap: 3 on Free, 20 on Pro, 100 on Business.
The two-failure confirmation rule
A component must fail two checks in a row before an incident opens. This rule prevents false alarms from a single bad check. A temporary DNS issue, a slow upstream service, or a brief network glitch does not trigger an incident unless the problem persists.
When the second failure arrives, the incident is created and subscribers are notified. The incident stays open until the component passes two checks in a row, at which point it is marked as resolved and another email is sent.
Why a single failed check is not an outage
A single failed check can happen for many reasons that are not a real outage. Most transient issues clear up within a single check interval. If an incident opened on the first failure, subscribers would get alerts for problems that resolve themselves before anyone can act.
By waiting for two failures in a row, the system gives the component a chance to recover on its own. When the second failure arrives, the problem is more likely to be real and worth reporting.
The 90-day bar and no data days
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.
Grey bars mean no data for that day. Days without checks are not counted as up. The raw check results are kept for ${FREE_HISTORY_DAYS} days on Free, ${PRO_HISTORY_DAYS} days on Pro, ${BUSINESS_HISTORY_DAYS} days on Business.
How an incident opens and resolves automatically
An incident opens automatically when a component fails two checks in a row. The incident status is set to investigating. When the component passes two checks in a row, the incident is marked as resolved and subscribers are notified.
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.
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.
Uptime status page questions
What is the two-failure rule?
A component must fail 3 checks in a row before an incident opens. A single failed check does not trigger an incident. This prevents false alarms from temporary issues.
What does a grey bar mean?
Grey means no checks were performed that day. Days without checks are not counted as up. The uptime bar shows 90 days of history with one bar per day.
How long is history kept?
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.
Can I create manual incidents?
Yes. You can create manual incidents with a title and status (investigating, identified, monitoring, resolved). Each incident can have multiple updates that are emailed to subscribers.