How to add a public status page to your website

When the homepage fails, visitors need a page they can refresh. Waiting for a social post is too slow.

Sitebase’s status page checks the URLs you pick and publishes the result. Visitors see the current banner, a row per monitor, and a timeline when something is down.

Sitebase is in private beta. Public signup isn’t open. These steps are for accounts with access.

Pick the URLs visitors use

Start with the pages that would make someone think the product is down. The marketing homepage is one. The app, the API, or a docs site can be others.

Write them as full URLs. Use the address a visitor would type.

Two or three monitors is enough for a first page. Starter includes 3 monitors. Pro includes 10, Business 25, and Agency 50.

Create the status page

Add your website in Sitebase. On the Features to start with step, select Status page. A site has one status page. You add several monitors inside it.

If the site already has the feature, open Status page in the sidebar.

Until you add a monitor, the page shows Setup, Config, and Docs. After the first monitor, Monitors, Incidents, and Data appear. Monitors becomes the default tab.

Add a monitor

Open Setup. Under Add your first monitor, enter a name and a URL.

Name it the way you talk about it: Website, API, Docs. For the URL, use something like https://flaviocopes.com.

Click Create monitor. That first form only asks for those two fields. Sitebase stores the check as GET, every 5 minutes, expecting HTTP 200.

To add another monitor, use + Add monitor on the Monitors tab. That form also lets you pick:

• Method: GET or HEAD
• Interval: 5 min by default. Pro and above can also pick 1 min or 2 min
• Expected status: 200 unless you check a URL that answers with something else

HEAD is useful when you only need to know the URL is reachable and you do not want the full body. GET is the first choice for a regular page.

You can Pause a monitor during maintenance and Resume it later without losing history. Delete asks for confirmation.

Sitebase sends checks with the user agent Sitebase-Uptime/1.0. If a firewall blocks unknown bots, allow that string so the checks can reach the URL.

Tune what visitors see

Open Config. The default title is System Status. The default description is Current status of our services. Change those to match how you talk about the product.

Show response times and Show uptime percentages are on by default. Leave them on unless you want a quieter page.

History period (days) can be 30, 60, or 90. The default is 90. That window is what the Data tab and the public uptime bars use.

There is also a checkbox to email you and your collaborators when a monitor goes down or recovers. It starts off. Turn it on if you want those emails. They are not part of the profile notification toggles.

Save. The public embed updates behind the same snippet.

Put the page on your site

Copy the snippet from Setup. The public key identifies this status page. It is not a private API credential.

This is the shape of it. Replace YOUR_STATUS_KEY with the key from your dashboard, or paste the complete snippet Sitebase gives you:

<script
  async
  crossorigin="anonymous"
  src="https://sitebase.dev/embed.js"
  data-sitebase-widget="YOUR_STATUS_KEY"
></script>

Put it on a /status page, or in the footer of the site you monitor. In an Astro page, add is:inline so the script stays intact.

The hosted page is easier on Notion, Wix, or Squarespace, which strip script tags. The Setup tab shows that URL too:

<iframe
  src="https://sitebase.dev/embed/YOUR_STATUS_KEY"
  title="System status"
  style="width:100%;height:640px;border:0"
></iframe>

Give the iframe enough height for the banner, the monitor rows, and any open incidents, including on a phone. The hosted page refreshes itself every 60 seconds and does not collect visitor data.

When something is down

A check that times out or cannot connect is down. A response with the wrong HTTP status is degraded. Degraded does not open an incident.

After two consecutive down checks, Sitebase opens an incident. If you named the monitor Website, the title is “Website is down” and the status is investigating. The first update says the automated check found the URL unreachable.

When the URL answers again, the incident is marked resolved. The update is “Service has recovered. Incident auto-resolved.”

You can also use + Report incident for maintenance you already know about. Pick the affected monitor, write a title, choose Investigating, Identified, or Monitoring, and add a message. Later, Post update can move it through those statuses or mark it Resolved.

The public banner reads All systems operational when every monitor is up. If any monitor is down, it reads Major outage detected. A degraded monitor reads Some systems experiencing issues. Open incidents appear under Recent incidents, plus resolved ones from the last 14 days.

Check the first result

Open the hosted URL from Setup in a fresh browser window.

You should see Checking status… first, then the banner and your monitor rows. Confirm the name, the uptime percentage, and the response time if you left those toggles on.

On a phone-sized screen, check that the rows stay readable.

Then look at Monitors in the dashboard. Last check should move from Never to a recent time. Data shows an uptime bar per monitor under Uptime overview (90-day) if you kept the default history. Right after the first check, the daily strip may still say No data yet. That fills in as checks land.

If a check never appears, confirm the URL is public, uses https://, and is not blocked for Sitebase-Uptime/1.0.

For install detail, see embedding Sitebase features and the status page documentation. If you also want visitor numbers on the same site, follow how to add analytics.