From 10d8e7a6f884c728362727830c3bf5ff088b78d4 Mon Sep 17 00:00:00 2001 From: manel Date: Tue, 17 Mar 2026 07:53:09 +0100 Subject: [PATCH 1/2] docs: add incident duration calculation and custom date sections --- communicate/status-pages/incidents.mdx | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/communicate/status-pages/incidents.mdx b/communicate/status-pages/incidents.mdx index c0e8d77c..72d6e836 100644 --- a/communicate/status-pages/incidents.mdx +++ b/communicate/status-pages/incidents.mdx @@ -43,6 +43,24 @@ From there, you can: * Change the incident severity * Delete the incident entirely +## Incident duration + +Incident duration measures the actual downtime of your service. It is calculated based on the timestamps of your incident updates: + +- **Resolved incidents**: Duration is measured from the first update to the first resolved update that closed the incident. If the incident was later re-opened and resolved again, the duration extends to the final resolved update. +- **Ongoing incidents**: Duration is measured from the first update to the current time. + +For example, if an incident was opened at 10:00, resolved at 10:30, then re-opened at 11:00 and resolved again at 11:30, the duration would be 1 hour 30 minutes (10:00 → 11:30). However, if the incident was resolved at 10:30 and a second resolved update was added later without re-opening, the duration remains 30 minutes. + +### Adjusting incident duration with custom dates + +Each incident update has a public date that determines when the update is considered to have occurred. You can edit this date to adjust the incident timeline and duration. This is useful when: + +- You need to correct the start time of an incident that was reported late. +- You want to set an accurate resolved time for an incident that was resolved before the update was posted. + +To change an update's public date, edit the incident update and select a custom date and time. + ## Incident notifications Whenever you post an incident update, Checkly can automatically send email notifications to users subscribed to your Status Page. From 9b6a87338503348f7b6a6ea6537ff2bc8e56d0e1 Mon Sep 17 00:00:00 2001 From: manel Date: Tue, 17 Mar 2026 08:00:30 +0100 Subject: [PATCH 2/2] docs: link to backfilling from duration section instead of duplicating --- communicate/status-pages/incidents.mdx | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/communicate/status-pages/incidents.mdx b/communicate/status-pages/incidents.mdx index 72d6e836..82da53cc 100644 --- a/communicate/status-pages/incidents.mdx +++ b/communicate/status-pages/incidents.mdx @@ -52,14 +52,7 @@ Incident duration measures the actual downtime of your service. It is calculated For example, if an incident was opened at 10:00, resolved at 10:30, then re-opened at 11:00 and resolved again at 11:30, the duration would be 1 hour 30 minutes (10:00 → 11:30). However, if the incident was resolved at 10:30 and a second resolved update was added later without re-opening, the duration remains 30 minutes. -### Adjusting incident duration with custom dates - -Each incident update has a public date that determines when the update is considered to have occurred. You can edit this date to adjust the incident timeline and duration. This is useful when: - -- You need to correct the start time of an incident that was reported late. -- You want to set an accurate resolved time for an incident that was resolved before the update was posted. - -To change an update's public date, edit the incident update and select a custom date and time. +You can adjust the incident duration by editing the public date on incident updates, or by [backfilling an incident](/communicate/status-pages/incidents#backfilling-an-incident) with custom timestamps. ## Incident notifications