A free status page that updates itself

What the free plan includes

• 1 public status page at yourname.status.scaledpapers.com
• 5 uptime checks (website, API, DNS, or TCP), every 5 minutes from 1 region you pick
• Incidents and maintenance: open incidents, post updates, schedule maintenance windows
• A 90-day uptime bar per component, with its uptime percentage
• Visitor subscribe by email, RSS (/incidents.rss), or Slack (/feed subscribe)
• A live SVG status badge for your README, docs, or footer
• The full REST API and MCP server, so Claude Code, Cursor, or Codex can set the page up for you
• 14 days of check results and email alerts

What visitors see

One status line (“All systems operational”) when things are healthy, or a colored banner for degraded performance, partial outage, major outage, or maintenance. Below it: each component with its status and 90-day uptime bar, open incidents at the top with the latest update, an “Under maintenance” list during a window, past incidents with full history, and a Subscribe to updates button. Visitors never need an account.

Checks that keep the page current

A status page with no checks behind it goes stale the minute you get busy. Here you link each component to a check. One failed check is recorded, not sent. When failures in a row reach the confirmation period you set (1, 2, 3, or 5), you get one alert. With auto-incidents on, the component goes down, an incident opens, and subscribers get one email. A blip during recovery doesn't open a second incident: it resolves once the check has stayed up for 5 minutes.

When to upgrade to Pro ($15/month)

Pro is for when the page becomes part of how customers judge you:

• Custom domain (status.yourcompany.com) over HTTPS, set up with a CNAME and a TXT record
• Private, password-protected status pages
• 5 status pages, 25 checks, 60-second checks from 5 regions (San Francisco, Ashburn, Montreal, Frankfurt, Singapore)
• 90 days of check results
• Slack, Discord, PagerDuty, Pushover, and webhook alerts

Compare plans

Set it up in a few minutes

1. Sign in and click New status page. Give it a name; the subdomain fills itself in.
2. Add components (for example API, Dashboard, Website).
3. Add a check for each component's URL, link it to the component, and turn on Create an incident on this component when the check is down.
4. Share the page link, or drop the badge in your README.

Or ask your coding agent: “Create checks for the health URLs in this repo and a public status page with one component per service.” The MCP docs show the one-key setup.