rewindex

ChangesRootlySlack Performance Degradation (Upstream Issue)

Rootly: Incident deleted: Slack Performance Degradation (Upstream Issue)

Incident deletedDeleted by vendor (rule)Changed stspg.io (opens in new tab)
Summary

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.

RemovedTitle#1
Before: Slack Performance Degradation (Upstream Issue)
After: removed
RemovedImpact#2
Before: minor
After: removed
RemovedStatus#3
Before: resolved
After: removed
RemovedStart time#4
Before: 2025-11-07 02:32 UTC
After: removed
RemovedResolved time#5
Before: 2025-11-07 05:39 UTC
After: removed
RemovedAffected components#6
Before: Slack App
After: removed
RemovedUpdateinvestigating#7
Before: We’re currently observing degraded Slack performance due to an upstream issue with Slack. You can follow updates directly from Slack here: https://slack-status.com/2025-11/66f5fbbfdb8d6f73
After: removed
RemovedUpdateidentified#8
Before: It appears Slack has identified the issue and is implementing a fix. We are continuing to monitor here: https://slack-status.com/2025-11/66f5fbbfdb8d6f73.
After: removed
RemovedUpdateresolved#9
Before: This incident has been resolved.
After: removed

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.

History of this incident

YesterdayTuesday, October 27Tue, Oct 27

1 rewrite

All Rootly changesRootly profileMarkdownJSON