Rootly: Slack-dependent features degraded due to ongoing upstream Slack incident

Impact: criticalStatus: resolvedStarted 2026-05-14 14:01 UTCResolved 2026-05-14 16:00 UTC (2.0 h)4 updatesSource: stspg.io

Summary

Rootly’s Slack-dependent features were degraded by an upstream Slack incident, rated critical, starting 2026-05-14 14:01 UTC and lasting 1 h 58 min. On-Call, Mobile, and Web Platform remained fully operational; Rootly marked the incident resolved at 2026-05-14 16:00 UTC after the issue was resolved on Slack’s side.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: Slack App

Timeline of updates

identified2026-05-14 14:01 UTC
Slack-dependent features in Rootly are currently degraded due to an ongoing upstream Slack incident. We are continuing to monitor closely. See Slack's Status Page here: https://slack-status.com/2026-05/fe557ca05fdb64fa
identified2026-05-14 14:34 UTC
Slack-dependent features in Rootly are currently degraded due to an ongoing upstream Slack incident. Rootly is otherwise fully operational (On-Call, Mobile, and Web Platform). We will continue to monitor and will update as Slack recovers.
monitoring2026-05-14 14:49 UTC
Slack has acknowledged the incident: https://slack-status.com/2026-05/fe557ca05fdb64fa. We are continuing to monitor.
resolved2026-05-14 16:00 UTC
The issue has been resolved on Slack's side.

Rewindex changes for this incident

Critical incident: Slack-dependent features degraded due to ongoing upstream Slack incident 2026-05-14 14:01 UTC

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Rootly profile · Recent Rootly incidents · Markdown · JSON