Status pages

A status page shows your users the current state of your services and the recent incidents, updated automatically from your monitors. It answers "is it just me?" before they open a support ticket.

Create pages in Status pages → New status page. The number of pages depends on your plan — see Pricing.

Address#

Every page has a slug and is published at:

https://status.isituprightnow.com/<slug>

Changing the slug later breaks the links people already have, so choose it carefully. You can also serve the page on your own domain — see Custom domain.

Components#

Add the monitors the page should show. For each one:

• Display name — what your users see (API, Website, Checkout), independent of the monitor's internal name;
• Order on the page;
• Show uptime — show or hide the uptime percentage.

Each component shows its current status (operational, outage, maintenance, paused or unknown) and a bar per day for the last 90 days with that day's uptime and incidents. Only the monitors you add are visible; targets, URLs and alert settings are never shown.

The overall status at the top is:

Active incidents and those of the last 14 days are listed below the components. Public data is refreshed about every 30 seconds.

Appearance#

Privacy and search engines#

• Password protection — visitors must enter a password to see the page. Status badges are not available for protected pages.
• Hide from search engines — adds noindex so the page doesn't appear in search results (useful for internal pages).
• Google Analytics — add a measurement ID (G-…) to load Google Analytics on this page only. Leave it empty and no analytics script is loaded.

Custom domain#

Serve the page on a domain of your own, such as status.example.com (available on plans with custom domains):

1. In the page settings, enter the domain under Custom domain and save.
2. At your DNS provider, create a CNAME record for that host name pointing to:

status.isituprightnow.com

3. Wait for the status to become Active. We check the record about every 10 minutes; DNS changes can take up to 24 hours. HTTPS certificates are issued automatically once the record resolves.

Use a subdomain: most DNS providers don't allow a CNAME on the bare domain (example.com). A domain can be used by one status page only.

Subscribers#

Visitors can subscribe to a page with their e-mail address:

• They confirm the subscription through a link (double opt-in) and can unsubscribe from every e-mail.
• They are e-mailed when a component goes down and when it recovers (at most one outage e-mail per page every 15 minutes), and when you post an announcement.
• You can see and remove subscribers in the page editor. Each page has a maximum number of subscribers.

Announcements#

Two ways to tell visitors about something that monitors can't see (planned work, a partial problem, a third-party issue):

• Pinned banner — a short text at the top of the page until you remove it.
• Post an announcement — a title, a message and a severity (info, warning or critical). It is published immediately and e-mailed to confirmed subscribers. The newest announcement of the last 7 days is shown on the page.

Status badge#

Show the live overall status in a README, on your website or in your docs:

https://status.isituprightnow.com/<slug>/badge.svg

[![Status](https://status.isituprightnow.com/<slug>/badge.svg)](https://status.isituprightnow.com/<slug>)

<a href="https://status.isituprightnow.com/<slug>">
  <img src="https://status.isituprightnow.com/<slug>/badge.svg" alt="Service status" height="20">
</a>

The badge reads status | operational, degraded, outage, maintenance or unknown, and is cached for 60 seconds. Badges of password-protected pages return 404, so a badge never reveals a private page.