ChangesRootlySlack-dependent features degraded due to ongoing upstream Slack incident
Rootly: Incident deleted: Slack-dependent features degraded due to ongoing upstream Slack incident
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what Rootly removed; blue is what they added. Muted text is unchanged context.
Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
Before captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
e4fcd2c784e2be8d…
History of this incident
Tuesday, October 27
1 rewrite
- Deleted by RootlyDeleted by the vendor
Slack-dependent features degraded due to ongoing upstream Slack incidentthis change
Thursday, May 14
1 incident change
- DegradationCritical incident
Slack-dependent features degraded due to ongoing upstream Slack incident
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.
Cite this
Incident deleted: Slack-dependent features degraded due to ongoing upstream Slack incident on Rootly’s status page, changed 2026-10-27 18:43 UTC (change 2 of 2).
- Title
- Incident deleted: Slack-dependent features degraded due to ongoing upstream Slack incident
- Vendor
- Rootly
- Date
- URL
- https://rewindex.com/change/d7cc4f73cd807bc