Read live status and incident history

The live page shows its overall state, the current status and recent availability of each selected component, and public Incident history.

Each component row renders 60 real history segments from Heartbeat observations. The window is bounded by the workspace plan, so a Pro page shows its 90 visible days rather than repeating the current state.

Use the component rows to see which monitor is affected, then read the Incident history for recorded start and resolution details.

When a page has no component state to report, niceuptime uses its defined overall fallback rather than inventing an Incident.

Listed public pages requested by slug may be served from a short shared cache; hostname reads use no-store caching.

Private pages show an access gate instead of monitor or Incident data.

Unlisted pages remain available by their direct route, while missing or unavailable pages do not render a live status page.