Rootly: Degraded Performance Across the Web Platform and Slack

What to do

Check whether your product depends on Rootly. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 1h 45m it lasted.
Anything that failed between 2024-04-10 07:05 UTC and 2024-04-10 08:50 UTC may need a replay.
Subscribe to Rootly's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=rootly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

identifiedApr 10, 2024, 7:05 AM UTC
The issue has been identified and a fix is being implemented.
provider
identifiedApr 10, 2024, 7:21 AM UTC
We are continuing to work on a fix for this issue.
provider
monitoringApr 10, 2024, 7:30 AM UTC
A fix has been implemented and we are monitoring the results.
provider
resolvedApr 10, 2024, 8:50 AM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Rootly still down?

No, this incident was resolved 2024-04-10 08:50 UTC. For Rootly's live state, see https://down.guide/rootly.

How long did it last?

1h 45m, from 2024-04-10 07:05 UTC to 2024-04-10 08:50 UTC, by the times Rootly posted.

What caused it?

Rootly hasn't published a root cause. If it does, it shows here.

Where does this come from?

Rootly's official status page, https://status.rootly.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.