Rootly: Intermittent Failures with User Sign In and Incident Creation

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 26m it lasted.
Anything that failed between 2024-04-01 14:53 UTC and 2024-04-01 15:19 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.

investigatingApr 1, 2024, 3:03 PM UTC
The team is currently investigating issues with users signing into Rootly Web Platform.
provider
investigatingApr 1, 2024, 3:05 PM UTC
We are continuing to investigate this issue.
provider
investigatingApr 1, 2024, 3:10 PM UTC
We are continuing to investigate this issue. Slack, Web, and API are currently impacted. Rootly On-Call remains online without impact.
provider
identifiedApr 1, 2024, 3:15 PM UTC
The issue has been identified and the team is aware of the root cause. A fix is being implemented.
provider
resolvedApr 1, 2024, 3:19 PM UTC
This incident has been resolved. RCA will follow and be sent to customers.
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-01 15:19 UTC. For Rootly's live state, see https://down.guide/rootly.

How long did it last?

26m, from 2024-04-01 14:53 UTC to 2024-04-01 15:19 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.