Hello Statuspage Team,

I would like to propose two improvements to how historical data is managed on a status page.

Current situation:

The start date is set per component. It can only be moved forward if all earlier downtime data (incidents, maintenances, and component-level downtime) is deleted first. With many components, this means a lot of manual work, and the result is that we lose history we may still want to keep for ourselves.

Proposal:

1. Export historical data for all components

A page-level export (CSV and/or JSON) of all historical uptime, downtime, incident and maintenance data per component, available in the UI and through the API. This would allow us to archive data before any cleanup and use it for internal reporting.

2. A global "public display start date"

A single page-level setting, applied to all components by default (with an optional per-component override), that controls from which date uptime history is shown to the public.

-       This setting should only affect what is displayed (the uptime bars and the calculated uptime percentage).

-       It should NOT delete or block on older data. Historical data stays stored and available for export and internal reporting.

-       Changing the date should never require deleting incidents or maintenances.

Why this matters:

We want to show a clean, relevant history to our customers (for example from 1 January 2025) without having to destroy older data that is valuable for internal analysis, SLA reporting and audits. Separating what is shown publicly from what is stored would also remove the need for manual cleanup across many components.

Thank you for considering this. Please let me know if you need more detail on our use case.