Rootly incident
Slack-dependent features degraded due to ongoing upstream Slack incident
Resolved on May 28, 2026, affecting Rootly Production Status service.
May 27, 23:25 PDT Resolved - This incident has been resolved. May 27, 21:36 PDT Update - We are continuing to monitor. We are not currently seeing any impact on our Slack integration. You can follow along on Slack's status page here: https://slack-status.com/2026-05/46d9d5d41fbedd9f May 27, 17:23 PDT Monitoring - We are continuing to monitor as error rates decrease. You can follow along on Slack's status page here: https://slack-status.com/2026-05/46d9d5d41fbedd9f May 27, 16:52 PDT Investigating - We are experiencing increased error rates with our Slack integration due to a Slack incident. You can follow along on Slack's status page here: https://slack-status.com/2026-05/46d9d5d41fbedd9f
Affected components
Update timeline
- resolved May 28, 2026, 06:25 AM UTC
May 27, 23:25 PDT Resolved - This incident has been resolved. May 27, 21:36 PDT Update - We are continuing to monitor. We are not currently seeing any impact on our Slack integration. You can follow along on Slack's status page here: https://slack-status.com/2026-05/46d9d5d41fbedd9f May 27, 17:23 PDT Monitoring - We are continuing to monitor as error rates decrease. You can follow along on Slack's status page here: https://slack-status.com/2026-05/46d9d5d41fbedd9f May 27, 16:52 PDT Investigating - We are experiencing increased error rates with our Slack integration due to a Slack incident. You can follow along on Slack's status page here: https://slack-status.com/2026-05/46d9d5d41fbedd9f
Your product runs on more than Rootly
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services