Rootly Outage History

Started Apr 15, 2026, 07:03 AM UTC· resolved Apr 15, 2026, 07:03 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Jan 23, 2026, 06:04 PM UTC· resolved Jan 23, 2026, 06:04 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Oct 27, 2025, 06:41 PM UTC· resolved Aug 27, 2026, 12:57 PM UTC

1. investigating Aug 27, 2026, 12:41 PM 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 Aug 27, 2026, 12:57 PM UTC

   Aug 27, 05:57 PDT Resolved - This incident has been resolved. Aug 27, 05:41 PDT Investigating - 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.

3. resolved Aug 27, 2026, 12:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 27, 2025, 06:41 PM UTC· resolved May 28, 2026, 06:25 AM UTC

1. investigating May 27, 2026, 11:52 PM 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 May 28, 2026, 12:23 AM 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 May 28, 2026, 04:36 AM 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 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

5. resolved May 28, 2026, 06:25 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 27, 2025, 06:41 PM UTC· resolved May 14, 2026, 04:00 PM UTC

1. identified May 14, 2026, 02:01 PM 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 May 14, 2026, 02:34 PM 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 May 14, 2026, 02:49 PM UTC

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

4. resolved May 14, 2026, 04:00 PM UTC

   The issue has been resolved on Slack's side.

5. resolved May 14, 2026, 04:00 PM UTC

   May 14, 09:00 PDT Resolved - The issue has been resolved on Slack's side. May 14, 07:49 PDT Monitoring - Slack has acknowledged the incident: https://slack-status.com/2026-05/fe557ca05fdb64fa. We are continuing to monitor. May 14, 07:34 PDT Update - 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. May 14, 07:01 PDT Identified - 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

Read the full incident report →

Started Oct 27, 2025, 06:41 PM UTC· resolved Oct 29, 2025, 09:40 PM UTC

1. investigating Oct 29, 2025, 08:32 PM 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 engineering team is actively working to identify and mitigate the cause. We will provide updates as more information becomes available.

2. identified Oct 29, 2025, 09:10 PM UTC

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

3. resolved Oct 29, 2025, 09:40 PM UTC

   Oct 29, 14:40 PDT Resolved - 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. Oct 29, 14:10 PDT Identified - We've identified the issue and are working to towards mitigation. Oct 29, 13:32 PDT Investigating - 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 engineering team is actively working to identify and mitigate the cause. We will provide updates as more information becomes available.

4. resolved Oct 29, 2025, 09:40 PM 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.

Read the full incident report →

Started Oct 27, 2025, 06:41 PM UTC· resolved Nov 07, 2025, 05:39 AM UTC

1. investigating Nov 07, 2025, 02:32 AM 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 Nov 07, 2025, 03:14 AM 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 Nov 07, 2025, 05:39 AM UTC

   Nov 6, 21:39 PST Resolved - This incident has been resolved. Nov 6, 19:14 PST Identified - 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. Nov 6, 18:32 PST Investigating - 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

4. resolved Nov 07, 2025, 05:39 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 27, 2025, 06:41 PM UTC· resolved Nov 12, 2025, 10:06 PM UTC

1. investigating Nov 12, 2025, 09:40 PM UTC

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

2. monitoring Nov 12, 2025, 10:03 PM UTC

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

3. monitoring Nov 12, 2025, 10:04 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Nov 12, 2025, 10:06 PM UTC

   This incident has been resolved.

5. resolved Nov 12, 2025, 10:20 PM UTC

   Nov 12, 14:06 PST Resolved - This incident has been resolved. Nov 12, 14:04 PST Update - We are continuing to monitor for any further issues. Nov 12, 14:03 PST Monitoring - We have a fix implemented and are continuing to monitor. Some customers may notice slightly slower performance. Nov 12, 13:40 PST Investigating - We are investigating issues affecting our Web Platform and Slack. Rootly On-Call is unaffected.

Read the full incident report →

Started Oct 27, 2025, 06:41 PM UTC· resolved Nov 18, 2025, 01:58 PM UTC

1. investigating Nov 18, 2025, 11:54 AM 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 Nov 18, 2025, 12:19 PM 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 Nov 18, 2025, 12:49 PM UTC

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

4. monitoring Nov 18, 2025, 01:19 PM 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 Nov 18, 2025, 01:37 PM 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 Nov 18, 2025, 01:42 PM UTC

   We are continuing to monitor for any further issues.

7. monitoring Nov 18, 2025, 01:44 PM UTC

   We are continuing to monitor for any further issues.

8. resolved Nov 18, 2025, 01:58 PM UTC

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

9. resolved Nov 18, 2025, 01:58 PM UTC

   Nov 18, 05:58 PST Resolved - All regions are showing healthy traffic and all products are working as expected. We will continue to monitor out of precaution. Nov 18, 05:44 PST Update - We are continuing to monitor for any further issues. Nov 18, 05:42 PST Update - We are continuing to monitor for any further issues. Nov 18, 05:37 PST Update - 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. Nov 18, 05:19 PST Update - We are seeing degraded affects across several regions still for some users (some with stronger recovery than others). We are continuing to monitor. Nov 18, 04:49 PST Update - We are seeing degraded affects across several regions still for some users. We are continuing to monitor. Nov 18, 04:19 PST Monitoring - 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 Nov 18, 03:54 PST Investigating - 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.

Read the full incident report →

Started Oct 27, 2025, 06:41 PM UTC· resolved Dec 05, 2025, 09:14 AM UTC

1. investigating Dec 05, 2025, 09:01 AM 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 Dec 05, 2025, 09:14 AM UTC

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

3. resolved Dec 05, 2025, 09:14 AM UTC

   Dec 5, 01:14 PST Resolved - The issues have been resolved: https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q Dec 5, 01:01 PST Investigating - 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.

Read the full incident report →

Started Oct 27, 2025, 06:41 PM UTC· resolved Jan 23, 2026, 06:04 PM UTC

1. investigating Jan 23, 2026, 02:59 PM 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 Jan 23, 2026, 03:08 PM 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 Jan 23, 2026, 06:04 PM UTC

   Jan 23, 10:04 PST Resolved - This incident has been resolved. Jan 23, 07:08 PST Monitoring - 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. Jan 23, 06:59 PST Investigating - 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

4. resolved Jan 23, 2026, 06:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 27, 2025, 06:41 PM UTC· resolved Jan 29, 2026, 11:08 AM UTC

1. investigating Jan 29, 2026, 09:55 AM UTC

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

2. identified Jan 29, 2026, 10:08 AM UTC

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

3. monitoring Jan 29, 2026, 10:53 AM 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 Jan 29, 2026, 11:08 AM UTC

   This incident has been resolved.

5. resolved Jan 29, 2026, 11:08 AM UTC

   Jan 29, 03:08 PST Resolved - This incident has been resolved. Jan 29, 02:53 PST Monitoring - 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. Jan 29, 02:08 PST Identified - We've identified the issue and are monitoring as the system comes back to steady state. Jan 29, 01:55 PST Investigating - We are currently investigating an issue with with intermittent latency in workflows. On-Call is unaffected.

Read the full incident report →

Started Oct 27, 2025, 06:41 PM UTC· resolved Feb 03, 2026, 08:25 PM UTC

1. investigating Feb 03, 2026, 08:23 PM 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 Feb 03, 2026, 08:25 PM UTC

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

3. resolved Feb 03, 2026, 08:28 PM UTC

   Feb 3, 12:25 PST Resolved - This has been resolved. Again no impact on incident creation or on-call paging. Feb 3, 12:23 PST Investigating - 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.

Read the full incident report →

Started Oct 27, 2025, 06:41 PM UTC· resolved Apr 14, 2026, 11:23 PM UTC

1. investigating Apr 14, 2026, 03:51 PM 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 application including on-call is not affected. A workaround is directly visiting https://rootly.com/account. We are monitoring the situation and will provide updates as they become available.

2. resolved Apr 14, 2026, 11:23 PM UTC

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

3. resolved Apr 15, 2026, 07:06 AM UTC

   Apr 14, 16:23 PDT Resolved - Webflow has resolved the issue and our marketing homepage is functioning as expected. Full details: https://status.webflow.com/incidents/kdtchw1lvsfv. Apr 14, 08:51 PDT Investigating - 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 application including on-call is not affected. A workaround is directly visiting https://rootly.com/account. We are monitoring the situation and will provide updates as they become available.

Read the full incident report →

Started Oct 20, 2025, 06:48 PM UTC· resolved Oct 20, 2025, 09:42 PM UTC

1. investigating Oct 20, 2025, 06:48 PM 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 available.

2. identified Oct 20, 2025, 07:08 PM UTC

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

3. identified Oct 20, 2025, 07:48 PM UTC

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

4. identified Oct 20, 2025, 08:22 PM UTC

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

5. monitoring Oct 20, 2025, 08:34 PM 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 Oct 20, 2025, 09:42 PM UTC

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

7. resolved Oct 20, 2025, 11:16 PM UTC

   Oct 20, 14:42 PDT Resolved - This issue is now fully resolved as our upstream providers have recovered. Oct 20, 13:34 PDT Monitoring - 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. Oct 20, 13:22 PDT Update - Our engineering team continues to actively work on the issue. Alerts are being ingested but sent out delayed. Oct 20, 12:48 PDT Update - Our engineers are still working to mitigate the issue. Paging continues to be delayed but alert ingestion remains unaffected. Oct 20, 12:08 PDT Identified - Our engineers are still working to mitigate the issue. Paging continues to be delayed. Oct 20, 11:48 PDT Investigating - 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 available.

Read the full incident report →

Started Oct 20, 2025, 05:34 PM UTC· resolved Oct 20, 2025, 05:55 PM UTC

1. investigating Oct 20, 2025, 05:34 PM 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 Oct 20, 2025, 05:55 PM UTC

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

3. resolved Oct 20, 2025, 05:55 PM UTC

   Oct 20, 10:55 PDT Resolved - Our marketing homepage is working as expected. Thank you for the patience. Full update history: https://status.webflow.com/ Oct 20, 10:34 PDT Investigating - 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.

Read the full incident report →

Started Oct 20, 2025, 11:36 AM UTC· resolved Oct 20, 2025, 11:36 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Oct 20, 2025, 09:53 AM UTC· resolved Oct 20, 2025, 11:36 AM UTC

1. identified Oct 20, 2025, 09:53 AM UTC

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

2. identified Oct 20, 2025, 10:05 AM UTC

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

3. identified Oct 20, 2025, 10:10 AM UTC

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

4. identified Oct 20, 2025, 10:31 AM 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 Oct 20, 2025, 11:22 AM 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 Oct 20, 2025, 11:36 AM UTC

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

7. resolved Oct 20, 2025, 11:38 AM UTC

   Oct 20, 04:36 PDT Resolved - The earlier delays in Rootly On-Call notifications have been fully resolved. All systems are operating normally. Thank you for your patience. Oct 20, 04:22 PDT Update - 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. Oct 20, 03:31 PDT Update - 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. Oct 20, 03:10 PDT Update - We are continuing to work on a fix for this issue. Oct 20, 03:05 PDT Update - We are continuing to work on a fix for this issue. Oct 20, 02:53 PDT Identified - The issue has been identified and a fix is being implemented.

Read the full incident report →

Started Sep 25, 2025, 04:16 PM UTC· resolved Sep 25, 2025, 09:13 PM UTC

1. investigating Sep 25, 2025, 04:16 PM 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 certain API endpoints, including: GET /api/v1/incidents, GET /api/v1/services, GET /api/v1/groups, GET /api/v1/users, and GET /api/v1/audits. Our team is actively working on resolving this issue and will provide updates as soon as more information becomes available.

2. monitoring Sep 25, 2025, 04:49 PM 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 Sep 25, 2025, 09:13 PM UTC

   Sep 25, 14:13 PDT Resolved - This incident has been resolved. Sep 25, 09:49 PDT Monitoring - 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. Sep 25, 09:16 PDT Investigating - 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 certain API endpoints, including: GET /api/v1/incidents, GET /api/v1/services, GET /api/v1/groups, GET /api/v1/users, and GET /api/v1/audits. Our team is actively working on resolving this issue and will provide updates as soon as more information becomes available.

4. resolved Sep 25, 2025, 09:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 04, 2025, 05:19 PM UTC· resolved Sep 05, 2025, 01:58 AM UTC

1. investigating Sep 04, 2025, 05:19 PM 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 Sep 04, 2025, 05:41 PM 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 Sep 04, 2025, 05:44 PM UTC

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

4. identified Sep 04, 2025, 07:03 PM 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 information becomes available.

5. identified Sep 04, 2025, 09:37 PM UTC

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

6. identified Sep 05, 2025, 12:08 AM 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 Sep 05, 2025, 12:53 AM UTC

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

8. resolved Sep 05, 2025, 01:58 AM 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.

9. resolved Sep 05, 2025, 04:17 AM UTC

   Sep 4, 18:58 PDT Resolved - 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. Sep 4, 17:53 PDT Update - Slack's engineering team is continuing to implement the fix. Web, mobile, and on-call paging remain operational. Sep 4, 17:08 PDT Update - Slack Engineering has identified the issue, and we are working with them to mitigate. Web, mobile, and paging (on-call) remains operational. Sep 4, 14:37 PDT Update - We are actively debugging with the Slack engineering team on potential upstream issues. Web, mobile, on-call remains operational. Sep 4, 12:03 PDT Identified - 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 information becomes available. Sep 4, 10:44 PDT Update - Web is operational - we are continuing to monitor reports of Slack interactions failing. Sep 4, 10:41 PDT Monitoring - 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. Sep 4, 10:19 PDT Investigating - 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.

Read the full incident report →

Started Aug 28, 2025, 01:02 PM UTC· resolved Aug 28, 2025, 04:10 PM UTC

1. investigating Aug 28, 2025, 01:02 PM 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 suggest this behavior is tied to the latest version of Slack. We are actively monitoring the situation and working to confirm the root cause. We’ll provide further updates as soon as more information becomes available. We apologize for the disruption in the meantime.

2. identified Aug 28, 2025, 01:57 PM 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 Aug 28, 2025, 04:10 PM UTC

   Aug 28, 09:10 PDT Resolved - This issue is now resolved. Aug 28, 06:57 PDT Identified - 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. Aug 28, 06:02 PDT Investigating - 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 suggest this behavior is tied to the latest version of Slack. We are actively monitoring the situation and working to confirm the root cause. We’ll provide further updates as soon as more information becomes available. We apologize for the disruption in the meantime.

4. resolved Aug 28, 2025, 04:10 PM UTC

   This issue is now resolved.

Read the full incident report →

Started Aug 21, 2025, 06:09 PM UTC· resolved Aug 21, 2025, 07:47 PM UTC

1. investigating Aug 21, 2025, 06:09 PM 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 Aug 21, 2025, 06:42 PM 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 identifying potential effects on other services such as our web interface and APIs. Our on-call product remains operational. We’ll continue to share updates as we make progress.

3. resolved Aug 21, 2025, 07:47 PM UTC

   Aug 21, 12:47 PDT Resolved - 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. Aug 21, 11:42 PDT Identified - 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 identifying potential effects on other services such as our web interface and APIs. Our on-call product remains operational. We’ll continue to share updates as we make progress. Aug 21, 11:09 PDT Investigating - 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

4. resolved Aug 21, 2025, 07:47 PM 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.

Read the full incident report →

Started Aug 15, 2025, 02:02 PM UTC· resolved Aug 15, 2025, 02:35 PM UTC

1. investigating Aug 15, 2025, 02:02 PM 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. Paging and push notifications are not affected.

2. resolved Aug 15, 2025, 02:35 PM UTC

   Aug 15, 07:35 PDT Resolved - 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. Aug 15, 07:02 PDT Investigating - 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. Paging and push notifications are not affected.

3. resolved Aug 15, 2025, 02:35 PM 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.

Read the full incident report →

Started Jul 24, 2025, 03:11 PM UTC· resolved Jul 24, 2025, 05:39 PM UTC

1. investigating Jul 24, 2025, 03:11 PM 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 root cause and mitigate the impact. We will provide an update within 30 minutes or as soon as more information becomes available. Thank you for your patience as we work to resolve this issue.

2. identified Jul 24, 2025, 03:25 PM 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 updates. Paging is operational.

3. monitoring Jul 24, 2025, 04:00 PM 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 Jul 24, 2025, 05:39 PM UTC

   Jul 24, 10:39 PDT Resolved - 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. Jul 24, 09:00 PDT Monitoring - 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. Jul 24, 08:25 PDT Identified - 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 updates. Paging is operational. Jul 24, 08:11 PDT Investigating - 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 root cause and mitigate the impact. We will provide an update within 30 minutes or as soon as more information becomes available. Thank you for your patience as we work to resolve this issue.

5. resolved Jul 24, 2025, 05:39 PM 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.

Read the full incident report →

Started Jul 15, 2025, 05:34 PM UTC· resolved Jul 15, 2025, 07:29 PM UTC

1. investigating Jul 15, 2025, 05:34 PM 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 working with Slack to resolve this issue. 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 closely with Slack and will update this page when we have more information. On-call paging is not impacted.

2. investigating Jul 15, 2025, 06:39 PM 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 Jul 15, 2025, 06:57 PM 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 Jul 15, 2025, 07:01 PM 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 (Windows/Linux). We will continue to monitor this issue.

5. resolved Jul 15, 2025, 07:29 PM UTC

   Jul 15, 12:29 PDT Resolved - 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. Jul 15, 12:01 PDT Monitoring - 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 (Windows/Linux). We will continue to monitor this issue. Jul 15, 11:57 PDT Update - 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). Jul 15, 11:39 PDT Update - 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. Jul 15, 10:34 PDT Investigating - 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 working with Slack to resolve this issue. 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 closely with Slack and will update this page when we have more information. On-call paging is not impacted.

6. resolved Jul 15, 2025, 07:29 PM 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.

Read the full incident report →