Pendo: Marketing site outage
Cloudflare outage, Jul 2, 2019 · 16 vendors, 16 incidents
Pendo’s incident blames Cloudflare as the cause. (hop 1, posted +1 h 44 min vs the first vendor naming Cloudflare)
“…an outage with our marketing site (https://www.pendo.io/). This was due to a now-resolved Cloudflare outage (https://www.cloudflarestatus.com/). The Pendo application, guide serving, and data collecti…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Cloudflare<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>1 vendor, 1 blamed Cloudflare<br/>Wise"]:::blames
root --> h1
h4["1 to 4 hours later<br/>3 vendors, 3 blamed Cloudflare<br/>Optimizely, Discord, Pendo"]:::blames
root --> h4
me["Pendo (this incident)<br/>posted +1 h 44 min"]:::me
h4 --- 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 had experienced an outage with our marketing site (https://www.pendo.io/). This was due to a now-resolved Cloudflare outage (https://www.cloudflarestatus.com/). The Pendo application, guide serving, and data collection were not impacted.
From Pendo’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.pendo.io (opens in new tab).