Uptime status

Arrow leftorArrow right

Inspects the previous or next day on a service strip, or the previous or next half hour on the latency chart.

Page uporPage down

Jumps a week on a service strip.

HomeorEnd

Jumps to the first or latest point.

EnterorSpace

Selects the focused service so the latency chart follows it.

Escape

Clears the inspected day or point.

• Each strip is a focusable role="group" labelled with the service and described by its uptime summary.
• The latency chart has a text summary as its label, and polite live regions read out the inspected day or point.
• Incident headers are disclosure buttons with aria-expanded and aria-controls, and service rows use aria-pressed.

• The selected service highlight moves between rows with a shared layout spring, and the tooltip follows the pointer on a spring.
• The latency line morphs between services, and status text swaps with a short rise.
• Reduced motion removes the springs and moves the tooltip directly.

• Below an 860px container the response time chart and incidents stack into one column.
• Below 560px row details and uptime labels hide and the status button moves under the summary.
• Strips and the latency chart use touch-action pan-y, so touch scrubbing keeps vertical scroll.

• Each service draws 90 SVG bars; many services on one page means hundreds of rects, which is fine but not free.
• Chart widths follow ResizeObservers; there is no animation loop.

• Use for a public or internal status page.
• Replace services, daily history, latency samples and incidents in uptime-data.ts; bars, percentages and scales derive from them.
• Remove or rewire the simulated incident trigger to your monitoring feed.

The full library index for assistants is at /llms.txt.