Changes / Rootly / Slack-dependent features degraded due to ongoing upstream Slack incident
Rootly: Critical incident: Slack-dependent features degraded due to ongoing upstream Slack incident
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 diff below (Sol; type: incident degradation). Check the diff before relying on it.
What changed
Before: not present
After: Slack-dependent features degraded due to ongoing upstream Slack incident
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-05-14 14:01 UTC
Before: not present
After: 2026-05-14 16:00 UTC
Before: not present
After: Slack App
Before: not present
After: 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
Before: not present
After: 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.
Before: not present
After: Slack has acknowledged the incident: https://slack-status.com/2026-05/fe557ca05fdb64fa. We are continuing to monitor.
Before: not present
After: The issue has been resolved on Slack's side.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Slack-dependent features degraded due to ongoing upstream Slack incident (this change) 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. | Major incident |