Rewindex

CompaniesRootlyIncidents

Rootly: Delays on Slack and Web Platform

No impact listedStatus: resolvedStarted Resolved (22 min)4 updatesstspg.io (opens in new tab)
Part of an outage event

Cloudflare outage, Oct 30, 2023 · 24 vendors, 24 incidents

Rootly’s incident blames Cloudflare as the cause. (hop 1, posted +2 min vs the first vendor naming Cloudflare)

“…king as normal, including incident creation in Slack. We had an upstream hiccup caused by Cloudflare. Looks like everything is working as normal, including incident creation in Slack. We had an upstre…”

Swipe sideways to see the whole diagram.

blamed Auth0Cloudflareown incident not archivedWithin an hour4 vendors, 3 blamed CloudflareCensus, Rootly, Optimizely, VantaAuth0own incident not archivedSvix, Dremio+9 min to +39 minRootly (this incident)posted +2 min
blamed Auth0Cloudflareown incident not archivedWithin an hour4 vendors, 3 blamed CloudflareCensus, Rootly, Optimizely,VantaAuth0own incident not archivedSvix, Dremio+9 min to +39 minRootly (this incident)posted +2 min
Rootly is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>4 vendors, 3 blamed Cloudflare<br/>Census, Rootly, Optimizely, Vanta"]:::blames
  root --> h1
  p0["Auth0<br/>own incident not archived"]:::inferred
  root -.-> p0
  k0["Svix, Dremio<br/>+9 min to +39 min"]:::hop2
  p0 -->|"blamed Auth0"| k0
  me["Rootly (this incident)<br/>posted +2 min"]:::me
  h1 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: TerraformRootly Slack AppSlack AppAPIWeb PlatformWorkflows

Timeline of updates

  1. investigating

    We are noticing our background jobs processing slower than normal. Any workflows queued to run are behind schedule. Our engineering team has identified the issue and is currently deploying a fix.

  2. investigating

    We are continuing to investigate this issue. Our engineering team has a fix currently being deployed.

  3. investigating

    We are continuing to investigate this issue. Our engineering team has a fix currently being deployed.

  4. resolved

    Looks like everything is working as normal, including incident creation in Slack. We had an upstream hiccup caused by Cloudflare.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Rootly profileRecent Rootly incidentsMarkdownJSON