Webapp.io Outage History

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

1. investigating 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:38 AM UTC

1. investigating 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, 09:13 PM UTC· resolved Sep 25, 2025, 09:13 PM UTC

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

Read the full incident report →

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

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

Read the full incident report →

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

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

Read the full incident report →

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

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

Read the full incident report →

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

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

Read the full incident report →

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

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

Read the full incident report →

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

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

Read the full incident report →

Started Jul 15, 2025, 02:29 PM UTC· resolved Jul 15, 2025, 02:29 PM UTC

1. resolved Jul 15, 2025, 02:29 PM UTC

   Jul 15, 07:29 PDT Resolved - The Slack team is now reporting that this issue is now resolved for all users. Jul 15, 05:33 PDT Monitoring - 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. Jul 15, 05:18 PDT Update - 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. Jul 15, 02:57 PDT Update - Please follow the Slack Incident here: https://slack-status.com/2025-07/1ce16e396a56dcf8 Jul 15, 00:17 PDT Update - We are continuing to work with Slack regarding this issue. Jul 15, 00:10 PDT Update - We are continuing to work with Slack regarding this issue. Jul 15, 00:00 PDT Update - We are continuing to work with Slack regarding this issue. Jul 14, 21:00 PDT Update - We are continuing to work with Slack regarding this issue. Jul 14, 19:00 PDT Update - We are continuing to work with Slack regarding this issue. Jul 14, 17:14 PDT Identified - 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 closely with Slack and will update this page when we have more information.

Read the full incident report →

Started Jul 11, 2025, 01:58 PM UTC· resolved Jul 11, 2025, 02:07 PM UTC

1. resolved Jul 11, 2025, 02:07 PM UTC

   Jul 11, 06:58 PDT Resolved - The issue impacting Slack Blocks for Alert notifications has been resolved Jul 11, 06:22 PDT Update - We are continuing to work on a fix for this issue. Jul 11, 06:19 PDT Identified - 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. Jul 11, 06:05 PDT Investigating - We are currently investigating an issue where some Slack notifications are not being delivered.

Read the full incident report →

Started Jul 04, 2025, 06:37 PM UTC· resolved Jul 04, 2025, 06:37 PM UTC

1. resolved Jul 04, 2025, 06:37 PM UTC

   Jul 4, 11:37 PDT Resolved - This incident has been resolved. Jul 4, 11:28 PDT Update - 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. Jul 4, 11:27 PDT Identified - The issue has been identified and a fix is being implemented.

Read the full incident report →

Started May 12, 2025, 11:06 PM UTC· resolved May 13, 2025, 12:09 AM UTC

1. investigating May 12, 2025, 11:06 PM 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 May 13, 2025, 12:09 AM UTC

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

Read the full incident report →

Started Apr 02, 2025, 03:34 PM UTC· resolved Apr 02, 2025, 03:58 PM UTC

1. investigating Apr 02, 2025, 03:34 PM UTC

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

2. resolved Apr 02, 2025, 03:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 25, 2025, 05:42 PM UTC· resolved Mar 25, 2025, 06:00 PM UTC

1. investigating Mar 25, 2025, 05:42 PM UTC

   Intermittent latency in Web application, team is investigating.

2. investigating Mar 25, 2025, 05:43 PM UTC

   We are continuing to investigate this issue.

3. investigating Mar 25, 2025, 05:51 PM UTC

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

4. resolved Mar 25, 2025, 06:00 PM UTC

   This issue has been resolved.

Read the full incident report →

Started Mar 22, 2025, 01:40 AM UTC· resolved Mar 22, 2025, 01:48 AM UTC

1. investigating Mar 22, 2025, 01:40 AM 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 Mar 22, 2025, 01:50 AM 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.

Read the full incident report →

Started Feb 26, 2025, 10:22 PM UTC· resolved Feb 27, 2025, 02:16 PM UTC

1. monitoring Feb 26, 2025, 10:22 PM 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 Feb 27, 2025, 04:16 PM 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.

Read the full incident report →

Started Feb 26, 2025, 04:06 PM UTC· resolved Feb 26, 2025, 08:42 PM UTC

1. identified Feb 26, 2025, 04:06 PM 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 being unable to load Slack completely. Rootly On-Call and Web Platform remain unaffected.

2. identified Feb 26, 2025, 04:57 PM UTC

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

3. identified Feb 26, 2025, 05:04 PM 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 Feb 26, 2025, 08:42 PM 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.

Read the full incident report →

Started Feb 11, 2025, 03:11 AM UTC· resolved Feb 11, 2025, 04:10 AM UTC

1. investigating Feb 11, 2025, 03:11 AM 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 Feb 11, 2025, 03:55 AM 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 Feb 11, 2025, 04:10 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 02, 2024, 05:50 AM UTC· resolved Nov 02, 2024, 05:52 AM UTC

1. investigating Nov 02, 2024, 05:50 AM UTC

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

2. resolved Nov 02, 2024, 05:52 AM UTC

   Login issues have been resolved.

Read the full incident report →