What Should an Outage Dashboard Say During a Feed Failure?
From the earlier reference collection. Read the current software blog.
During a feed failure, state what source is affected, when it last worked, what data remains visible, and what is known about the problem.
Identify the affected source
A generic “data unavailable” banner leaves readers guessing. Name the affected feed or service in language they recognize, and say which locations or metrics depend on it. If only one region is affected, do not make the entire dashboard appear broken. A precise scope helps people decide whether they can still use other parts of the page.
Describe what the dashboard observed rather than assigning blame without evidence. “No new readings received from the east station feed since 10:15 a.m.” is more defensible than “The provider is down” unless the provider has confirmed an outage.
Preserve the last known data carefully
If the last successful data remains useful, keep it available with a prominent stale label and timestamp. For example: “Showing last received report from 10:15 a.m.; newer reports are unavailable.” Do not let an old value retain the visual styling of a current reading. For time series, end the line at the last observation and show a gap rather than extending the value forward.
If the dashboard has no safe fallback, say that plainly. Hiding a missing value without explanation can look like zero activity or an intentional removal. A clear status is better than an empty chart that asks the reader to infer the cause.
Explain what can still be used
Tell readers which sections remain current and which are affected. If an outage feed is delayed but historical reports load normally, make that distinction explicit. Avoid broad assurances such as “all other data is current” unless freshness has been checked across those sources.
Include a useful next step when available: check back after a stated interval, consult an official source, or use a separate data download. Make sure any alternative is clearly identified as a different source so readers do not confuse it with the failed feed.
Update the message as conditions change
The status should change when new data arrives, and the page should not continue to display an obsolete incident notice after recovery. Record the last successful update and, if known, the time service resumed. If the cause remains unknown, say so rather than filling the gap with speculation.
A feed failure is a moment when dashboard communication matters most. A short, specific explanation preserves context, reduces mistaken conclusions, and helps readers understand what the remaining data can support.