Skip to content

Open-source status page, incident response and uptime monitoring

feat: changelog auto-resolved-incidents (#676)

Maximilian Kaske2075793ee6fd
diff --git a/apps/web/public/assets/changelog/auto-resolved-incidents.png b/apps/web/public/assets/changelog/auto-resolved-incidents.png
new file mode 100644
index 000000000..e24739ab9
Binary files /dev/null and b/apps/web/public/assets/changelog/auto-resolved-incidents.png differ
diff --git a/apps/web/src/content/changelog/auto-resolved-incidents.mdx b/apps/web/src/content/changelog/auto-resolved-incidents.mdx
new file mode 100644
index 000000000..79fce42c0
--- /dev/null
+++ b/apps/web/src/content/changelog/auto-resolved-incidents.mdx
@@ -0,0 +1,18 @@
+---
+title: Auto Resolved Incidents
+description: Automatically resolve incidents when your endpoint is back.
+image: /assets/changelog/auto-resolved-incidents.png
+publishedAt: 2024-02-19
+---
+
+We have added auto-resolved incidents to the incident management feature. Now,
+once your endpoint is back up and running i.e. _more than 50% of the regions are
+not failing_, the incident will be automatically resolved. The time between the
+creation and resolution of the incident will be marked as downtime on the status
+page.
+
+Additionally, the calculated `p95` latency over a day has been removed. It is
+costly to calculate and was not providing much value.
+
+Instead, we are thinking of adding a chart that shows the latency of the last X
+days/hours. If you have ideas, [let us know](/discord)!