Historical report exports
StatusGator lets you export historical monitoring data across all plans. Use this feature to analyze service reliability or negotiate with vendors using data-backed insights.
How to export historical data
- Click Reports in your dashboard menu.
- Choose one of four report types:
- Board history – Lists all incidents affecting your monitors within a selected timeframe.
- All status changes – Shows raw monitor status transitions (e.g., up → down) with timestamps.
- Component status pages – Includes component-level changes for deeper insight.
- Component summary – Summarizes each component's downtime or warning periods over time.
- Select the date range.
- Download the table in your preferred format—JSON, CSV, or Excel—by clicking the download icon located at the bottom right of the table.
Available coverage
- By default, you’ll get data starting from the first of the month you signed up.
- Need older data? Reach out to support—we’re happy to help!
Component status changes
When exporting reports that include component-level data, each change entry will contain the following fields:
- name – The name of the service monitor.
- recorded_at – The time (UTC) we detected the change to the status page.
- from – The overall service status before the change.
- to– The overall service status after the change. This reflects the "worst" component status.
- Example: if one component is down and another is warn, the overall service status will be down.
- message – A headline or summary of the incident from the status page.
- details – More detailed incident information, if provided by the status page.
- group_name – If the status page organizes components into groups (e.g., product or region), this field shows the group.
- name – The component name (feature, product, or region).
- component_from – The status of the component before the change.
- component_to – The status of the component after the change.
Uses for historical reports
- Create uptime/downtime summaries for team reporting.
- Identify recurring issues and monitor trends.
- Support vendor discussions with concrete, time-stamped outage data.