Rootly vs FireHydrant - Uptime & Outage Comparison
Compare uptime, outage statistics, and incident history between Rootly and FireHydrant. 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.
Rootly
Status monitoring since October 2022
Operational
Rootly Incident Statistics
1
Last 7 days
2
Last 30 days
4
Last 90 days
Recent Rootly Incidents
Resolved
5 days ago
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...
Resolved
18 days ago
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...
Resolved
about 2 months ago
Marketing Site Errors Due to Upstream Webflow Issue
We are currently investigating reports loading issues on our marketing homepage, affecting users in some locations. ...
Components Status
FireHydrant
Status monitoring since March 2024
Operational
FireHydrant Incident Statistics
1
Last 7 days
1
Last 30 days
4
Last 90 days
Recent FireHydrant Incidents
Resolved
6 days ago
Phone spam causing latency issues
We're mitigating an advanced DDoS attack on FireHydrant's servers. We've introduced a change to prevent bad actors f...
Resolved
3 months ago
On Call Schedules not loading
We've identified an issue with listing on-call schedules in our API due to timezone discrepancies related to a recent...
Ready to monitor Rootly, FireHydrant, and all your dependencies?
14-day free trial · No credit card required · No code required