Create a Public Status Page for Your Monitors
Before you start
You need at least one LoadFocus monitor - a status page publishes the results of checks you already run. New to the idea? See what a status page is.
Create a status page
- Open Status Pages from the sidebar (or go to
/status-pages). - Click New status page.
- Give it a title and a subdomain. Your page goes live immediately at
https://your-subdomain.loadfoc.us.
After saving, the editor stays open on Components so you can pick the checks the page should show - a new page has none yet.
Page details
The title is the name visitors see. The subdomain decides the address, and it can be changed later: the old one keeps redirecting, so a shared link never breaks.
Published is the on/off switch. An unpublished page is a draft - visitors get a 404 until you tick it, which is what lets you set a page up properly before anyone sees it.
Branding
Brand colour drives the accent on the page and in the emails your subscribers receive. Colour theme is light, dark, or auto (follow the visitor's own system setting).
Header layout chooses between a large centred status headline and a compact horizontal row. The horizontal one leaves more room for content, which helps once a page has many services.
For the logo you can either paste a URL or upload an image - drag one onto the box, or click to choose. There are separate slots for light and dark backgrounds, plus a favicon. PNG, JPEG, WebP, GIF, SVG and ICO are accepted, up to 256 KB. An uploaded image always wins over a URL in the same slot. If you enter your website address and press Fetch logo, we will try to find one for you.
Get in touch is where the button in the page header points. It takes a URL or an email address.
Language sets the language of the public page - the status labels, the tab names and the subscribe form. It is independent of the language you use in the dashboard.
Status history
Days to display is the length of the uptime bar under each component: 30 or 90 days. The uptime percentage next to it always covers the same window as the bar.
Timezone decides where a day starts. Set it to the timezone you operate in, or "yesterday" on the bar will mean something different to you than it does to the page.
Uptime decimal places controls how the percentage is written - 99.9% or 99.917%.
Show "Not monitored" as Operational paints a day with no checks green instead of grey. It is never applied while our own collector is stalled: an outage on our side must not read as green on your page.
Hide from search engines is off by default, so your status page can be found. Turn it on to keep it out of search results.
Announcement
A short note pinned above everything on the public page - a heads-up that does not warrant a full incident. It renders as plain text, and clearing the field removes it.
Optionally give it a URL to open when clicked, and tick Email subscribers about this announcement to send it out. That only fires when the text actually changes, and only for that save: re-saving the page with the same announcement will not mail anyone twice.
You can also show the same announcement on your own site. Copy the <script> tag and paste it
before your closing </body> tag; the bar stays hidden until an announcement is set, and a
visitor who dismisses it sees it again once you change the text.
Components
A section is a group of services, and it owns the components inside it. Rename the section once and everything under it follows. Leave the section name blank to hide its heading.
Each component is one service on your page. Give it a name, optionally a short description, and tick the checks that power it - their results drive the live status and the uptime bar. Untick Show status history to display the component's current state without the bar.
Reorder sections and components with the arrows, or drag them by the handle on the left. Dragging a component into a different section keeps it intact, including any subscribers who follow it - which deleting and re-adding it would not.
Incidents
Report and update incidents through their lifecycle: investigating, identified, monitoring, resolved. Choose which components are affected and how badly, and whether to email subscribers.
Turn on automatically create incidents and we will open one for you when a check fails, and resolve it when the check recovers. Minimum incident length hides very short blips from the public history, so a flapping check does not fill your page with noise.
Maintenance
Schedule maintenance windows, one-off or recurring, so planned work does not look like an outage. Affected components show as under maintenance for the duration.
Subscribers
Let visitors subscribe to email updates for incidents and maintenance. Subscriptions are double opt-in - we email a confirmation link, and nobody is subscribed until they click it. You can see and remove subscribers from this tab.
Private page
Keep a status page off the public internet with a password, an IP allowlist, or both. A locked page is never indexed by search engines regardless of the other settings. This is a paid feature.
Share and embed
Your page is public at https://your-subdomain.loadfoc.us. The editor gives you three ready
snippets:
- an iframe that embeds the whole status page in your own site,
- a status badge image you can put in a README or a footer,
- the RSS feed of incidents, for a reader or a chat channel.
Top navigation links replace the default Status / Maintenance / Previous incidents links if you would rather point visitors at your own pages.
To serve the page on your own hostname instead, for example status.yourcompany.com, follow
Add a Custom Domain to Your Status Page.
Read it programmatically
Every status page also serves a Statuspage-compatible JSON API, RSS and Atom incident feeds, and an SVG status badge. See Status Page API, RSS Feeds and Status Badge.