While the Checks tab logs every individual network ping, the Incidents tab aggregates consecutive failed checks into unified, continuous downtime events. This screen acts as your primary historical ledger for tracking website outages, calculating total downtime duration, and compiling data for Service Level Agreement (SLA) reports.




Log Controls & Data Export

At the top right of the incidents table, you have three powerful management tools:

  • Search Bar: Quickly locate specific outages by typing a date, error code, or specific cause keyword.
  • Filter Utility (funnel icon): Refine the list to display only specific incident types or isolate currently active outages from resolved historical events.
  • Export Utility (download icon): Click this icon to download a raw CSV/PDF report of your downtime history, making it easy to share uptime validation with clients or external stakeholders.

The Incident Triage Table

The dashboard translates complex outage windows into a highly scannable, five-column matrix:

Column

Description

Status Icon

A quick visual indicator of the event's lifecycle. A red exclamation mark (❗) signifies that the incident is currently active and the website remains offline. A green checkmark (🟢) confirms the issue has been fully resolved.

Cause

The primary trigger for the outage (e.g., HTTP 503, Connection Timeout, or No data if the server completely dropped the connection or rate-limited the agent, as seen with severe 429 errors). This text is a clickable blue hyperlink—clicking it dives deeper into the specific network headers and error logs captured during the exact moment of failure.

Duration

The aggregate length of the outage from the first failed check to the first successful recovery ping (e.g., 21 m and 24 s).

Started at

The precise timestamp (yyyy-mm-dd hh:mm:ss) when the monitoring agent first detected the website falling offline.

Ended at

The exact timestamp the website recovered and began returning 200 OK statuses. If the downtime is currently active, this column prominently displays a red Ongoing badge instead of a timestamp.

Action Menu (...)

The contextual menu on the far right allows you to manually acknowledge the incident, add internal notes for your engineering team, or delete the log entry entirely.