Skip to content
Feature

Incident history, notes and CSV export, weekly summary email

Every confirmed outage is stored as an incident with its start, end, cause and, when DNS changed beforehand, the likely cause. You can add a note of up to 500 characters, download incidents and individual checks as CSV, and every week an email summarises uptime, response time and incidents per monitor.

The incident list

In short: One row per outage: which monitor, when it started, how long it lasted, what caused it, and your note.

An incident opens when a second check confirms a failure and closes when a check passes again. Incidents are kept for 400 days, so a yearly review has the whole year. Open incidents are shown first, with a count in the navigation so you can see at a glance whether anything is down.

Notes

Each incident has a note field of up to 500 characters for what you found: "Disk full on db-1, cleared logs", "Host's network issue, their status page confirms". Notes stay with the incident and appear in the CSV export, so the next person who sees the same cause has the last fix next to it.

CSV exports

Open the file in a spreadsheet to work out downtime per month, send it to a host when you are arguing about an SLA, or keep it as a record.

ExportWhereWhat's in it
IncidentsIncidents page, Download CSVMonitor, started, resolved, duration, cause, likely cause, note
ChecksA monitor's page, Download CSVUp to 5,000 recent checks: time, result, status code, error, DNS, connect, TLS, time to first byte and total milliseconds

Uptime and response time on the monitor page

Every monitor shows uptime and average response time for the last 24 hours, 7 days and 30 days, built from hourly totals that are kept for 90 days on Starter and a year on Pro and Business. Recent checks are listed with every timing, so a slow server shows up as a growing time-to-first-byte long before it fails.

The weekly summary email

Once a week, starting a week after sign-up, the account owner gets one email: overall uptime across all monitors, the number of incidents, and a table with each monitor's uptime, average response time in milliseconds and incident count. A quiet week reads "A quiet week: 100% uptime across 12 monitors and no incidents." It can be turned off under Settings.

Questions

How long is incident history kept?

400 days for incidents and hourly statistics. Individual check results are kept for a shorter time; the hourly totals are what the uptime percentages are built from.

Can I export my uptime data?

Yes. The incidents list downloads as one CSV file, and each monitor's recent checks download as another, both from the app with no extra setup.

Who gets the weekly summary?

The workspace owner's confirmed email address, once every seven days. Turn it off or on under Settings.

Does the summary include cron jobs?

Yes. Heartbeats appear in the table with their uptime and incidents. They have no response time, since nothing is requested from them.

Keep the record, not just the alert.

Every outage with its cause, your notes, CSV when you need it, and a summary email every week. Free for 14 days, no card.

Start watching free

Updated October 8, 2026.