Skip to content

docs: add incident duration calculation and custom date sections #218

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
shiini2 merged 2 commits into from
Mar 17, 2026
Merged

docs: add incident duration calculation and custom date sections #218

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
10d8e7a
docs: add incident duration calculation and custom date sections
shiini2 Mar 17, 2026
9b6a873
docs: link to backfilling from duration section instead of duplicating
shiini2 Mar 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions communicate/status-pages/incidents.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,17 @@ 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.
Copy link
Copy Markdown
Contributor Author

@shiini2 shiini2 Mar 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently this will often be off by up to ~2 minutes because we get this from the backend then we cache it

Copy link
Copy Markdown
Contributor Author

@shiini2 shiini2 Mar 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure if we should specify this in the docs, I could probably eventually find a workaround for this

Copy link
Copy Markdown
Contributor

@thebiglabasky thebiglabasky Mar 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I wouldn't mention it yet?


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.

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

Whenever you post an incident update, Checkly can automatically send email notifications to users subscribed to your Status Page.
Expand Down