Compare uptime, outage statistics, and incident history between FireHydrant and Rootly. See which service has better reliability.
Note: Each service has different practices when updating its status page. One service may report more incidents due to transparency, not necessarily worse reliability. Compare these stats with context.
Status monitoring since March 2024
Voice call delivery issues for Bulgarian / Telenor customers
{"note"=>"Some voice notifications are delayed or failing for Bulgarian / Telnor customers. We are actively invest...
MS Teams performance degraded
We're seeing problems with our MS Teams integration: the MS Teams bot and broader integration are currently unavailab...
Web application unavailable: assets failing to load
We're investigating an issue preventing the FireHydrant web application from loading. Browsers are unable to load the...
Status monitoring since October 2022
Some users seeing errors loading dropdowns and alert index page
We're aware that some users are experiencing errors (including intermittent 500 responses) when loading certain dropd...
Slack-dependent features degraded due to ongoing upstream Slack incident
We are experiencing increased error rates with our Slack integration due to a Slack incident. You can follow along on...
Slack-dependent features degraded due to ongoing upstream Slack incident
Slack-dependent features in Rootly are currently degraded due to an ongoing upstream Slack incident. We are continuin...
14-day free trial · No credit card required · No code required