# Status pages: products, page layouts and past incidents

- Date: 2026-10-03
- Categories: New, Improved
- Tags: Status pages, On-Call
- Author: The EvoHub team
- URL: https://changelog-dev.evohub.io/status-pages-products-page-layouts-and-past-incidents

> Group components into products, choose how visitors see them (one list, folded groups, or a page per product), let visitors follow a single product, and record past incidents from On-Call.

Status pages can now present several products on one page.

### Products and layouts
- Groups of components are your products. Choose one of three layouts: **One list** (the default, unchanged), **Folded groups**, or **A page per group**.
- With folded groups, each product shows its overall status and a rolled-up uptime bar, and you choose which products start open.
- With a page per group, every product gets its own page with its components, uptime history, incidents and maintenance, and the main page becomes a directory of product cards with their current status and recent history. Up to three products per page.
- Give each product its own logo.
- Visitors can subscribe to a single product. Components added to the product later are included automatically.

### Console
- Reorder components and whole groups by dragging or with the arrow buttons, and rename a group from its heading.
- The console shows a component's status the way visitors see it while an incident or maintenance is active.
- Editing a component no longer resets its status or moves it to the top.
- Incidents and maintenance are now run from On-Call, and the status page console shows them read-only, so the two never drift apart.

### Past incidents
- Record an incident that has already ended from On-Call with **It already happened** and its start and end times. It pages nobody.
- Publishing it adds it to the status page history on the right days, without emailing subscribers.

### Public page
- Maintenance stages are shown in their own colours, and the main page names the incident that is currently live.