Request an invite

Create your status page

From a new account to a public page in five steps: your organization, the page, its components, its monitors and, on the paid plan, your own domain.

You need an Upstreamr account. During the invite-only beta, accounts are by invitation: request an invite.

The free plan covers 1 page, 10 monitors and 100 email subscribers. See plans

Guides and contents

Sign up and create your organization

Sign up with your name, your work email and a password of at least 12 characters, then open the link in the email we send you. It works for 24 hours.

The setup wizard opens next. It walks you through your organization, your status page and your first monitor, then two optional steps: provider locations and teammates. Skip setup leaves it; every step can be done later from the admin.

  1. Enter the Organization name and a Slug: 2 to 48 lowercase letters, digits and dashes.
  2. Select Create organization.

Create the page

Enter a Page name, the Address (the page’s free subdomain), an optional Logo URL and your Time zone, then select Create page. The wizard’s page is published straight away. You can add your own domain later.

More pages are under Pages → New page. A new page starts unpublished, and an unpublished page answers 404 until you switch on Published in its settings. Each page has tabs for its settings, access, domains, theme, groups, subscribers and webhooks.

An example status page with a scheduled maintenance written by the hosting company: cooling system maintenance in Limburg, Thu 5 Nov 2026, 06:00 to 15:00 UTC, affecting Dedicated servers, Limburg. Example data.

Add components

Components are the parts of your service your customers care about: a website, a server range, a network, a datacenter. Each has its own status and uptime.

  1. Go to Components → New component.
  2. Name it and pick its Kind: Service, Server, Network, Region, Datacenter or PoP. A description and a location are optional.
  3. Under Placements, select Add to a page. Choose the page, a group, the name shown there, its order and whether to Show uptime.

A component that’s on no page stays private. Put one component on several of your pages and an incident posted once shows on every page in your organization that displays it. Groups (Components → Groups) gather components under a heading; a Collapsed group starts folded.

Add monitors

The wizard’s first monitor already checks one address over HTTP and drives the component it created. For the rest, go to Monitors → New monitor and pick a type:

  • HTTP(S) and TCP port run from Cloudflare’s edge, with nothing to install. To check that a page contains a word, use HTTP with Body must contain.
  • DNS runs from the edge too, over DNS-over-HTTPS through a public resolver, and checks the answer against the values you expect. Domain expiry reads your domain’s expiry date from its registry once a day, for domains under TLDs with RDAP; it alerts your team 30 days before and goes down once expired (Warn below (days), Down below (days)).
  • TLS certificate and Ping (ICMP) run on a probe agent on your own servers (paid plan, 1 agent included), and so does DNS through a resolver you choose. A certificate check alerts your team 14 days before the certificate expires and goes down once it has. Until then the status page stays operational: an expiry warning is yours to act on, not something your customers see.
  • Game server queries the game itself: see Game servers.
  • Push (heartbeat) waits for your job to call its URL. If no call arrives within the interval and its grace, the monitor is down; a call with ?status=down marks it down at once.

Pick the Component the monitor drives, or leave it empty to only record the checks. The Interval (s) is every 3 minutes at most on the free plan and every minute on the paid plan. With two or more probes, Quorum sets how many must agree before the monitor goes down.

Post incidents and maintenance

Incidents → Report incident or Schedule maintenance. Choose the affected components and pages and keep Notify subscribers on. A maintenance starts and ends on its own at the times you set.

  • Start from template fills the title, first update, status and components from one of your Templates (in the sidebar). Placeholders such as {component} and {window} are filled in when you publish.
  • Repeats makes a maintenance recurring: weekly, monthly on a day of the month, or monthly on a weekday such as the first Tuesday. The next two windows are always scheduled ahead.
  • Subscribers get reminders before a maintenance starts, 24 hours and 1 hour ahead by default. Pick up to three of 1 week, 48 hours, 24 hours and 1 hour per page under Maintenance notifications in the page’s settings, or per maintenance with Reminders to subscribers. Each goes out once per window.

Switch from another status page

Moving from OpenStatus, Atlassian Statuspage, Instatus or Better Stack? Bring your components and past incidents and maintenance with you.

  1. Open the page and select Import history (organization owners and admins).
  2. Enter your current status page’s address, such as status.example.com. Upstreamr finds out which provider runs it, or choose it under Provider. Any RSS or Atom status feed works too, with titles, text and dates only.
  3. The preview lists the components, groups, incidents and maintenance that will be added, what’s already here, and what the old page can’t provide. Select Import.

Every update comes over with its original time, and past events arrive resolved. Nobody is notified, and upcoming maintenance doesn’t start, end or send reminders until you edit it. Run the import again just before you switch: it adds only what’s new. Statuspage shares its 50 most recent incidents and maintenances; Instatus and Better Stack their recent history in full and older events with less detail. Then bring your subscribers.

Integrations come along too. Every page answers Atlassian Statuspage’s read API at the same addresses, such as /api/v2/summary.json, and the feeds at /history.atom and /history.rss, so widgets, monitors and scripts that read your old page’s API or feeds keep working once your domain points here. Components and incidents get new ids, so a tool that looks one up by its Statuspage id needs the new one: The API.

Use your own domain

Custom domains are on the paid plan.

  1. Open the page, then the Domains tab. Enter the Hostname, such as status.example.com, and select Add domain.
  2. At your DNS host, add the two TXT records the tab shows (one proves you own the name, one lets the certificate be issued), then the CNAME it shows. For a bare domain without a subdomain, use your DNS host’s CNAME flattening, ALIAS or ANAME record.
  3. The domain moves from Pending DNS to Validating SSL to Active. Refresh checks again; with more than one domain, Make primary picks the page’s main address.

Link previews and the page icon

When someone shares your page or one of its incidents in Slack, Discord, Teams, WhatsApp or on X, the preview shows a picture: your logo and the page’s current state in its colour, or the incident’s title and where it stands, in the language of the link. It follows the page as it changes. A private page shows no picture.

Browser tabs and phone home screens use the Favicon URL under Links & branding in the page’s settings. Without one, they show your page’s first letter on its colour.

What to do next