Linear — Service status

Analytics DashboardSee it livestatus.linear.app

A public status page pairs current service health with recent incident history.

Linear — Service status — captured interface — Page excerpt · scroll inside to explore

Source capture · 2026-09-04Open full image ↗

Dashboards

Why this pattern works

Keep the current state prominent and make historical updates easy to scan.

Design notes

Surface: Service status
Navigation: History and status sections support scanning from current state to prior updates.
Layout: A service-health overview precedes dated operational and incident information.
Density: Use consistent spacing within repeated information so headings, values, and secondary details remain easy to compare.
Color: A restrained status page with clear text hierarchy and semantic health indicators.
Type: Use a clear type hierarchy for the page title, primary content, and supporting labels.
Pattern: Keep the current state prominent and make historical updates easy to scan.
States: Public service-status snapshot at capture time; current availability may differ.
Don't: Do not copy brand assets or sample records. Preserve keyboard access and design empty, loading, and error states for the actual task.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Linear — Service status
Source: https://status.linear.app/
Swipefile reference: https://swipefile.design/ref/linear-status/
Captured: 2026-09-04. This is a dated reference, not a claim about the current live product.
Capture scope: a page excerpt. Do not infer unseen sections or interactions.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Service status
- nav: History and status sections support scanning from current state to prior updates.
- layout: A service-health overview precedes dated operational and incident information.
- density: Use consistent spacing within repeated information so headings, values, and secondary details remain easy to compare.
- color: A restrained status page with clear text hierarchy and semantic health indicators.
- typography: Use a clear type hierarchy for the page title, primary content, and supporting labels.
- pattern: Keep the current state prominent and make historical updates easy to scan.
- states: Public service-status snapshot at capture time; current availability may differ.
- dont: Do not copy brand assets or sample records. Preserve keyboard access and design empty, loading, and error states for the actual task.

Useful for: Keep the current state prominent and make historical updates easy to scan.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Keep the current state prominent and make historical updates easy to scan.

Linear — Service status

Make it your own

Keep exploring