How Does a Statsy Status Page Work?

Statsy gives you a public status page at your own domain, tracks each service's health automatically, and emails subscribers when something breaks. You can start on a free plan with no credit card, and the site claims an average setup time of about 5 minutes from signup to a live page. It's aimed at developers and small teams who want transparency without building and maintaining their own status infrastructure.

What the page actually shows

The core idea is a single public URL — status.yoursite.com — that your users check when something feels broken. On that page, Statsy displays:

• Per-service status: each service (Website, API, Auth, Database, Email Delivery, Dashboard, and so on) shows as Operational, Degraded, or Outage.
• A 90-day uptime figure, tracked automatically rather than entered by hand. The example on the site shows "90-day uptime — 99.4% · 13 days without incident."
• Past incidents and maintenance, listed with a date, a short description, and a resolution note. Resolved incidents and completed maintenance are marked separately.
• A one-click email subscribe for visitors. No account is required on the visitor side — they enter an email and get alerts.

So the page serves two audiences at once: someone glancing at it to confirm "is it just me?", and someone who wants to be told proactively.

How monitoring and updates flow

Statsy pairs the status page with uptime monitoring, so the page reflects real checks rather than manual edits.

1. You point Statsy at endpoints — for example https://api.yourapp.com/health or https://yourapp.com. The site's example shows response times attached to each (142ms Operational, 2.4s Degraded, a timeout marked Outage).
2. Statsy checks them on an interval. The free plan's interval isn't stated in the material; the site lists a 1-minute check interval on Pro.
3. When a check fails, the status changes and alerts fire. The example notification reads: "Statsy detected that dashboard is down. Your status page has been updated automatically."
4. Recovery is detected and announced too — a follow-up email notes the service "is back up."

The practical takeaway: once endpoints are configured, the page updates itself. You're not manually flipping a service to "Degraded" during an incident unless you want to.

Setting it up

The site describes the flow as signup → live page in about 5 minutes, with no onboarding calls. Based on the material, the steps are:

1. Create an account via "Get Started Free." No credit card is required for the free plan.
2. Add your services and their check URLs (health endpoints, homepage, dashboard, etc.).
3. Publish the page. It's live at a Statsy URL immediately; a custom domain like status.yoursite.com is available on paid plans.
4. Let visitors subscribe. They click subscribe, enter an email, and receive incident and recovery alerts.

Verification: load the public URL in a private browser window — you should see your services with current statuses and the 90-day uptime figure without logging in. Then trigger a test by pointing a check at a URL you know will fail, and confirm the status flips and an alert email arrives.

What's free vs. paid

The material is explicit about a few boundaries and silent on others, so treat this as the reliable split:

The site repeats "$0 to get started on free plan, forever," but it doesn't publish a full feature-by-feature free/paid comparison or prices in the material provided. If the custom domain or the 1-minute interval matters to you, check the pricing page before committing — those are the two capabilities the site explicitly ties to paid tiers.

Common questions worth answering up front

• Do visitors need an account? No. Subscribing to email alerts is one click, no account needed.
• Do I have to update the page manually? No — monitoring drives the status automatically, though the incident/maintenance entries shown in the example are written descriptions.
• Can I use my own domain? Yes, on paid plans.
• How fast are checks? 1 minute on Pro; the free tier's interval isn't stated.

Who this fits

Statsy suits a small team that wants a credible public status page without standing up its own monitoring stack or paying enterprise status-page pricing. It fits less well if you need the custom domain on a zero budget, or if you need a monitoring interval faster than what the free tier offers — in those cases the paid plan is the real starting point, and you should confirm current pricing first.