Use Download incident data on the Incident Details page to save the incident and its available supporting evidence as a JSON file.
What the export contains
Depending on what was recorded and is still retained, the file can include:
- Monitor name, URL, method, and non-secret configuration details.
- Incident type, state, start, recovery, duration, and diagnosis.
- Request and response summary.
- Regional confirmation evidence.
- Stored DNS, TCP, TLS, and HTTP diagnostics.
- Grouped incident activity.
- A bounded sample of nearby checks and alert records.
The export reflects the information available when you download it. It does not trigger a new check or rerun diagnostics.
What the export does not contain
The JSON file does not expose saved Basic Authentication passwords, encrypted request-secret data, or custom-header secret values. Response bodies are not captured for incident display or export.
Checks and alerts in the export are bounded supporting evidence, not an unlimited historical archive. Use Detailed Logs and CSV export when you need the full raw-check result set still within retention.
Download the file
- Open the monitor's incident.
- Select Download incident data.
- Wait while the additional incident sections load.
- Save the generated
.jsonfile through your browser.
If the download fails, confirm you are still signed in and retry. Very old incidents can produce a smaller file because supporting checks or alerts have expired.
Open and use JSON
JSON is a structured text format. You can open it in a code editor, import it into a compatible analysis tool, attach it to an internal support case, or provide it to a trusted hosting or development team.
The incident export is not a PDF report, invoice, formal service-level agreement, or proof of the website's internal root cause.
Review before sharing
Although saved request secrets are excluded, the file can contain:
- Monitored URLs and paths.
- Public IP addresses resolved during diagnostics.
- Timestamps and regional evidence.
- HTTP headers selected for troubleshooting.
- Operational errors and account-specific monitor information.
Review the file and your organization's disclosure rules before sharing it outside your team.