Orvain UI

Service uptime

Service uptime is a Metrics block from Orvain UI, built for React and Vue with a matching Figma frame.

Best for

The health of a few services day by day, with the incidents behind it

Anatomy

Period control · uptime with its change · incidents, time affected and what is degraded now · a tick per day per service · recent incidents with their state

MCPConnect the MCP server

Service uptime

99.98 %
down −0.01 pt, worse vs previous 90 days
  • Incidents 6
  • Affected 3h 12m
  • Now 1 degraded

  • No incidents
  • Degraded
  • Outage
Service uptime, last 90 days
DateServiceIncidentKindDuration
Sat 3 OctAPIElevated error rateOutage12 min
Mon 14 SepDashboardSlow page loadsDegraded1h 5m
Wed 21 OctWebhooksDelayed deliveriesDegraded38 min
Sun 8 NovWebhooksDelayed deliveriesDegraded46 min so far
Sun 30 AugAuthSign-in delaysDegraded22 min
Fri 6 NovPaymentsCard payments failing for some EU customersOutage9 min

Recent incidents

  • 8 NovDelayed deliveriesWebhooks · degraded · 46 min so farInvestigating
  • 6 NovCard payments failing for some EU customersPayments · outage · 9 minResolved
  • 21 OctDelayed deliveriesWebhooks · degraded · 38 minResolved

In the Orvain Library

Get Service uptime for your product

The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.

  • React
  • Vue
  • Figma frame
  • Orvain MCP
Get all accessHow the MCP works

About this block

Part of Metrics

What’s inside

05parts

The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.

  1. Period control
  2. Uptime with its change
  3. Incidents, time affected and what is degraded now
  4. A tick per day per service
  5. Recent incidentswith their state

Responsive behaviour

640 px

Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.

1440pxDesktop · 12 columns

When to use it

Where Metrics earns its place

Reach for Metrics

  • The top row of a dashboard, where each tile answers a single question
  • A report someone scans before deciding whether to open the table underneath
  • Comparing two series across a few categories, with a legend that can switch one off
  • Looking for a pattern across two axes, such as hour against weekday

Reach for something else

  • The reader needs the individual records: a chart shows shape and a table shows rows, so link one to the other rather than asking the chart to do both
  • There are only two or three values to compare; write them as a sentence, because a chart of three bars costs more attention than it returns
  • An operational signal that has to be acted on within seconds: a status page or an alert is the right surface, since a trend chart is read rather than watched

Accessibility

06to keep

What the block ships with. Hold on to these as you make it yours.

  • Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
  • Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
  • More than colourA state never rides on colour alone; a mark or a word goes with it.
  • Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
  • Calm motionFor visitors who ask for reduced motion, things simply appear.
  • Room to hitTargets stay at least 24px, with space between neighbours.

Notes for AI

1 line

Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.

Add the Orvain “Service uptime” block to this page: period control, uptime with its change, incidents, time affected and what is degraded now, a tick per day per service, recent incidents with their state.

Works in
Connect the MCP

Questions about Service uptime.

What is the Service uptime block?

Service uptime is a Metrics block from Orvain UI, built for React and Vue with a matching Figma frame. Best for the health of a few services day by day, with the incidents behind it.

What is the Service uptime block made of?

Is the Service uptime block responsive?

Is the Service uptime block accessible?

How do I add the Service uptime block to my project?

When should I not use a Metrics block?

Previous← Sign-up funnel

More Metrics blocks

All Metrics

Metric card

One headline figure with the months behind it: point at a month and it becomes the figure

Monthly rows

A short run of months you read down, like a table that draws

Ranked bars

Two series across a few categories: a legend that also switches them off

Day stack

A week of tracked time: what was booked and what was left

Donut breakdown

Where a total went: five parts at most, each named beside its share

Area trend

A running level over a year, with what is forecast set apart

Launch plan

A plan of tasks over weeks: what is done, what is late and where today falls

Hour heatmap

When in the week people show up, hour by hour

Diverging months

Money in against money out, month by month, with the balance

KPI card row

Four headline numbers over the same period, side by side

Figure strip

A few related figures read as one line, each against the period before

This week vs last week

A day-by-day comparison with the week before

Forecast with a target

Whether the year will land on its goal, with the likely range

Latency

A response time against its limit, with the traffic behind it

Noise level

A live reading on a fixed scale, from low to high

Score gauge

A score out of a total that is built from parts

Sign-up funnel

People moving through ordered steps, and who left at each

The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.