Incident Update Timeline
A split section pairing a communication promise and three bullet commitments with a live incident feed of phase chips, timestamps, and update text.
A split section pairing a communication promise and three bullet commitments with a live incident feed of phase chips, timestamps, and update text.
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
Incident Update Timeline shows how you communicate under pressure before anyone has to find out the hard way. The left column states the communication promise, first update within ten minutes and a new one at least every twenty, backed by three bullets on plain language, engineer authored updates, and nothing edited after the fact. The right column proves it with a real incident feed.
The updates are one array. Phase chips walk the rail from investigating to resolved, each with its timestamp preserved word for word. The active flag marks the resolved entry, filling its node and chip, so the eye lands on the ending first, the outcome before the story.
Reach for this block on status pages and trust centers where the question behind the SLA is really will you tell me when it breaks. A sample feed answers it more convincingly than a promise alone, buyers who have been left guessing during someone else's outage recognize the difference immediately.
A natural flow around it on a Marketing Pro page:
Before
After
One strong use is a preserved API incident feed. Other timelines:
Tip: keep the resolved entry as the active node, ending on the recovery is what makes the feed reassuring rather than tense.