Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Split Status Page Block for React

A split status page for a hosted status service: the 90-day uptime and four components with their state at the start, the three most recent releases at the end, and a divider between them.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

A status page for React with Base UI, as a split. At the start, the title states the fleet's 90-day uptime, computed from the minutes of downtime typed per component, then a dot with "All systems operational" and the time it was checked, and four components as a list of rows: each has its name, a filled square with the word "Operational", and its own 90-day uptime. At the end, "Recent changes": three releases with a type tag (an icon and a word), a version, a fixed date, a linked title and one sentence, and a "View all releases" link. A solid divider runs from the page's top rule down between the halves with a + where they meet; on a phone the halves stack with the status first and a rule between. It's built from Guides, Badge, Status and Button, with your theme's tokens for every colour and CSS only for the entrance.

FAQ

How do I change the components and their uptime?

Edit COMPONENTS at the top of the file: each has a name and the minutes it was down in the last 90 days. A component's uptime is 1 - minutes down / minutes in 90 days, to two decimals, and the figure in the title is the same sum over all four, so they always agree. The numbers in the block are example data.

How would I show a component that is not operational?

The state is the word and a filled square at the end of the row. Add a state to the component, show a different word with a different glyph (a half square or a ring, never colour alone) and change the line above the list; the one real alert may use the status dot. Keep the word, so the row reads the same without the glyph.

Where do the recent changes come from?

From the typed RELEASES list: a kind (New, Improved, Fixed or Security, each an icon and a word), a version, an ISO date written as text from a month table so the server and the browser agree, a title that links to the release and one sentence. "View all releases" is a ghost button that takes your link. The button renders the link it's given with render, with nativeButton={false}.

How does the divider reach the top rule?

The page column is the grid itself, so the halves carry their own padding and the end half's divider starts at the top rule. A + marks where they meet on large screens; below lg the same crossing is drawn as a rule across the top of the stacked second half.

What changes on a phone?

The halves stack with the status first, so "All systems operational" and the components land on the first screen. A component row wraps its state and uptime under its name when they don't fit, and nothing scrolls sideways at 320 pixels.

Does it work in a right-to-left layout?

Yes. Percentages and versions are isolated so they stay in reading order, the arrow on "View all releases" mirrors, and the divider follows the page's direction.

  • Pro

    Tabbed Window Uptime History

    Incidents and uptime

    A tabbed window of ninety-day uptime for an uptime monitor: one tab per service, a large uptime figure that rolls to the new service, a strip of ninety daily bars and a three-row table of incidents.

  • Pro

    A health board for a hosting product: four service lanes of thirty daily cells, with a row of release pins above them that open a card of what shipped, and the month's uptime at the end of each lane.

  • Pro

    Release Band SLA Compliance

    Incidents and uptime

    A band of three release cells for a managed-service reporting product: uptime, p95 response and first reply with the target beside the actual, a check or a ring for each, and a breach count in each foot.

  • Pro

    Release Notes Changelog

    Spotlights and media

    One release written as a long article behind a split divider, with a sticky contents list that marks the section on screen and turns into a row of chips on a phone.

  • Pro

    Region Status Footer

    Trust and compliance

    A split footer for a webhook-relay API: a subscribe-to-updates popover at the start, a framed figure of three regions with latency and thirty-day bars at the end.

  • Pro

    An API's reliability record: a 30-day status grid with one flagged day, the computed uptime beside it, and a framed table of endpoints with volume, p95 latency and success rate.