Response Time Chart
Median and p99 latency as shadcn lines with the visible spike explained.
Median and p99 latency as shadcn lines with the visible spike explained.
Search blocks by description or jump to a page.
The source for every Marketing block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Response Time Chart publishes latency the way engineers read it. Median and p99 run as two shadcn lines across two weeks with a legend and millisecond axis, and the footnote does the honest work, naming where the data is sampled and explaining the visible spike, it was a deploy, the postmortem is linked. Performance transparency with its homework attached.
Built on ui/chart with a two key config, the data array wires to real monitoring. The median p99 pairing matters, medians comfort and tails confess, publishing both is what makes the chart engineering rather than marketing.
Reach for this block on status pages and developer trust pages below current-status-list, up answers if it works, this answers how well. Developer audiences specifically check for percentiles, a median only latency chart reads as hiding the tail.
A natural flow around it on a Marketing Pro page:
Before
After
One strong use is API latency percentiles from real monitors. Other series:
Tip: explain visible anomalies in the footnote before anyone asks, a named spike is reliability, an unnamed one is a question.