Rootly’s incident blames Cloudflare as the cause. (hop 1, posted +24 min vs the first vendor naming Cloudflare)
“…Intermittent Issues Accessing Rootly due to Cloudflare All regions are showing healthy traffic and all products are working as expected. We will continue to monitor out of precaution. All regions are…”
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.
What changed
Struck in red is what Rootly removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
RemovedTitle#1
Before: Intermittent Issues Accessing Rootly due to Cloudflare
After: removed
RemovedImpact#2
Before: minor
After: removed
RemovedStatus#3
Before: resolved
After: removed
RemovedStart time#4
Before: 2025-11-18 11:54 UTC
After: removed
RemovedResolved time#5
Before: 2025-11-18 13:58 UTC
After: removed
RemovedAffected components#6
Before: On-Call, Slack App, Web Platform
After: removed
RemovedUpdateinvestigating#7
Before: We are seeing upstream Cloudflare issues at the moment. They are experiencing a global outage that we are monitoring. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
It appears to be intermittent depending on the users location.
After: removed
RemovedUpdatemonitoring#8
Before: We are seeing strong recovery across most regions (NA, EMEA, APAC, etc.). Everything appears to be functioning as expected for most users (some still require retries and is intermittent). We are continuing to monitor. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
After: removed
RemovedUpdatemonitoring#9
Before: We are seeing degraded affects across several regions still for some users. We are continuing to monitor.
After: removed
RemovedUpdatemonitoring#10
Before: We are seeing degraded affects across several regions still for some users (some with stronger recovery than others). We are continuing to monitor.
After: removed
RemovedUpdatemonitoring#11
Before: We are seeing degraded affects across several regions still for some users. We are continuing to monitor. Cloudflare has identified the issue and implementing a fix: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7.
After: removed
RemovedUpdatemonitoring#12
Before: We are continuing to monitor for any further issues.
After: removed
RemovedUpdatemonitoring#13
Before: We are continuing to monitor for any further issues.
After: removed
RemovedUpdateresolved#14
Before: All regions are showing healthy traffic and all products are working as expected. We will continue to monitor out of precaution.
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.