Runframe

Slack has resolved the upstream incident. Runframe’s Slack-dependent features have recovered, including incident channel creation and Slack update delivery. We are continuing to monitor for any residual impact.

Thu, 14 May 2026, 16:38 BST

Slack has identified a likely cause and is rolling back a recent configuration change. They are seeing signs of recovery, including lower error rates and stabilizing systems. We are continuing to monitor. Slack-dependent Runframe features may remain degraded until Slack’s incident is resolved.

Thu, 14 May 2026, 16:23 BST

Slack-dependent features in Runframe remain degraded. We are treating this as a major outage for affected Slack workflows while the upstream Slack incident continues. Core Runframe functionality outside of Slack-dependent workflows remains available.

Thu, 14 May 2026, 15:56 BST

Slack has confirmed an incident affecting their platform. We are monitoring Slack’s status page and assessing the impact on Runframe’s Slack integration. Slack status: https://slack-status.com/2026-05/fe557ca05fdb64fa

Thu, 14 May 2026, 15:43 BST

We are seeing issues with Runframe’s Slack integration and are investigating. Affected users may be unable to create incident channels or send updates to Slack. Other Runframe functionality remains available.

Thu, 14 May 2026, 15:41 BST