Skip to content
HonkWatch
PricingLocationsHonk RadarHelpAPI Log inGet started
All help topics

Getting started

  • Getting started
  • How checks work

Monitors

  • Which monitor to use
  • Website monitor
  • API monitor
  • Keyword monitor
  • Ping monitor
  • Port monitors (TCP and UDP)
  • DNS monitor
  • SSL certificate monitor
  • Domain expiry monitor
  • Third-party services
  • Page load monitor
  • Heartbeat monitor (cron jobs)
  • Maintenance windows
  • Incidents

Alerts

  • Setting up alerts
  • Email alerts
  • Slack
  • Microsoft Teams
  • Discord
  • Telegram
  • PagerDuty
  • ntfy
  • Webhooks
  • Zapier

Phone and desktop app

  • The phone and desktop app
  • App alerts not arriving

Status pages

  • Status pages
  • Status page on your own domain

Team and account

  • Team members
  • Plans and limits
  • API keys and the API
  • Your account

Troubleshooting

  • A monitor says down but my site works
  • I did not get an alert
  • Allowing our checks through a firewall
  • Questions and answers

Help / Monitors

Incidents

An incident is the record of one outage of one monitor. It opens when HonkWatch decides a monitor is really down, and closes when the monitor comes back up. Incidents drive your down and recovery alerts, and they are what your uptime figures are worked out from.

When an incident opens

One failed check does not open an incident. For most monitor types, two settings decide when it counts as down:

  • Down when this many locations agree: how many check locations must see the failure. The default is 2.
  • Each of them after this many failed checks in a row: how many times each of those locations must fail in a row. You can pick 1, 2 or 3. The default is 2.

You find both when you edit a monitor. How checks work explains this in more detail.

When the monitor is confirmed down, HonkWatch:

  1. opens an incident with the start time, the cause (for example a status code or a timeout) and the cities that saw it,
  2. sends a down alert to every alert channel that has down alerts turned on,
  3. emails the subscribers of any status page that shows the monitor, if they follow it.

If a monitor is edited or resumed while its incident is still open, that is treated as the same outage. No second incident opens and no second alert is sent.

When an incident closes

The incident closes when fewer locations than the Down when this many locations agree number still see it failing, and at least one sees it working. A recovery alert then goes out with how long it was down and what the cause was. Status page subscribers get an email that it is working again.

To skip the recovery alert for a monitor, edit it and untick Send a "back online" message when it recovers.

Acknowledge an incident

Acknowledging tells your team that someone is on it, and stops repeat alerts.

  1. Open the monitor's page. You can get there from Incidents by pressing acknowledge, or by pressing the monitor's name.
  2. In the Incidents card, find the ongoing incident.
  3. Optional: type a short note in the Note (optional) box, for example Host is restarting the server, back in 10 minutes.
  4. Press Acknowledge.

The incident now shows when it was acknowledged. You can acknowledge an incident once, while it is still open. After that the form goes away, so write the note before you press the button.

The note is public on any status page that shows this monitor. Write it for your users, and leave out anything private.

Repeat alerts

By default a down alert is sent once. To keep reminding people until someone reacts:

  1. Open the monitor and edit it.
  2. Set Repeat the down alert every (minutes, 0 = once), for example 30.
  3. Save the monitor.

The shortest repeat is 5 minutes: a smaller number is raised to 5. The longest is 10,080 minutes (one week): a bigger number is lowered to that. Each repeat says how long the monitor has been down. Repeats stop when the incident is acknowledged or closes, and they are held back during a maintenance window.

The Incidents page

Incidents lists incidents across all your monitors, newest first, up to the 300 most recent. Use All, Ongoing and Resolved to filter. Each row shows:

  • Monitor: press the name to open the monitor.
  • Started: in your own time zone, or UTC if JavaScript is off.
  • Lasted: how long it was down, or how long it has been down so far.
  • Cause: what the checks saw, with your note under it.
  • Seen from: the cities whose checks failed.
  • Acknowledged: when it was acknowledged, and how many alerts were sent if there was more than one.

A monitor's own page shows its 20 most recent incidents in the Incidents card. Status pages show the 10 most recent incidents for the monitors on the page.

Maintenance windows

An outage that starts during a maintenance window does not open an incident and does not count against uptime. If the monitor is still down when the window ends, the incident opens then, counted from the end of the window, and the down alert goes out.

Third-party services

For third-party service monitors, the outage time comes from the provider's own status source. If that source could not be read for part of the outage, the incident shows that the duration is unavailable instead of guessing.

If something looks wrong

  • An incident opened but the site was working. See A monitor says down but my site works.
  • The site was down but no incident opened. Check whether a maintenance window covered the monitor, and whether the monitor was paused. It may also have recovered before enough locations agreed.
  • Repeat alerts keep coming. Acknowledge the incident on the monitor's page.
  • No alert arrived for an incident. See I did not get an alert.
← Maintenance windows Setting up alerts →

Still stuck? Email [email protected] and say which guide you were following.