Status pages
Publish a branded public page that shows your services' health, uptime, and incident history — and let your users subscribe to updates.
A status page is a public (or private) page that shows the current health of the services you monitor, their recent uptime, and any ongoing or past incidents. Instead of fielding "is it down for everyone or just me?" questions, you point users at one link that always reflects reality.
Your status page pulls live data straight from your monitors — you don't maintain it by hand. When a monitor goes down, the page updates on its own; you only step in to post an incident when you want to add human context.
Creating a status page
From Status pages in the portal, create a new page and give it:
A name — shown as the page's heading (e.g. "Acme Status").
A slug — the URL segment for the page. It's generated from the name and can be edited; slugs may contain lowercase letters, numbers, and hyphens only, and must be unique within your team.
Publish — a page stays unpublished (a private draft) until you toggle it live, so you can set everything up before anyone can reach it.
Adding monitors
A status page shows the monitors you assign to it — not your whole account. For each monitor you add, you can set:
- A display name — a public-friendly label (e.g. show "Checkout API" instead of the internal monitor name).
- Display order — the order services appear on the page.
Each monitor's public row shows its current status and an uptime bar. Telescope rolls the individual monitor statuses up into a single overall status banner at the top of the page:
| Overall status | When it shows |
|---|---|
| Operational | All assigned monitors are up |
| Degraded performance | At least one monitor is degraded, none are down |
| Partial outage | Some — but not all — monitors are down |
| Major outage | All assigned monitors are down |
Visibility
Control who can reach the page:
| Visibility | Who can view |
|---|---|
| Public | Anyone with the link |
| Private | Anyone with the link and the page password |
| Team only | Only signed-in members of your team |
Use Private for a customer- or partner-facing page you don't want indexed, and Team only for an internal dashboard.
Branding
Make the page match your brand:
- Logo and favicon
- Primary color (defaults to
#3B82F6) - Header and footer text
- Custom CSS for finer control
- Meta title / description for how the page looks when shared or indexed
You can also serve the page from your own custom domain (e.g. status.yourcompany.com) instead of the default Telescope URL.
Display options
- Show uptime percentage — display the rolling uptime figure per monitor.
- Show response time — display response-time data.
- Uptime window — how many days of history the uptime bars cover (default 90).
Incidents
When something goes wrong — or you're doing planned maintenance — post an incident to tell users what's happening. An incident has an impact and moves through a status lifecycle, with timestamped updates you add as the situation evolves.
Impact levels: none, minor, major, critical.
Status lifecycle:
| Status | Meaning |
|---|---|
| Investigating | You're aware and looking into it |
| Identified | You've found the cause |
| Monitoring | A fix is in place and you're watching it |
| Resolved | The incident is over |
Each update you post is stamped and kept, so the page shows a full timeline — during the incident and in the page's history afterward.
Letting users subscribe
Visitors can subscribe to a status page to be notified when incidents are posted, over any of:
- Email — they enter their address and confirm via a double-opt-in link.
- Slack — they connect a Slack workspace to receive updates in a channel.
- Microsoft Teams — they add an incoming webhook for a Teams channel.
Every subscription is confirmed before it's active, and every notification includes an unsubscribe link.
Embedding
To surface your status inline on your own site, use the embed snippet from the page's settings — a small widget that shows current status without sending users away.