Resend — Service status

Analytics DashboardSee it liveresend-status.com

A service-status page summarizes current health and shows uptime history for individual services.

Resend — Service status — captured interface — Viewport capture · opening screen

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

Dashboards

Why this pattern works

Communicate system health with a readable overall summary and drill-down service history.

Design notes

Surface: Service status
Navigation: Report and subscription actions sit in the top bar.
Layout: A constrained central column stacks overall status, service rows, and a history action.
Density: Headline metrics are spacious; supporting chart labels and rankings use denser alignment.
Color: Charcoal surfaces, green operational indicators, and occasional warm historical incident markers.
Type: Bright service labels and small muted percentages make repeated uptime rows easy to compare.
Pattern: Communicate system health with a readable overall summary and drill-down service history.
States: Capture-time operational summary and per-service uptime bars; conditions may change.
Don't: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

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: Resend — Service status
Source: https://resend-status.com/
Swipefile reference: https://swipefile.design/ref/resend-status/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## 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: Report and subscription actions sit in the top bar.
- layout: A constrained central column stacks overall status, service rows, and a history action.
- density: Headline metrics are spacious; supporting chart labels and rankings use denser alignment.
- color: Charcoal surfaces, green operational indicators, and occasional warm historical incident markers.
- typography: Bright service labels and small muted percentages make repeated uptime rows easy to compare.
- pattern: Communicate system health with a readable overall summary and drill-down service history.
- states: Capture-time operational summary and per-service uptime bars; conditions may change.
- dont: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

Useful for: Communicate system health with a readable overall summary and drill-down service history.

## 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: Communicate system health with a readable overall summary and drill-down service history.

Resend — Service status

Make it your own

Keep exploring