Skip to content

Open-source status page, incident response and uptime monitoring

fix: blog post image (#1974)

Maximilian Kaskeec7c3c91e8a0
diff --git a/apps/web/public/assets/posts/status-page-is-politics/status-page-politics.png b/apps/web/public/assets/posts/status-page-is-politics/status-page-politics.png
new file mode 100644
index 000000000..5ba24d310
Binary files /dev/null and b/apps/web/public/assets/posts/status-page-is-politics/status-page-politics.png differ
diff --git a/apps/web/src/content/pages/blog/status-pages-is-politics.mdx b/apps/web/src/content/pages/blog/status-pages-is-politics.mdx
index 0e13f4685..78955e5f6 100644
--- a/apps/web/src/content/pages/blog/status-pages-is-politics.mdx
+++ b/apps/web/src/content/pages/blog/status-pages-is-politics.mdx
@@ -3,6 +3,7 @@ title: "Status Pages Are Politics"
description: "An always-green status page isn't a sign of reliability — it's a sign of opacity. Why the industry rewards dishonesty and what buyers should do about it."
author: "Maximilian Kaske"
publishedAt: "2026-03-12"
+image: "/assets/posts/status-page-is-politics/status-page-politics.png"
category: "education"
faq:
- question: "Why is an always-green status page a red flag?"