Search blocks by description or jump to a page.
Provider status board where each connected service shows live status, response time, and last incident, plus an impact note on the degraded provider.
The source for every Application block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
Connected Services Status is an upstream provider status board for the third party services an app depends on. The header reads 3 of 4 providers operational, checked 40 seconds ago, with a Notify me on incidents button. Each row shows a two letter mark, the provider name, its last incident line, the current API response time, and a status dot with an Operational or Degraded label. The one degraded provider, Slack, expands to a What this means for you note explaining that channel notifications are queued and will send once delivery recovers, with a vendor recovery estimate and the count of queued notifications.
Services are one const array with a degraded flag that drives both the status weight and whether the impact note renders. The impact copy is written for the person reading it, what is queued and what still works, rather than a raw vendor status string, so the board answers the support question before it is asked.
Reach for this block on a system status page or an integration settings screen, wired to each provider public status feed and your own request success rates. Show it when a dependency is degraded so users understand the delay is upstream, not your app.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the upstream dependency board. Other status surfaces:
Tip: the impact note is the whole value here; a status dot alone still generates tickets, a plain explanation of what is queued prevents them.