Rootly logo

Is Rootly Down?

MonitoringLive status, outages, and incident history

No. Rootly is up right now.

Every monitored Rootly system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 6m agoLive · every 60s

Know the moment Rootly breaks

Rootly is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Rootly status page
How we know: the official Rootly status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Rootly Status Summary

As of 13:51 UTC on 14 November 2026, Rootly is operational. PulsAPI checked Rootly's official status page and found 8 of 8 components operational, with no active incidents. The latest incident, "Incident creation on Slack impacted due to upstream Slack incident", was on Nov 11, 2026 and lasted 2h 26m.

Cite as: PulsAPI, “Rootly status”, checked 14 November 2026, 13:51 UTC. https://www.pulsapi.com/services/rootly

Rootly Component Status

The main Rootly systems on this page. All 8 are operational right now.

8operational
API
Operational
Mobile App
Operational
On-Call
Operational

5 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Rootly AI, Slack App, Status Pages, Web Platform, Workflows.

See all of them free

Component statuses may change independently during partial outages.

Recent Rootly Outages & Incidents

Incident history from the official Rootly status page, including resolution updates.

Incident creation on Slack impacted due to upstream Slack incidentResolved Nov 11, 2026 · 2h 26mResolved

We are no longer seeing errors with Slack channel creation or message delivery. We are marking this incident as resolved and will continue to monitor to ensure service remains stable. --- [2026-11-11T08:25:26-08:00] (monitoring) Incident channel creation has recovered on our end. We are continuing to monitor while we await confirmation of full recovery on Slack's Status page. You can follow Slack's progress here: https://slack-status.com/2026-11/b8bb993128ac94f5 --- [2026-11-11T08:07:59-08:00] (monitoring) Error rates remain significantly lower, though we continue to see occasional intermittent issues with incident channel creation. We are continuing to monitor and you can continue to follow along Slack's progress here: https://slack-status.com/2026-11/b8bb993128ac94f5. Rootly remains available via Web Platform and On-Call is unaffected. --- [2026-11-11T07:40:38-08:00] (monitoring) We are seeing errors drop significantly and only a few intermittent issues. We are continuing to monitor and you can continue to follow along Slack's progress here: https://slack-status.com/2026-11/b8bb993128ac94f5. Rootly remains available via Web Platform and On-Call is unaffected. --- [2026-11-11T07:40:52-08:00] (investigating) We are investigating errors in creating incident channels due to an upstream Slack outage. Rootly On-Call remains fully operational, including alerting and paging. Incident creation inside the Web Platform is also unaffected. We are monitoring the situation and will provide updates as Slack restores their service. You can follow along here: https://slack-status.com/2026-11/b8bb993128ac94f5.

Some users seeing errors loading dropdowns and alert index pageResolved Aug 27, 2026 · 15 minResolved

This incident has been resolved. --- [2026-10-23T09:06:23-07:00] (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.

Rootly Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Rootly incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Rootly Outage Reports

Problems reported by engineers using Rootly. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Rootly problems reported yet.

Something wrong with Rootly on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Rootly

Rootly's status page at status.rootly.com lists 8 components, such as API, Mobile App and On-Call. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on Rootly's side or yours.

Rootly Status FAQ

Is Rootly down right now?

The verdict at the top of this page comes from the latest poll of the official Rootly status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Rootly is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Rootly recovers.

How do I check Rootly uptime history?

PulsAPI tracks Rootly uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Rootly changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Rootly outages?

PulsAPI reads the official Rootly status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Rootly components?

Yes. PulsAPI monitors 8 individual Rootly components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Rootly goes down?

Yes. Create a free account and subscribe to Rootly: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Rootly to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Rootly problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Rootly?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Rootly plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Rootly with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services