PandaDoc: Issue with Identity Verification (Persona)
Google Cloud outage, Jun 12, 2025 · 101 vendors, 107 incidents
PandaDoc’s incident started in the same window without naming Google Cloud (timing only, not evidence of a link). (timing only, posted +1 h 18 min vs the first vendor naming Google Cloud)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Google Cloud<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>29 vendors, 28 blamed Google Cloud<br/>Pinecone, Northflank, imgix +26"]:::blames
root --> h1
h4["1 to 4 hours later<br/>12 vendors, 11 blamed Google Cloud<br/>Smartsheet, Daily, Confluent +9"]:::blames
root --> h4
later["Later<br/>1 vendor, 1 blamed Google Cloud<br/>Zilliz"]:::blames
root --> later
p0["Firebase<br/>own incident not archived"]:::inferred
root -.-> p0
k0["Codeium, Windsurf<br/>+13 min"]:::hop2
p0 -->|"blamed Firebase"| k0
p1["Anthropic<br/>posted +28 min, did not name Google Cloud"]:::timing
root -.-> p1
k1["GitHub, GitHub Copilot<br/>+24 min"]:::hop2
p1 -->|"blamed Anthropic"| k1
p2["Cloudflare<br/>own incident not archived"]:::inferred
root -.-> p2
k2["Doppler, Jupyter (Anaconda), Socket +4<br/>+35 min to +3 h 41 min"]:::hop2
p2 -->|"blamed Cloudflare"| k2
me["PandaDoc (this incident)<br/>posted +1 h 18 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
- investigating
We’re currently experiencing issues with identity verification due to an incident on our third-party provider’s side (Persona). Impact: Notarization: Persona verification is unavailable. Workaround: Please use Personally Known verification instead. Document Verification (ID Check): ID Check for Advanced Verification may not function as expected. Workaround: You can switch the recipient’s verification method to another available type, such as Knowledge-Based Authentication (KBA). Instructions: KBA Setup Guide We recommend using these alternatives until the issue with Persona is resolved. Our team is monitoring the situation closely.
- resolved
This incident has been resolved.
Archive proof
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.
How the archive is checked, and what it cannot prove.
First version captured 18:22 UTC
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on Oct 19, 23:18 UTC. Record hash
b705cc8e0c6c7321…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).