Sentry: Potential loss in ability to submit events due to CloudFlare Outage.
Cloudflare outage, Jul 17, 2020 · 24 vendors, 24 incidents
Sentry’s incident blames Cloudflare as the cause. (hop 1, posted +49 min vs the first vendor naming Cloudflare)
“…Potential loss in ability to submit events due to CloudFlare Outage. We believe CloudFlare has addressed their instability.…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Cloudflare<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>6 vendors, 6 blamed Cloudflare<br/>Sigma Computing, WorkOS, Doppler, Linode (Akamai) +2"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed Cloudflare<br/>Hotjar"]:::blames
root --> h4
me["Sentry (this incident)<br/>posted +49 min"]:::me
h1 --- meFull 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.
Timeline of updates
- resolved
We believe CloudFlare has addressed their instability.
From Sentry’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.sentry.io (opens in new tab).