PandaDoc: Issue with document creation using Public API
AWS outage, Nov 25, 2020 · 28 vendors, 29 incidents
PandaDoc’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +1 h 50 min vs the first vendor naming AWS)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>1 vendor, 1 blamed AWS<br/>Pipedream"]:::blames
root --> h1
h4["1 to 4 hours later<br/>4 vendors, 4 blamed AWS<br/>HubSpot, Xero, Lattice, Heap"]:::blames
root --> h4
later["Later<br/>2 vendors, 2 blamed AWS<br/>Confluent, Pipedream"]:::blames
root --> later
me["PandaDoc (this incident)<br/>posted +1 h 50 min"]:::me
root -.->|"same window"| 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’re all set! Users can create documents using Public API. If you experience any issues with this, please reach out to us at support@pandadoc.com.
From PandaDoc’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.pandadoc.com (opens in new tab).