Public status pages

A status page is the cheapest support ticket you will ever avoid. When something breaks, people want one thing: confirmation that you already know.

Every plan gets one at <slug>.uptimeglobe.com. Pick which monitors appear, and it is live.

The slug is derived, not typed

You do not choose the subdomain directly. You nominate one of the page’s monitors as the primary, and the slug comes from its hostname:

troublefixers.org → troublefixers.uptimeglobe.com

The rule is the registrable domain’s second-level label — the bit that is recognisably your name — with the suffix dropped. Deriving it rather than letting anyone type it is what keeps stripe.uptimeglobe.com from being claimed by someone who does not own stripe.com.

Two cases have no derivable slug and cannot be primary: IP addresses, and heartbeat monitors, which have no host at all.

If the canonical slug is taken, the fallback appends the suffix — troublefixers-org — and then -2, -3 if needed. A hyphen rather than an underscore because DNS hostnames only permit letters, digits and hyphens; an underscored subdomain could not be served at all.

On the free plan, a slug is not reserved

If a paying customer’s primary monitor derives a slug a free account is holding, the paid account takes it. The free page is renamed — it keeps working, at a new address — and you get an email immediately, plus a notice in the dashboard until you pick a new primary monitor.

This only ever goes one direction: free to paid. A paid plan’s slug is never taken from it. If the address matters to you, that is the reason to be on one.

Your own domain

From Pro upward you can serve the page at your own hostname — status.example.com — by pointing a CNAME at us. The certificate is issued and renewed automatically.

The subdomain keeps working alongside it, so links you have already shared do not break.

What visitors see

Each monitor on the page shows current state and a history strip: 24 hours, 30 days, 90 days, and — on plans with longer chart retention — a year or two. Every plan gets the first three; see HTTP monitors for what is recorded per check.

Days with no data render as neutral gaps rather than as outages, which matters on a page younger than its window. A bar that says “no data” and a bar that says “down” are opposite claims and never share a colour.

Incidents you post appear beneath the monitors with their full update timeline, so a visitor can read what happened and when, not just that something did.

The page is server-rendered with no client-side JavaScript. It loads on a bad connection, during your outage, which is exactly when it is needed.

Badges, embeds and JSON

The same data is available in three other shapes — an SVG badge for a README, an embeddable widget for your own site, and a JSON feed for anything else. Those have their own page: badges, embed and JSON.

What it costs

Nothing extra. Status pages are included on every plan; only the custom domain is gated, and only from Pro.