Webapp.io Outage History

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 alert table. On-call paging and alerting is unaffected. We're actively investigating and will post updates as we learn more.

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.

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.

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

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.

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.

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

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.

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.

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

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.

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.

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.