Rootly

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-27 12:41 UTC

   We're aware that some users are experiencing errors (including intermittent 500 responses) when loading certain dropdown/selection menus and alert index table. On-call paging and alerting is unaffected. We're actively investigating and will post updates as we learn more.

2. resolved 2026-08-27 12:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-27 23:52 UTC

   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

2. monitoring 2026-05-28 00:23 UTC

   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

3. monitoring 2026-05-28 04:36 UTC

   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

4. resolved 2026-05-28 06:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-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

2. identified 2026-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.

3. monitoring 2026-05-14 14:49 UTC

   Slack has acknowledged the incident: https://slack-status.com/2026-05/fe557ca05fdb64fa. We are continuing to monitor.

4. resolved 2026-05-14 16:00 UTC

   The issue has been resolved on Slack's side.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Homepage

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-14 15:51 UTC

   We are currently investigating reports loading issues on our marketing homepage, affecting users in some locations. This is related to an ongoing issue with our hosting provider, Webflow. You can follow their progress here: status.webflow.com/incidents/kdtchw1lvsfv. The Rootly...

2. resolved 2026-04-14 23:23 UTC

   Webflow has resolved the issue and our marketing homepage is functioning as expected. Full details: https://status.webflow.com/incidents/kdtchw1lvsfv.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Web Platform

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-03 20:23 UTC

   We are noticing slower than normal loading times on a few pages (namely subtabs). We are actively working on the issue. No impact to incident creation, Slack, and on-call paging.

2. resolved 2026-02-03 20:25 UTC

   This has been resolved. Again no impact on incident creation or on-call paging.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Workflows

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-29 09:55 UTC

   We are currently investigating an issue with with intermittent latency in workflows. On-Call is unaffected.

2. identified 2026-01-29 10:08 UTC

   We've identified the issue and are monitoring as the system comes back to steady state.

3. monitoring 2026-01-29 10:53 UTC

   A fix has been implemented and continuing to monitor the results. All systems are running normally and continue to see no impact to On-Call.

4. resolved 2026-01-29 11:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Homepage

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-01-23 14:59 UTC

   Our marketing (Rootly.com) homepage is intermittently loading + broken links due to an upstream Webflow incident. We are closely monitoring. No impact to any Rootly product. Follow along on Webflow: https://status.webflow.com/incidents/tzg02d69k7yf

2. monitoring 2026-01-23 15:08 UTC

   Things appear to be resolved. We will continue to monitor until Webflow's status page marks it as resolved: https://status.webflow.com/incidents/tzg02d69k7yf.

3. resolved 2026-01-23 18:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Homepage

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-12-05 09:01 UTC

   Our Rootly.com homepage are seeing 500 errors due to upstream service provider (Cloudflare) issues. No impact to On-Call, Web, Slack, or any other part of our application.

2. resolved 2025-12-05 09:14 UTC

   The issues have been resolved: https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: On-Call, Slack App, Web Platform

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-11-18 11:54 UTC

   We are seeing upstream Cloudflare issues at the moment. They are experiencing a global outage that we are monitoring. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 It appears to be intermittent depending on the users location.

2. monitoring 2025-11-18 12:19 UTC

   We are seeing strong recovery across most regions (NA, EMEA, APAC, etc.). Everything appears to be functioning as expected for most users (some still require retries and is intermittent). We are continuing to monitor. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

3. monitoring 2025-11-18 12:49 UTC

   We are seeing degraded affects across several regions still for some users. We are continuing to monitor.

4. monitoring 2025-11-18 13:19 UTC

   We are seeing degraded affects across several regions still for some users (some with stronger recovery than others). We are continuing to monitor.

5. monitoring 2025-11-18 13:37 UTC

   We are seeing degraded affects across several regions still for some users. We are continuing to monitor. Cloudflare has identified the issue and implementing a fix: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7.

6. monitoring 2025-11-18 13:42 UTC

   We are continuing to monitor for any further issues.

7. monitoring 2025-11-18 13:44 UTC

   We are continuing to monitor for any further issues.

8. resolved 2025-11-18 13:58 UTC

   All regions are showing healthy traffic and all products are working as expected. We will continue to monitor out of precaution.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App, Web Platform, Status Pages

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-12 21:40 UTC

   We are investigating issues affecting our Web Platform and Slack. Rootly On-Call is unaffected.

2. monitoring 2025-11-12 22:03 UTC

   We have a fix implemented and are continuing to monitor. Some customers may notice slightly slower performance.

3. monitoring 2025-11-12 22:04 UTC

   We are continuing to monitor for any further issues.

4. resolved 2025-11-12 22:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-11-07 02:32 UTC

   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

2. identified 2025-11-07 03:14 UTC

   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.

3. resolved 2025-11-07 05:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App, Web Platform, Mobile App, API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-29 20:32 UTC

   We are currently investigating reports of increased latency across the Rootly platform. Users may experience slower-than-usual response times when performing actions. At this time, paging and alerting are not impacted, and all core functionality remains operational. Our...

2. identified 2025-10-29 21:10 UTC

   We've identified the issue and are working to towards mitigation.

3. resolved 2025-10-29 21:40 UTC

   We have fully resolved the latency issues that were affecting our service. All systems are should now be operating normally, and performance has returned to expected levels.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: On-Call

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-20 18:48 UTC

   We are currently investigating delays in paging notifications due to an issue with one of our upstream providers. As a result, incident alerts may be delayed in reaching on-call responders. We appreciate your patience and will provide updates as more information becomes...

2. identified 2025-10-20 19:08 UTC

   Our engineers are still working to mitigate the issue. Paging continues to be delayed.

3. identified 2025-10-20 19:48 UTC

   Our engineers are still working to mitigate the issue. Paging continues to be delayed but alert ingestion remains unaffected.

4. identified 2025-10-20 20:22 UTC

   Our engineering team continues to actively work on the issue. Alerts are being ingested but sent out delayed.

5. monitoring 2025-10-20 20:34 UTC

   Our system has recovered and new notifications are being sent without delay. Some previously delayed pages are and other on-call notifications may arrive later than expected.

6. resolved 2025-10-20 21:42 UTC

   This issue is now fully resolved as our upstream providers have recovered.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Homepage

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-20 17:34 UTC

   Our marketing homepage (Rootly.com) is impacted by upstream Webflow issues: https://status.webflow.com/. Some users are seeing 500s. We'll update here once resolved.

2. resolved 2025-10-20 17:55 UTC

   Our marketing homepage is working as expected. Thank you for the patience. Full update history: https://status.webflow.com/

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: On-Call, Slack App

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-20 09:53 UTC

   The issue has been identified and a fix is being implemented.

2. identified 2025-10-20 10:05 UTC

   We are continuing to work on a fix for this issue.

3. identified 2025-10-20 10:10 UTC

   We are continuing to work on a fix for this issue.

4. identified 2025-10-20 10:31 UTC

   We are continuing to work through delayed on-call notifications. Incident response and Slack works as expected. We'll continue to provide regular updates here.

5. identified 2025-10-20 11:22 UTC

   We are continuing to work through delayed on-call notifications. Incident response and Slack works as expected. We'll continue to provide regular updates here.

6. resolved 2025-10-20 11:36 UTC

   The earlier delays in Rootly On-Call notifications have been fully resolved. All systems are operating normally. Thank you for your patience.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Web Platform, API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-25 16:16 UTC

   We are currently investigating increased latency in our in-app search (including alert search and incident search). Newly created resources may not be immediately searchable. Search results in-app may be slower to load than normal. Search results may be returned more slowly for...

2. monitoring 2025-09-25 16:49 UTC

   We identified the root cause of the issue and have implemented a fix. Latencies have returned to normal and we are monitoring them going forward.

3. resolved 2025-09-25 21:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App, Web Platform

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-09-04 17:19 UTC

   We are currently investigating reports of failures when interacting with our app in Slack and web. Our team is actively looking into the issue and will provide updates as more information becomes available.

2. monitoring 2025-09-04 17:41 UTC

   We have identified the underlying issue affecting interactions with our app in Slack and web. We are seeing signs of gradual recovery and are continuing to monitor the situation closely to ensure full resolution.

3. monitoring 2025-09-04 17:44 UTC

   Web is operational - we are continuing to monitor reports of Slack interactions failing.

4. identified 2025-09-04 19:03 UTC

   The Rootly Slack app is currently unavailable. Users are unable to interact with our product in Slack at this time. Our web app remains available. Our engineering team is actively working to restore full functionality. On-Call remains operational. We will provide updates as more...

5. identified 2025-09-04 21:37 UTC

   We are actively debugging with the Slack engineering team on potential upstream issues. Web, mobile, on-call remains operational.

6. identified 2025-09-05 00:08 UTC

   Slack Engineering has identified the issue, and we are working with them to mitigate. Web, mobile, and paging (on-call) remains operational.

7. identified 2025-09-05 00:53 UTC

   Slack's engineering team is continuing to implement the fix. Web, mobile, and on-call paging remain operational.

8. resolved 2025-09-05 01:58 UTC

   Slack's engineering has resolved the issue. Slack is working as expected. We appreciate your patience. RCA will be made available to customers from Slack and Rootly.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-28 13:02 UTC

   We are currently monitoring an incident from Slack (https://slack-status.com/2025-08/54ca351d3ad76351) and are aware of issues with our Slack App displaying a "We cannot display this message" error when interacting with apps that utilize drop-down options. Initial findings...

2. identified 2025-08-28 13:57 UTC

   We've identified that the following impacted version: 4.45.69 342c17f19a46a42fda9612f6d8e0b46dea5a07a5@1756377163 The impact appears to limited to Slack's Desktop App. Web, some versions of Slack Desktop and mobile continue to be operational.

3. resolved 2025-08-28 16:10 UTC

   This issue is now resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App, Web Platform, API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-08-21 18:09 UTC

   We are currently investigating increased reports of latency and failures when interacting with our app in Slack. Our team is actively looking into the issue and will provide updates as more information becomes available

2. identified 2025-08-21 18:42 UTC

   We’ve investigated and found the issue is related to a broader ongoing incident at one of our infrastructure providers. You can follow their status updates here: https://www.cloudflarestatus.com/incidents/d9n3g1vnxdd2 While our Slack app is the most visibly impacted, we are also...

3. resolved 2025-08-21 19:47 UTC

   This incident has been fully resolved and all services are functioning normally. There was no impact to on-call paging at any time. We’ll continue to monitor, but no further action is required.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Mobile App

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-15 14:02 UTC

   We're aware of a potential issue that could impact Android users loading the mobile app. If any Android users have issues loading the app, please clear cache to fix. Long hold on the Rootly app icon (which brings up a menu), hit app info -> storage and cache -> clear cache....

2. resolved 2025-08-15 14:35 UTC

   The issue has been mitigated. If you haven't upgraded to the latest version of the mobile app on Android you would've remained unaffected. Again, paging and push notifications are unaffected.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App, Web Platform, API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-24 15:11 UTC

   We are currently investigating an issue causing elevated latency across multiple parts of our platform. Affected users may experience delays when accessing the dashboard, API responses, and background processing tasks. Our engineering team is actively working to identify the...

2. identified 2025-07-24 15:25 UTC

   We have identified that higher-than-normal load on our database systems is contributing to increased latency in our services for some users. Our engineering team is actively working to rebalance traffic and optimize performance. We will continue to monitor closely and provide...

3. monitoring 2025-07-24 16:00 UTC

   We're seeing a noticeable reduction in latency across affected services. API responses, dashboard performance, and background processes are beginning to recover. Our team is continuing to monitor the situation closely to ensure stability. Paging continues to be operational.

4. resolved 2025-07-24 17:39 UTC

   The earlier latency issues have been fully resolved. Database load is now being handled effectively, and service latency has remained consistently within nominal ranges across all affected components.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-15 17:34 UTC

   We are seeing multiple reports that Slack Client Version 4.45.60 5ceb15a480a45f9ff66f8ac70ad43d9365eda8e6@1752518552 (Production) has re-introduced the same issue with select menus and dropdowns from earlier noted here: https://slack-status.com/2025-07/1ce16e396a56dcf8 We are...

2. investigating 2025-07-15 18:39 UTC

   We are still seeing reports of select and multi-select menus failing to populate due to an issue with certain versions of the Web and Desktop Slack client. The following platforms are unaffected: - Rootly Web Dashboard - Slack iOS/Android app On-call paging is not impacted.

3. investigating 2025-07-15 18:57 UTC

   Slack continues to work toward resolving this matter: https://slack-status.com/2025-07/1ce16e396a56dcf8 Slack is currently recommend that users continue trying to refresh their client using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux).

4. monitoring 2025-07-15 19:01 UTC

   We are seeing reports that updating Slack Desktop Client to version Version 4.45.60 a8def85020f2e6f981e24e9ee2c4f8582820e1e7@1752601050 (Production) may resolve this issue. Please continue trying to refresh desktop client using Command + Shift + R (Mac) or Ctrl + Shift + R...

5. resolved 2025-07-15 19:29 UTC

   This issue is resolved. A hard refresh of Slack's web client, or desktop client using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux) may be required to restore select and multi-select form functionality.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-07-15 00:14 UTC

   A recent Slack Web Client update broke loading multi select dropdowns. Known web client versions impacted are: - 4.45.60 - 4.44.65 As a workaround, in order to create / update an incident you can use our Web Dashboard or Slack iOS / Android app. We are are monitoring the issue...

2. identified 2025-07-15 02:00 UTC

   We are continuing to work with Slack regarding this issue.

3. identified 2025-07-15 04:00 UTC

   We are continuing to work with Slack regarding this issue.

4. identified 2025-07-15 07:00 UTC

   We are continuing to work with Slack regarding this issue.

5. identified 2025-07-15 07:10 UTC

   We are continuing to work with Slack regarding this issue.

6. identified 2025-07-15 07:17 UTC

   We are continuing to work with Slack regarding this issue.

7. identified 2025-07-15 09:57 UTC

   Please follow the Slack Incident here: https://slack-status.com/2025-07/1ce16e396a56dcf8

8. identified 2025-07-15 12:18 UTC

   The Slack incident is ongoing: https://slack-status.com/2025-07/1ce16e396a56dcf8 We recommend following both pages for updates. Creating and updating incidents via our Web Dashboard or Slack iOS / Android app continues to function as expected. On-call paging is not impacted.

9. monitoring 2025-07-15 12:33 UTC

   We have confirmed that loading multi select dropdowns is functioning as expected in our workspace and others after closing and re-opening the Slack client. We will continue to monitor this issue.

10. resolved 2025-07-15 14:29 UTC

    The Slack team is now reporting that this issue is now resolved for all users.

Excerpts are shortened. Read the full incident on Rootly's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-11 13:05 UTC

   We are currently investigating an issue where some Slack notifications are not being delivered.

2. identified 2025-07-11 13:19 UTC

   We have identified the issue and have verified that the scope of the outage only applies to Slack Blocks for Alert notifications. We actively deploying a fix for this issue.

3. identified 2025-07-11 13:22 UTC

   We are continuing to work on a fix for this issue.

4. resolved 2025-07-11 13:58 UTC

   The issue impacting Slack Blocks for Alert notifications has been resolved

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: On-Call

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-07-04 18:27 UTC

   The issue has been identified and a fix is being implemented.

2. identified 2025-07-04 18:28 UTC

   We are currently investigating an issue impacting the Mobile API for Alerts, resulting in degraded service for customers accessing alerts via mobile devices. Affected users may experience: - Errors loading alert data - Web application access remains operational and unaffected.

3. resolved 2025-07-04 18:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-05-12 23:06 UTC

   An upstream Slack incident has resulted in certain users being unable to load the platform. https://slack-status.com/2025-05/7b32241eb41a54aa

2. resolved 2025-05-13 00:09 UTC

   Slack has resolved their incident: https://slack-status.com/2025-05/7b32241eb41a54aa.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Status Pages

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-04-02 15:34 UTC

   We're investigating user reports of public status pages not loading.

2. resolved 2025-04-02 15:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Web Platform

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-25 17:42 UTC

   Intermittent latency in Web application, team is investigating.

2. investigating 2025-03-25 17:43 UTC

   We are continuing to investigate this issue.

3. investigating 2025-03-25 17:51 UTC

   Rootly on-call and ability to create incidents is working as expected.

4. resolved 2025-03-25 18:00 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App, Web Platform, Status Pages, Mobile App, API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-03-22 01:40 UTC

   We are currently investigating an issue impacting the performance of Slack and web-based services. Users may experience interruptions in accessing the Web Platform and Rootly Slack commands.

2. resolved 2025-03-22 01:48 UTC

   The issue affecting Web and Slack performance has been resolved. All services are functioning normally. We appreciate your patience during this incident and apologize for any inconvenience caused.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2025-02-26 22:22 UTC

   We are still noticing a minority of errors failing on Slack's end due to their outage impacting /rootly commands on Slack. Stay up to date with Slack: https://slack-status.com/2025-02/1b757d1d0f444c34.

2. resolved 2025-02-27 14:16 UTC

   Slack reported this morning issues impacting their app have been resolved. However, historical events are still attempting to get replayed through their system queue. Stay up to date with Slack: https://slack-status.com/2025-02/1b757d1d0f444c34.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-02-26 16:06 UTC

   Slack is running into an incident that is impacting /slash commands (e.g. /rootly new) and messaging capabilities https://slack-status.com/2025-02/1b757d1d0f444c34. This means button interactions and messages are delayed or will fail completely. Some users have also reported...

2. identified 2025-02-26 16:57 UTC

   Latency and failure rates from Slack remain quite high still https://slack-status.com/2025-02/1b757d1d0f444c34.

3. identified 2025-02-26 17:04 UTC

   Our engineering team is continuing to monitor closely. We've pushed a few changes to modify our retry logic despite Slack API reporting an outage. We are continuing to look for alternative methods. Stay up to date with Slack: https://slack-status.com/2025-02/1b757d1d0f444c34.

4. resolved 2025-02-26 20:42 UTC

   Error rates have come down significantly. Scattered delays when creating channels. The /rootly command is now working as intended. Stay up to date with Slack: https://slack-status.com/2025-02/1b757d1d0f444c34.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Workflows

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-11 03:11 UTC

   A handful of workflows are currently delayed due to latency in our queue. We are investigating the issue. Rootly On-Call and incident creation remains unimpacted.

2. monitoring 2025-02-11 03:55 UTC

   The issue has been resolved and latencies are back to normal. We are currently monitoring. Rootly On-Call and incident creation remains unimpacted.

3. resolved 2025-02-11 04:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Web Platform

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-11-02 05:50 UTC

   We are investigating an issue affecting customers ability to log into Rootly.com. On-Call, Slack, and incident creation remain unaffected.

2. resolved 2024-11-02 05:52 UTC

   Login issues have been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2024-10-30 23:49 UTC

   Our Web Platform and Slack were inaccessible for roughly 4 minutes before a fix was applied. Rootly On-Call and paging was unaffected.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-09-25 14:22 UTC

   Incident creation from Slack is impacted from an upstream provider issue but Web Platform and Rootly On-Call is not impacted.

2. investigating 2024-09-25 14:24 UTC

   We are continuing to investigate this issue.

3. resolved 2024-09-25 14:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-08-01 16:28 UTC

   Mainly affecting customers who are actively trialling Rootly, we've made an upgrade that has caused a slight queuing of workflow runs.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App, Web Platform

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-06-28 21:52 UTC

   We are investigating a partial outage affecting some users from accessing the Web Platform and Slack. Rootly On-Call and paging is not impacted.

2. resolved 2024-06-28 21:56 UTC

   The incident has been resolved. Thank you for your patience.

Excerpts are shortened. Read the full incident on Rootly's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-04-29 22:41 UTC

   Some emails sent through Rootly are queuing in SendGrid and processing after sitting in the queue for extended periods of time. We are currently debugging with SendGrid support.

2. resolved 2024-04-29 23:28 UTC

   This incident has been resolved and was due to an upstream 3rd party issue via SendGrid. Rootly availability and incident creation was not impacted.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-04-10 07:05 UTC

   The issue has been identified and a fix is being implemented.

2. identified 2024-04-10 07:21 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2024-04-10 07:30 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2024-04-10 08:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App, Web Platform

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-04-10 01:52 UTC

   We are experiencing degraded performance across the application. Incident creation is not impacted, and On-Call is not impacted.

2. investigating 2024-04-10 02:11 UTC

   We are continuing to investigate this issue.

3. resolved 2024-04-10 02:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2024-04-04 09:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App, Web Platform, API

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-04-01 15:03 UTC

   The team is currently investigating issues with users signing into Rootly Web Platform.

2. investigating 2024-04-01 15:05 UTC

   We are continuing to investigate this issue.

3. investigating 2024-04-01 15:10 UTC

   We are continuing to investigate this issue. Slack, Web, and API are currently impacted. Rootly On-Call remains online without impact.

4. identified 2024-04-01 15:15 UTC

   The issue has been identified and the team is aware of the root cause. A fix is being implemented.

5. resolved 2024-04-01 15:19 UTC

   This incident has been resolved. RCA will follow and be sent to customers.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Web Platform

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-01-23 17:28 UTC

   Our incident timeline on our Web Platform is loading slower than usual. Incident creation is unaffected.

2. resolved 2024-01-23 18:20 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-01-09 20:33 UTC

   Incident Slack channel creation is currently backed up. We are deploying a rollback. Incident creation on the Rootly Web Platform is working normally.

2. resolved 2024-01-09 20:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-01-09 20:19 UTC

   We have identified the issue and currently deploying a fix.

2. resolved 2024-01-09 20:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Workflows

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-11-19 14:15 UTC

   We are seeing a backlog of workflows queued waiting to be executed. The team is currently shipping a fix.

2. monitoring 2023-11-19 14:21 UTC

   A fix has been implemented and we are monitoring the results

3. resolved 2023-11-19 14:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Workflows

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-11-10 00:40 UTC

   The team has noticed a latency in workflow workers.

2. investigating 2023-11-10 00:40 UTC

   We are seeing a backlog of workflows queued waiting to be executed. The team is currently shipping a fix.

3. resolved 2023-11-10 00:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Slack App, Web Platform, API, Workflows

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2023-10-30 20:13 UTC

   We are noticing our background jobs processing slower than normal. Any workflows queued to run are behind schedule. Our engineering team has identified the issue and is currently deploying a fix.

2. investigating 2023-10-30 20:26 UTC

   We are continuing to investigate this issue. Our engineering team has a fix currently being deployed.

3. investigating 2023-10-30 20:28 UTC

   We are continuing to investigate this issue. Our engineering team has a fix currently being deployed.

4. resolved 2023-10-30 20:35 UTC

   Looks like everything is working as normal, including incident creation in Slack. We had an upstream hiccup caused by Cloudflare.

Excerpts are shortened. Read the full incident on Rootly's status page.

Affected: Web Platform

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2023-08-25 19:53 UTC

   A fix has been implemented and we are monitoring the results.

2. resolved 2023-08-25 20:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Rootly's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2023-07-27 09:00 UTC

   Slack is currently experiencing an outage which subsequently is affecting Rootly's Slack application. Expect Slack related actions (including those outside of Rootly's Slack app) to be affected (e.g. channel creation, notifications, etc.). Rootly.com Web App continues to...

2. resolved 2023-07-27 10:05 UTC

   Slack has restored full functionality to their services and has resolved their incident. Rootly's services are fully restored as a result. Details can be found on Slack's status page here: https://status.slack.com/2023-07/08e3781ccbef33d5

Excerpts are shortened. Read the full incident on Rootly's status page.