Skip to content

Open-source status page, incident response and uptime monitoring

chore: theme explorer posts (#1510)

Maximilian Kaske02cb4893b9c6
diff --git a/apps/docs/astro.config.mjs b/apps/docs/astro.config.mjs
index 54b2aeb6e..359f7f719 100644
--- a/apps/docs/astro.config.mjs
+++ b/apps/docs/astro.config.mjs
@@ -71,6 +71,10 @@ export default defineConfig({
label: "Best Practices for Status Pages",
slug: "concept/best-practices-status-page",
},
+ {
+ label: "Uptime Calculation and Values",
+ slug: "concept/uptime-calculation-and-values",
+ },
{
label: "Uptime Monitoring as Code",
slug: "concept/uptime-monitoring-as-code",
diff --git a/apps/docs/src/content/docs/concept/uptime-calculation-and-values.mdx b/apps/docs/src/content/docs/concept/uptime-calculation-and-values.mdx
new file mode 100644
index 000000000..24ecdd46c
--- /dev/null
+++ b/apps/docs/src/content/docs/concept/uptime-calculation-and-values.mdx
@@ -0,0 +1,70 @@
+---
+title: Uptime Calculation and Shared Values
+---
+
+Let’s face it - uptime values can be a complete lie if they’re not properly connected to monitoring.
+
+We want to make uptime transparent and configurable. You decide how your uptime is calculated and which values you want to share on your status page.
+When monitoring an endpoint, a check can end up in one of three states:
+
+- ✅ Success – everything’s fine
+- ⚠️ Degraded – slow or partially failing
+- ❌ Down – no response or full failure
+
+We now offer multiple types of uptime calculation:
+- **Absolute** (default): derived directly from your monitoring data
+ - **Duration**: aggregated from the incidents duration
+ - **Requests** (default): aggregated from the request values
+- **Manual**: for teams that prefer full control over what’s shown
+
+**TL;DR**
+
+| Type | Source of Truth | What Users See | Best For |
+|-------------|----------------------|-------------------------------------|----------------------------------|
+| **Duration** (Absolute) | Incident duration | Time based uptime, proportional colors | Accurate long-term view |
+| **Request** (Absolute) | Every ping result | Request-based uptime % | Real-time reflection |
+| **Manual** | Manually set status | Controlled, narrative updates | Transparency without monitoring |
+
+<br />
+
+Let’s break them down!
+
+## Absolute Type
+
+The absolute type calculates uptime based on actual monitoring results. It’s the most accurate reflection of what’s really happening, and comes in two variants: _Duration_ and _Request_.
+Both of these share real data with your users - incidents, degraded states, and historical uptime - but they differ in how they aggregate and display that data.
+
+---
+
+### Duration
+
+The duration value is calculated from the **total monitoring time and the duration of incidents**.
+
+In simple terms: `uptime = (total time - incident duration) / total time`
+
+This means uptime is based on how long something was down, not how many checks failed. Only incident durations are included in the calculation. Temporary single-region ping failures (e.g., one location failing once) are not propagated to users - because these often don’t represent a real outage. That’s also why we recommend at least three locations per monitor for redundancy. The proportional colors in the status bar are drawn from these duration values. Hovering over a day shows both incidents and status reports, so users can explore what happened.
+
+---
+
+### Request
+
+The request value is more straightforward - it looks at each ping result individually. **Every check we run contributes to your uptime score**.
+
+In simple terms: `uptime = (success + degraded - error) / total requests`
+
+This is the current default mode for most openstatus users. It’s simple, data-driven, and updates immediately as new results come in. Like with duration, hover cards display incidents and status reports, giving your users a quick overview of recent events.
+
+---
+
+## Manual Type
+
+The manual type is for teams who want to **fully control what’s shown** on your status page, without relying on automatic checks.
+By default, your monitor is marked operational. You can then manually create and publish status reports whenever you want to reflect changes — independent of any monitoring data.
+
+This is ideal if:
+- you don’t have synthetic monitoring set up yet,
+- or you’re sharing updates that aren’t tied to uptime (e.g., service degradation due to external dependencies).
+
+In this mode, all displayed uptime values and statuses come from your shared data, not from active pings.
+
+> **Note**: the values you are defining are attached to a status page. You cannot change the per monitor.
\ No newline at end of file
diff --git a/apps/web/public/assets/posts/introducing-status-page-theme-explorer/dashboard-status-page-redesign.png b/apps/web/public/assets/posts/introducing-status-page-theme-explorer/dashboard-status-page-redesign.png
new file mode 100644
index 000000000..80587b8ec
Binary files /dev/null and b/apps/web/public/assets/posts/introducing-status-page-theme-explorer/dashboard-status-page-redesign.png differ
diff --git a/apps/web/public/assets/posts/introducing-status-page-theme-explorer/palette.png b/apps/web/public/assets/posts/introducing-status-page-theme-explorer/palette.png
new file mode 100644
index 000000000..a31a41212
Binary files /dev/null and b/apps/web/public/assets/posts/introducing-status-page-theme-explorer/palette.png differ
diff --git a/apps/web/public/assets/posts/introducing-status-page-theme-explorer/theme-explorer-supabase.png b/apps/web/public/assets/posts/introducing-status-page-theme-explorer/theme-explorer-supabase.png
new file mode 100644
index 000000000..723aecc59
Binary files /dev/null and b/apps/web/public/assets/posts/introducing-status-page-theme-explorer/theme-explorer-supabase.png differ
diff --git a/apps/web/src/app/(pages)/(content)/play/page.tsx b/apps/web/src/app/(pages)/(content)/play/page.tsx
index 38b885baa..c611df99b 100644
--- a/apps/web/src/app/(pages)/(content)/play/page.tsx
+++ b/apps/web/src/app/(pages)/(content)/play/page.tsx
@@ -75,6 +75,12 @@ const playgrounds: CardProps[] = [
"Calculate uptime SLA percentages, allowed downtime, and service availability metrics.",
icon: ShieldCheck,
},
+ {
+ href: "https://themes.openstatus.dev",
+ title: "Theme Explorer",
+ description: "Explore our collection of themes for your status page.",
+ icon: Palette,
+ },
{
href: "https://light.openstatus.dev",
title: "Vercel Edge Ping",
diff --git a/apps/web/src/components/layout/marketing-footer.tsx b/apps/web/src/components/layout/marketing-footer.tsx
index 50b172b5b..d7528b791 100644
--- a/apps/web/src/components/layout/marketing-footer.tsx
+++ b/apps/web/src/components/layout/marketing-footer.tsx
@@ -84,6 +84,10 @@ export function MarketingFooter({ className }: Props) {
<FooterLink href="/play/checker" label="Speed Checker" />
<FooterLink href="/play/curl" label="cURL Builder" />
<FooterLink href="/play/uptime-sla" label="Uptime SLA Calculator" />
+ <FooterLink
+ href="https://themes.openstatus.dev"
+ label="Theme Explorer"
+ />
<FooterLink href="https://openstat.us" label="All Status Codes" />
<FooterLink
href="https://light.openstatus.dev"
diff --git a/apps/web/src/content/posts/introducing-status-page-theme-explorer.mdx b/apps/web/src/content/posts/introducing-status-page-theme-explorer.mdx
new file mode 100644
index 000000000..c8d33f97b
--- /dev/null
+++ b/apps/web/src/content/posts/introducing-status-page-theme-explorer.mdx
@@ -0,0 +1,85 @@
+---
+title: "Introducing: The Status Page Theme Explorer"
+description: Customize and build your own status page experience.
+author:
+ name: Maximilian Kaske
+ url: https://x.com/mxkaske
+ avatar: /assets/authors/max.png
+publishedAt: 2025-10-28
+image: /assets/posts/introducing-status-page-theme-explorer/palette.png
+tag: education
+---
+
+Who uses status pages the most? _Mainly Developers_. And to match their nerdiness, we’re adding more font-mono into the game. We’ve collaborated with [@aliszu](https://x.com/aliszu) to rebuilt our status page experience from the ground up and are providing you with more flexibility and control.
+
+A status page should feel at home with your brand - without requiring constant maintenance. It should also let you decide exactly how much data you want to share and at what level of detail.
+The status-page is now a standalone app, fully separated from our main web project - continuing the great split after the [dashboard extraction](/blog/new-dashboard-we-are-so-back).
+
+**TL;DR**: create your own theme on [themes.openstatus.dev](https://themes.openstatus.dev/?t=supabase&b=true) + more page configuration
+
+---
+
+### Theme Explorer
+
+From day one, we’ve built with [shadcn/ui](https://ui.shadcn.com), and we’re sticking to it: same `CSS` variables, same philosophy. And luckily, it makes it easy to change themes!
+
+<ImageWithCaption
+ src="/assets/posts/introducing-status-page-theme-explorer/theme-explorer-supabase.png"
+ alt="Supabase Theme"
+ caption="Supabase Theme"
+/>
+
+We’ve now extended those variables with custom ones for states like _maintenance_, _success_, and _degraded_, among others.
+
+We’re starting with four themes:
+- our new default openstatus (Squared) theme,
+- a legacy rounded theme close to the current one,
+- a [Supabase](https://supabase.com) theme, and
+- a GitHub high-contrast theme.
+
+And here’s the fun part: **you can contribute your own themes**.
+
+Go to [themes.openstatus.dev](https://themes.openstatus.dev), open the **Theme Builder** by toggling the sidebar (e.g. `cmd + b`) and play around with different styles.
+
+Once you’re happy with your setup:
+- Copy the configuration to your clipboard.
+- Create a new theme file with that config.
+- Append its ID to the `THEMES_LIST`.
+- Open a PR to contribute it!
+
+
+We have a comprehensive [README](https://github.com/openstatusHQ/openstatus/tree/main/packages/theme-store) with more context.
+
+We’ve also updated the local seed setup — making it easier to get started and preview your theme right away at http://localhost:3000/status.
+
+> Note, that we won’t accept every submission. We want to keep themes high-quality and recognizable - no random or off-brand experiments (sorry Santa 🎅).
+
+To try the new experience on your own status page, **opt in to the redesign (beta)** ([Tutorial > How to configure a status page](https://docs.openstatus.dev/tutorial/how-to-configure-status-page/)) and select your preferred theme. Newly created pages will automatically opt in to the new theme.
+
+---
+
+### Shared Values Configuration
+
+There’s more configuration.
+
+We’ve heard from teams who wanted to **manually update their status page without connecting any synthetic monitors**. While we still believe _monitoring + transparency go hand in hand_, we don’t want to exclude users who just want to share updates directly.
+
+<ImageWithCaption
+ src="/assets/posts/introducing-status-page-theme-explorer/dashboard-status-page-redesign.png"
+ alt="Status Page Dashboard Settings"
+ caption="Status Page Dashboard Settings"
+/>
+
+With the new _“manual”_ type, you can only share status reports you are creating, regardless of the derived synthetic monitoring values.
+
+All metrics, including uptime, will refer to your shared (manual) data.
+To understand the underlying concept, check out our docs:
+[Concepts > Status Values and Uptime Calculation](https://docs.openstatus.dev/concept/uptime-calculation-and-values/) - where we explain how these values are derived, including details about the default _“absolute”_ type (which takes duration and request values to aggregate the uptime data).
+
+---
+
+We’re not done yet. Next up: _grouped monitors_, _white-labeling support_, and _private themes_ - all coming to the new status page configuration soon.
+
+> Expect all status pages to be fully migrated to the new version early next year.
+
+If you’re already using openstatus - or planning to - and feel a status page feature is missing, we’d love to hear from you. Contact us via [[email protected]](mailto:[email protected]) or by joining [Discord](https://openstatus.dev/discord).
\ No newline at end of file
diff --git a/packages/theme-store/README.md b/packages/theme-store/README.md
index ae25c9670..96ea4b930 100644
--- a/packages/theme-store/README.md
+++ b/packages/theme-store/README.md
@@ -98,7 +98,7 @@ Create a pull request with your theme for review.
## Design Guidelines
### Color System
-- Use **OKLCH color space** for better perceptual uniformity
+- Use **OKLCH color space** for better perceptual uniformity (but all css color specs are supported)
- Ensure sufficient contrast ratios for accessibility
- Test both light and dark modes thoroughly