Create a public status page for your website or API

Someone opens your product and a request fails. Before contacting support, they want to know whether the service is having a problem. A status link in your website footer gives them somewhere to check.

DebugBundle now lets you create a public status page from the health checks you already run. Choose what to publish, give the page a title, and share its URL. Visitors can see current availability and recent uptime without signing in.

Turn health checks into a shareable status page

A website status page might show your main application and its API. An API status page might publish just the endpoints your customers depend on. Each DebugBundle page starts from one project, with the option to include selected checks from other projects you own in the same account.

The page reuses the Health Status view: project rows, expandable health checks, daily availability bars, measured 30-day uptime, and the latest verified result. Hover over a day, or focus it with your keyboard, to inspect its aggregate availability details.

Those results come from your existing uptime monitoring. A visit to the page does not run another check. Recent outages remain visible after recovery, and missing, stale, or paused coverage does not become a reassuring green status. Uptime reflects recorded check outcomes; it does not establish that every feature of your product is working.

If you haven't configured monitoring yet, start with the availability checks guide. Our health check endpoint guide explains how to choose a target that represents the user-facing path you want to monitor.

Create your public status page

As the project owner, open Project → Health, then:

1. Click Public status page, beside Create health check.
2. Enter a page title, such as “Acme service status.”
3. Choose the checks to publish. Use Other projects to include additional projects, then select their checks too.
4. Turn on Enable public page. For a new page, this saves your selected title and checks and publishes it immediately.
5. Copy the URL from the Public status link input using the icon on its right. Add a “System status” link to your website footer, help center, or product navigation.

For an existing page, the switch saves visibility immediately. Changes to the title, projects, or checks still need Save status settings. Preview status page shows the saved public view, so save those edits before reviewing them there.

Turning the switch off removes public access once the save succeeds. The URL stays the same when you enable the page again, so you can keep the link on your website.

Combine projects under one status title

A SaaS product can span several DebugBundle projects: a website, a backend API, and a separate customer portal. Include the relevant projects on one page instead of sending customers to several status links.

The page title can represent the whole product. Project and check names remain visible underneath it, so use names your customers will understand. Including another project does not publish all its checks; you choose them explicitly. Newly created checks remain private until you select and save them.

Keep diagnostic details private

The public view contains the title, selected project and check names, availability state, measured uptime, daily aggregates, and verified timestamps. Endpoint URLs, environment and service labels, HTTP error details, incidents, logs, debug bundles, credentials, and account information stay private.

Review the names before publishing. A shareable URL is public, and anyone with it can read the selected names and availability. You can leave internal-only checks out while continuing to use them in your authenticated Health view.

The page follows each visitor's device light or dark preference and includes a small linked DebugBundle logo and Powered by DebugBundle attribution. Public status pages are available on all plans, including Free; your existing health-check limits still apply.

Let your coding agent help with setup

An authorized coding agent can manage the same settings through the authenticated DebugBundle CLI or developer MCP integration. It can list the available projects and checks, save a publication, inspect the saved preview, and return the public URL for your website.

For example, ask:

Use my authenticated DebugBundle connection to create a public status page titled “Acme service status” for [project]. Include only the [website] and [API] checks, and leave all other checks private. Publish the page, verify its saved configuration, and add the returned URL to this repository's website footer as “System status.” Leave the website change for review.

The CLI exposes debugbundle health status get|save|options|preview. The developer MCP server has corresponding public-status tools. These management operations require project-owner access; the separate hosted OpenAI read-only connection does not publish pages.

Follow the developer MCP setup guide if you want your agent to help. To publish your first page from the dashboard, use the public status page guide.