Free hosted status page, no card
The status page that updates itself
UpButler status pages are wired to real checks. When something breaks, the component turns orange, an incident opens with a drafted update, and your subscribers hear about it, often before your support inbox does.
Live example: upbutler.com/s/upbutler
Written by AI from monitoring data
Searches are returning results up to two minutes late while we rebuild an index. Nothing is lost; new items appear as the rebuild catches up.
Product
Infrastructure
Email · Webhook · Slack · Discord · RSS
Four ways a component learns its status
A status page is only useful if it is true. Pick the source per component and mix them freely on one page.
- 1
Monitors
A component follows one or more checks. Worst-of or majority, your choice.
- 2
Push
Your deploy script, CI or agent posts statuses, many components in one call.
- 3
Manifest
One JSON health endpoint, every key becomes a component. Reads Statuspage components.json too.
- 4
Manual
Set it by hand from the dashboard when you know before the checks do.
curl -X POST https://upbutler.com/api/v1/services \
-H "Authorization: Bearer $UPBUTLER_KEY" -H "Content-Type: application/json" \
-d '{"name":"Search API","url":"https://api.acme.com/health","statusPage":"acme","group":"Product"}'curl -X POST https://upbutler.com/api/v1/pages/acme/status \
-H "Authorization: Bearer $UPBUTLER_KEY" -H "Content-Type: application/json" \
-d '{"statuses":{"search":"operational","exports":{"status":"degraded","message":"Queue backlog"}}}'// GET https://api.acme.com/status.json, checked every minute
{
"search": "ok",
"exports": { "status": "degraded", "message": "Queue backlog" },
"billing": "ok"
}You: "Put our new billing service on the Acme status page."
Agent → services_add { name: "Billing", url: "https://billing.acme.com/health",
statusPage: "acme", group: "Product" }
← monitor mon_8f2…, component "Billing", https://status.acme.comMonitors re-check a failure about 15 seconds later and only flip after two consecutive failures by default; pushed and manifest statuses get the same blip protection, needing two fresh reports before a component turns worse, while recoveries apply at once. A single slow request never paints your page red.
Incidents written for the people reading them
Failures open an incident automatically. Several components failing on the same page within 30 minutes share one incident, so customers read one story instead of five alarms.
Every incident gets an AI report built from the actual check data: likely causes and next steps for your team, and a customer-safe summary that leaves out hostnames and stack traces. On recovery, a post-incident summary is drafted for you. Write your own updates and polish them with one click, or let your agent post them through the API.
You set the voice. Each page has AI guidelines ("never mention our cloud provider") and a list of banned terms; AI text that uses one falls back to a neutral template. Incident templates keep recurring updates consistent, and after a bad day the AI drafts a postmortem from the timeline, checks and deploys that you can edit and publish to the page.
Scheduled maintenance works the same way: announced ahead of time, components marked while it runs, completed on schedule.
14:02Investigating
Search API failed 2 consecutive checks (HTTP 503, 30.0 s timeout). Incident opened automatically.
14:03AI reportinternal
Likely cause: index rebuild saturating the search cluster; response times rose for 6 minutes before the first 503. Suggested: pause the reindex job, check node memory.
14:09Identified
Searches are returning results up to two minutes late while we rebuild an index. Nothing is lost.
14:31Resolved
Recovered after 29 minutes. Post-incident summary drafted for review.
Your brand, not ours
Start from a theme, pick your fonts and accent, upload a logo. From Starter, the "Powered by UpButler" line disappears and your own domain is included as bring-your-own domains roll out. Pro adds custom CSS.
Live on its own address, instantly
Every page gets a short HTTPS address the moment you create it. No DNS, no certificates to manage. Bring-your-own domains are coming soon.
https://acme.upbutler.com (live as soon as you create the page)Groups, history and the details people look for
- Component groups that collapse, with optional descriptions per component.
- 90-day uptime bars per component, with the uptime percentage.
- Past incidents with their full public timeline, and a page per incident to link to.
- RSS, Atom and a JSON view of the page for anyone who wants to automate against your status.
Subscribers, on the channel they already watch
Visitors subscribe from your page. Updates fan out when you post them, from the dashboard, the API or an agent.
- Double opt-in, one-click unsubscribe, per-component preferences.
- Webhook
- A challenge handshake proves the endpoint is theirs; payloads are signed (Standard Webhooks).
- Slack
- Incident updates posted to a channel of their choosing.
- Discord
- Same updates, for communities that live in Discord.
- RSS & Atom
- For feed readers and the tools that poll them.
A free status page, and what paid plans add
Free has no time limit, and every new workspace starts with 14 days of Pro. Starter is $12/month, Pro $29 and Business $99; yearly billing gets two months free. Full details on the pricing page.
| Feature | Free $0 | Starter $12 | Pro $29 | Business $99 |
|---|---|---|---|---|
| Status pages | 1 | 1 | 5 | 20 |
| Components per page | 10 | 30 | 100 | 500 |
| Email subscribers per page | 25 | 500 | 5,000 | 25,000 |
| Emails per month | 300 | 2,500 | 15,000 | 60,000 |
| Webhook, Slack, Discord, RSS subscribers | Included | Included | Included | Included |
| Themes and fonts | Included | Included | Included | Included |
| Custom domains (rolling out) | — | 1 | 5 | 20 |
| Remove UpButler branding | — | Included | Included | Included |
| Custom CSS | — | — | Included | Included |
| AI incident reports per month | 10 | 100 | 1,000 | 5,000 |
| History | 30 days | 1 year | 1 year | 2 years |
Status page questions
Is the status page really free?
Yes. The Free plan includes one hosted status page with up to 10 components, 10 monitors, 25 email subscribers, unmetered webhook, Slack, Discord and RSS subscribers, and 10 AI incident reports a month. No card, no time limit, and commercial use is fine. It lives at your-slug.upbutler.com with a small "Powered by UpButler" note. New workspaces start with 14 days of Pro; when your page needs more components, more subscribers or no branding, Starter is $12/month.
Can I host the status page on my own domain?
Every page is live at its own address with HTTPS, like acme.upbutler.com, on every plan. Bring-your-own domains (status.yourcompany.com) are rolling out soon, included from Starter: 1 on Starter, 5 on Pro and 20 on Business.
What is the 90-day uptime bar?
Each component shows one bar per day for the last 90 days, colored by the worst status that day, with the uptime percentage underneath.
Do I have to use UpButler monitoring to use the status page?
No. Components can be driven by pushes from your own systems, a manifest JSON endpoint, or set manually. Many teams start by pushing from an existing monitoring tool and move checks over later.
Will the status page go down when my app goes down?
No. Status pages are served by UpButler, separately from your infrastructure, so they stay up when you are having a bad day. That is the point of a hosted status page.
Does AI post updates on my behalf?
On automatic incidents, by default, yes: the first public update and the recovery note use the AI-written customer-safe summary, as long as it follows the page’s AI guidelines and avoids its banned terms (otherwise a neutral template is used). Turn AI public updates off per page if you want to write every update yourself. The internal technical analysis is never published.
Can I schedule maintenance?
Yes. Scheduled maintenance shows on the page in advance, notifies subscribers, moves affected components to "maintenance" while it runs and completes on its own.
Your status page, live in a minute.
Create it from the dashboard, or hand your agent an API key and one sentence. Free for one page and 10 monitors, with 14 days of Pro to start.